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

Detecting exising indices and shards is broken #13265

Closed
s1monw opened this issue Sep 2, 2015 · 1 comment
Closed

Detecting exising indices and shards is broken #13265

s1monw opened this issue Sep 2, 2015 · 1 comment
Labels
>bug discuss :Distributed/Engine Anything around managing Lucene and the Translog in an open shard.

Comments

@s1monw
Copy link
Contributor

s1monw commented Sep 2, 2015

Today we rely on FS operations to find the indices on disk or to find the shards for an index. This is super error prone and requires String parsing. We should on each level index -> shard know exactly what to expect and don't use directory listings which are expensive and subject to change. There should be a metadata file on each level that is atomically written that we open and see what we have to expect no matter of what's on the FS.

@dakrone
Copy link
Member

dakrone commented Sep 2, 2015

+1 to moving away from parsing things from disk

@clintongormley clintongormley added the :Distributed/Store Issues around managing unopened Lucene indices. If it touches Store.java, this is a likely label. label Nov 28, 2015
@clintongormley clintongormley added :Distributed/Engine Anything around managing Lucene and the Translog in an open shard. and removed :Distributed/Store Issues around managing unopened Lucene indices. If it touches Store.java, this is a likely label. labels Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug discuss :Distributed/Engine Anything around managing Lucene and the Translog in an open shard.
Projects
None yet
Development

No branches or pull requests

3 participants