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

Clustered Mesh Search Status #1187

Open
deckdom opened this issue Apr 13, 2021 · 0 comments · Fixed by #1255
Open

Clustered Mesh Search Status #1187

deckdom opened this issue Apr 13, 2021 · 0 comments · Fixed by #1255

Comments

@deckdom
Copy link
Contributor

deckdom commented Apr 13, 2021

Gentics Mesh Version, operating system, or hardware.

  • v1.6.x

Problem

When Mesh is clustered, usually some random instance responds (Depends on load-balancer and other stuff of course.).
This is however quite troublesome for some endpoints, where only one instance is currently working on it and is the only one keeping track of the status.

Such an Endpoint would be the /admin/search/sync and/or /search/status.
When you start an ES Sync, only one instance is starting this operation (Which is fine).
However, when attempting to check the status of it, other instances usually respond to this request which do not know of this process and respond with an "empty" (Everything is 0) response which isn't the actual status.
Checking the logs I can clearly see some progress being made.

Reproducer

  • Create a Cluster of min. 2 instances (Currently using 3+1)
  • Add some content
  • Clear the search /admin/search/clear
  • Sync the search /admin/search/sync
  • Check the sync status /search/status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant