Which problem is this PR solving?

• Towards Phase out the distinction between primary and archive storage #6065

Description of the changes

• This PR completely removes the interface storage.ArchiveFactory by refactoring all the storage implementations to remove the distinction between a primary and archive interface. Note that the concept of archive storage remains the same within Jaeger, we just now use the same interface to handle both primary and archive storages.
• 🛑 Breaking change for users of GRPC storage 🛑
  • The GRPC storage was changed to only dispatch to the primary storage instead of being able to dispatch to a primary and archive storage.
  • Mitigation for jaeger-v1 users: In order to restore your archive storage, configure a new GRPC server on a different port and specify it via --grpc-storage-archive.server. Archive storage will also need to be enabled via --grpc-storage-archive.enabled=true
    • If you were using ElasticSearch or OpenSearch with grpc storage, you will require an extra mitigation step for your archive storage. This mitigation step can be found in Step 9 of the PR description of [v2][query] Create archive reader/writer using regular factory methods #6519 (specifically the section labelled Add Alias from Old Index to New Index).
  • Mitigation for jaeger-v2 users: In order to restore your archive storage, configured a new GRPC server on a different port and specify it via a new storage backend in jaeger_storage.backends (an example of this can be viewed at https://github.com/jaegertracing/jaeger/blob/main/cmd/jaeger/config-remote-storage.yaml)

How was this change tested?

gRPC Storage

On main (establish ground truth)

Start the remote storage binary (uses memory storage by default which implements the ArchiveFactory interface)

go run ./cmd/remote-storage

Start the all in one binary configured with grpc storage (jaeger-v1)

SPAN_STORAGE_TYPE=grpc go run ./cmd/all-in-one --grpc-storage.server=http://localhost:17271

Traces can be archived from the UI

For jaeger-v2, change the extension section of cmd/jaeger/internal/all-in-one.yaml to be the following

  jaeger_query:
    storage:
      traces: some_storage
      traces_archive: some_storage

  jaeger_storage:
    backends:
      some_storage:
        grpc:
          endpoint: localhost:17271
          tls:
            insecure: true

and then start the binary as follows:

go run ./cmd/jaeger/

For current PR

Stop both binaries and checkout this PR

gh pr checkout 6567

Start two remote storage binaries (in two separate terminals)

go run ./cmd/remote-storage --admin.http.host-port=:17270 --grpc.host-port=:17271 
go run ./cmd/remote-storage --admin.http.host-port=:17272 --grpc.host-port=:17273

Start the all-in-one binary with explicit archive configurations

SPAN_STORAGE_TYPE=grpc go run ./cmd/all-in-one --grpc-storage.server=http://localhost:17271 --grpc-storage-archive.enabled=true --grpc-storage-archive.server=http://localhost:17273

Traces can be once again archived from the UI

For jaeger-v2, the configuration was changed to the following:

extensions:
  jaeger_query:
    storage:
      traces: some_storage
      traces_archive: another_storage

  jaeger_storage:
    backends:
      some_storage:
        grpc:
          endpoint: localhost:17271
          tls:
            insecure: true
      another_storage:
        grpc:
          endpoint: localhost:17273
          tls:
            insecure: true

Try running all-in-one without archive-storage enabled

SPAN_STORAGE_TYPE=grpc go run ./cmd/all-in-one --grpc-storage.server=http://localhost:17271

We cannot archive traces

CLI Flags

ElasticSearch CLI Flags

git checkout main
SPAN_STORAGE_TYPE=elasticsearch go run ./cmd/collector help > es_main
git checkout v1-es-archive
SPAN_STORAGE_TYPE=elasticsearch go run ./cmd/collector help > es_current

The diff can be viewed here. There is no difference.

Cassandra CLI Flags

git checkout main
SPAN_STORAGE_TYPE=cassandra go run ./cmd/collector help > cassandra_main
git checkout v1-es-archive
SPAN_STORAGE_TYPE=cassandra go run ./cmd/collector help > cassandra_current

The diff can be viewed here. There are a few here differences here in which cassandra-archive.* gains some new configuration options that were previously only existed for the primary storage. cassandra-archive.* also gains some defaults that will be the same as the the primary storage.

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test