Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Index replication task exits after OS restart #222

Closed
saikaranam-amazon opened this issue Oct 28, 2021 · 0 comments
Closed

[BUG] Index replication task exits after OS restart #222

saikaranam-amazon opened this issue Oct 28, 2021 · 0 comments
Assignees
Labels
bug Something isn't working v1.2.0

Comments

@saikaranam-amazon
Copy link
Member

saikaranam-amazon commented Oct 28, 2021

Describe the bug
Index replication task exits after OS restart

To Reproduce
Steps to reproduce the behavior:

  • Create cluster without dedicated master nodes at the follower side
  • Start replication on any index
  • Bounce ES env/ Kill ES process on all the nodes
  • Verify that the replication is still going on and operation gets synced but the index replication task will be missing

Logs:

[o.e.p.AllocatedPersistentTask] [c09475a89cd6561ecff93a6dee209eb2] task replication:index:remote-index failed with an exception
ElasticsearchSecurityException[Open Distro Security not initialized for indices:admin/plugins/replication/index/update_metadata]
        at com.amazon.opendistroforelasticsearch.security.filter.OpenDistroSecurityFilter.apply0(OpenDistroSecurityFilter.java:297)
        at com.amazon.opendistroforelasticsearch.security.filter.OpenDistroSecurityFilter.apply(OpenDistroSecurityFilter.java:154)
        at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:178)
        at com.amazon.opendistro.elasticsearch.performanceanalyzer.action.PerformanceAnalyzerActionFilter.apply(PerformanceAnalyzerActionFilter.java:77)
        at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:178)
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:156)
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:84)
        at org.elasticsearch.client.node.NodeClient.executeLocally(NodeClient.java:86)
        at org.elasticsearch.client.node.NodeClient.doExecute(NodeClient.java:75)
        at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:412)
        at com.amazon.elasticsearch.replication.util.CoroutinesKt$suspendExecute$2.invokeSuspend(Coroutines.kt:84)
        at com.amazon.elasticsearch.replication.util.CoroutinesKt$suspendExecute$2.invoke(Coroutines.kt)
        at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:91)
        at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:154)
        at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
        at com.amazon.elasticsearch.replication.util.CoroutinesKt.suspendExecute(Coroutines.kt:83)
        at com.amazon.elasticsearch.replication.util.CoroutinesKt.suspendExecute$default(Coroutines.kt:82)
        at com.amazon.elasticsearch.replication.task.index.IndexReplicationTask.evalMonitoringState(IndexReplicationTask.kt:327)

Expected behavior
Index replication should be running

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v1.2.0
Projects
None yet
Development

No branches or pull requests

1 participant