-
Notifications
You must be signed in to change notification settings - Fork 229
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
Creating index template for Kibana to configure index replicas #1323
Creating index template for Kibana to configure index replicas #1323
Conversation
/retest |
1 similar comment
/retest |
"order": 0, | ||
"settings": { | ||
"index.number_of_replicas": $REPLICA_SHARDS, | ||
"index.number_of_shards": PRIMARY_SHARDS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing $
? ($PRIMARY_SHARDS
)
Left one comment. |
43d84bb
to
01f9327
Compare
Squashed commits |
/hold
|
@lukas-vlcek any thoughts? it appears that |
@ewolinetz let's check how exactly Kibana creates its indices. Can we locate particular line in the source code? |
From the ES logs:
From return callWithInternalUser('indices.create', {
index: index,
body: {
settings: {
number_of_shards: 1,
'index.mapper.dynamic': false
},
mappings
}
}).catch(handleError('Unable to create Kibana index "<%= kibana.index %>"')).then(function () {
return callWithInternalUser('cluster.health', {
waitForStatus: 'yellow',
index: index
}).catch(handleError('Waiting for Kibana index "<%= kibana.index %>" to come online failed.'));
}); |
@ewolinetz What will happen if we delete the .kibana index manually. Is the new .kibana index replicas=0? |
@ewolinetz the |
@lukas-vlcek unfortunately when i've tried that before the request is redirected to a kibana user index instead of changing the @anpingli I'll try that and see. Hopefully it doesn't redirect it to a kibana user index as well... |
@ewolinetz even when using admin certs? |
The multitenant code will attempt to modify anything that has Kibana in the request and a bearer token is provided. This is the source of a known issue where we are unable to delete index patterns. Maybe we should consider allowing admin users who provide a special header to take a request as is with no modifications. I would expect the admin certs to already behave this way but maybe there is something we are modifying |
FYI, the May be we can accept the YELLOW cluster state when running particular test? |
4cce24f
to
d1068b1
Compare
I can delete the indices, and then I see them recreated correctly with 0 replicas.
|
I think we are running into an issue where we are not ready (the index templates are still being seeded) and then ES is somehow allowing traffic through. |
Confirmed that #1326 fixes the issue of the index being created before the index template is seeded |
d1068b1
to
7e3b004
Compare
/hold |
7e3b004
to
724762e
Compare
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Addresses #1315