Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when there’s an attempt to force segment replication sync in OpenSearch, but the system configuration doesn’t allow it. This could be due to restrictions set in the OpenSearch settings or due to a lack of necessary permissions. To resolve this issue, you can adjust the OpenSearch settings to allow force segment replication sync, or ensure that the user or process attempting the operation has the necessary permissions. Additionally, check if the cluster health is green and there are no ongoing recovery or relocation operations, as these could also prevent segment replication.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” Ignore force segment replication sync as it is not allowed ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: indices, replication.
Log Context
Log “Ignore force segment replication sync as it is not allowed” classname is SegmentReplicationTargetService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
public void messageReceived(final ForceSyncRequest request; TransportChannel channel; Task task) throws Exception {
assert indicesService != null;
final IndexShard indexShard = indicesService.getShardOrNull(request.getShardId());
// Proceed with round of segment replication only when it is allowed
if (indexShard == null || indexShard.getReplicationEngine().isEmpty()) {
logger.info("Ignore force segment replication sync as it is not allowed");
channel.sendResponse(TransportResponse.Empty.INSTANCE);
return;
}
startReplication(indexShard; new SegmentReplicationTargetService.SegmentReplicationListener() {
@Override
