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

Failed To Upload Config On Busy Node #701

Closed
Alsheh opened this issue May 29, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@Alsheh
Copy link

commented May 29, 2019

Failed to upload sgconfig because SG primary shard happened to be on a busy node:

   FAIL: Configuration for 'config' failed because of org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of processing of [34088901][indices:data/write/bulk[s][p]]: request: BulkShardRequest [[searchguard][0]] containing [index {[searchguard][sg][config], source[n/a, actual length: [3.2kb], max length: 2kb]}] and a refresh, target allocation id: awbX-tSpQG6Tymfly0UqvA, primary term: 1 on EsThreadPoolExecutor[name = es-busy-node/write, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@33053b81[Running, pool size = 1, active threads = 1, queued tasks = 201, completed tasks = 12481003]]

I tried to move the SG primary shard to a less busy node using the ES API but I get this error:

{
  "error": {
    "root_cause": [
      {
        "type": "security_exception",
        "reason": "no permissions for [] and User [name=admin, roles=[admin], requestedTenant=null]"
      }
    ],
    "type": "security_exception",
    "reason": "no permissions for [] and User [name=admin, roles=[admin], requestedTenant=null]"
  },
  "status": 403
}

and the sgadmin tool does not seem to allow for a culster-level shard allocation filtering. I think it is necessary to have the ability to apply shard allocation filtering to the SG index either by the ES API or by the sgadmin tool.

@floragunncom

This comment has been minimized.

Copy link
Owner

commented May 29, 2019

You always can use curl with the same certificates you use for sgadmin to allow any operation. Should then look like curl -Ss https://eshost:9200/<api> --cert /path/to/admincert.pem --key /path/to/adminkey.pem --cacert /path/to/root-ca.pem

See also

@Alsheh

This comment has been minimized.

Copy link
Author

commented May 29, 2019

@floragunncom thanks! That's what I was looking for.

@Alsheh Alsheh closed this May 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.