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

Document order of replicas is nondeterministic #6442

Open
nadove-ucsc opened this issue Jul 23, 2024 · 3 comments
Open

Document order of replicas is nondeterministic #6442

nadove-ucsc opened this issue Jul 23, 2024 · 3 comments
Labels
-- [priority] Low bug [type] A defect preventing use of the system as specified debt [type] A defect incurring continued engineering cost needs info [process] Resolution requires more information orange [process] Done by the Azul team test [subject] Unit and integration test code

Comments

@nadove-ucsc
Copy link
Contributor

nadove-ucsc commented Jul 23, 2024

While working on #6122, we had difficulty asserting the contents of the verbatim PFB manifest due to inconsistencies in the ordering of the replicas. The order appeared stable on a personal deployment, but changed when pushing to GitHub. Our investigation revealed that the shard count affected the order of the replicas in the index, but patching the shard count to a consistent value (1) did not result in a consistent order.

Currently, our workaround is to sort the manifests before comparing the expected and observed values.

@nadove-ucsc nadove-ucsc added the orange [process] Done by the Azul team label Jul 23, 2024
@nadove-ucsc nadove-ucsc changed the title Document order of replicas in nondeterministic Document order of replicas is nondeterministic Jul 23, 2024
nadove-ucsc added a commit that referenced this issue Jul 23, 2024
@nadove-ucsc
Copy link
Contributor Author

It remains undetermined whether the inconsistency is due to the order in which the replicas are written to the index, or whether it arises when reading them from the index.

@dsotirho-ucsc
Copy link
Contributor

Assignee to consider next steps.

dsotirho-ucsc pushed a commit that referenced this issue Aug 2, 2024
dsotirho-ucsc pushed a commit that referenced this issue Aug 2, 2024
@hannes-ucsc hannes-ucsc added - [priority] Medium bug [type] A defect preventing use of the system as specified test [subject] Unit and integration test code debt [type] A defect incurring continued engineering cost -- [priority] Low and removed - [priority] Medium labels Sep 4, 2024
@hannes-ucsc hannes-ucsc removed their assignment Sep 4, 2024
@hannes-ucsc hannes-ucsc added the needs info [process] Resolution requires more information label Sep 4, 2024
@hannes-ucsc
Copy link
Member

We don't currently know what causes the non-determinism. We should probably ask Elastic or the Elasticsearch community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-- [priority] Low bug [type] A defect preventing use of the system as specified debt [type] A defect incurring continued engineering cost needs info [process] Resolution requires more information orange [process] Done by the Azul team test [subject] Unit and integration test code
Projects
None yet
Development

No branches or pull requests

3 participants