You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Gentics Mesh Version, operating system, or hardware.
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
/admin/search/clear
/admin/search/sync
/search/status
The text was updated successfully, but these errors were encountered: