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

Creating multiple indices for a single build overwrites metadata of previous indices #243

Open
ravila4 opened this issue Jul 6, 2022 · 0 comments

Comments

@ravila4
Copy link
Contributor

ravila4 commented Jul 6, 2022

Creating multiple indices for a build (for example, one for elasticsearch 7 and 8) results in only latest index information being displayed in the releases tab of the build information. I think this behavior is new, as I recall being able to see information about multiple releases before updating to BT 0.11.

Reproduction steps

  1. Create a build (You can use the "test_drug" configuration in MyChem for a quick result)
  2. Create a full release in 'local7' environment
  3. Create a full release in 'local8' environment

Results

We after running both steps, we see only the latest index is displayed in the studio, even though both were created successfully.
Both indices exist in their respective servers, and we can create snapshots manually.

Expected results

We should see two different indices, one for ES7 and one for ES8.

We can see that the issue is not with the studio app because the index data is missing from the MongoDB backend.
For example, for the build drug_20220628_hzp7ldjc in MyChem, we can see the metadata only contains one index under the index field: http://localhost:27080/build/drug_20220628_hzp7ldjc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant