Troubleshoot indexing and replication separation

Use the following information to troubleshoot common issues with Indexing and Replication Separation.

After you configure and push the cluster bundle for Indexing and Replication Separation, the feature might not behave as expected. The following sections describe common issues and their solutions.

The feature does not appear to turn on

The feature might not activate if one or more prerequisites are not met.

  1. Confirm that Ingest-Tier Scaling is already enabled.
  2. Confirm that SmartStore is enabled for the configured index.
  3. Confirm that hotBucketStreaming.sendSlices = true is present in the correct index stanza.
  4. Confirm that the updated bundle was pushed successfully.
  5. Confirm that the cluster finished converging after the bundle push.

The source peer still appears to use normal replication

The source peer might continue to use normal replication if the index configuration is not applied correctly.

  1. Confirm that the index you are testing is configured for the feature.
  2. Confirm that the index has a valid SmartStore remotePath.
  3. Confirm that no local app or peer-level override is replacing the cluster bundle configuration.
  4. Confirm that you are reviewing a new hot bucket created after the updated configuration took effect.

The cluster manager does not create streaming target jobs

The cluster manager might not create HotSlicePollingStreamingTargetJob jobs if the source peer or cluster settings are not correct.

  1. Confirm that the source peer reports streaming source behavior.
  2. Confirm that cluster health is green before you test.
  3. Confirm that replication and site settings satisfy the documented constraints.
  4. Check cluster manager logs for assignment or mask-transition errors.
  5. Inspect the bucket from the cluster manager REST API.
    CODE 
    GET /services/cluster/manager/buckets/{name}

The target peer does not become a streaming target

The target peer might not receive the streaming target assignment if the cluster manager has not created the required jobs or the peer is not healthy.

  1. Confirm that the cluster manager created HotSlicePollingStreamingTargetJob jobs.
  2. Confirm that the target peer is healthy and connected.
  3. Confirm that the target peer received the updated configuration and is in the cluster.
  4. Confirm that the bucket under test belongs to an index that has the feature enabled.