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

Add System ID to Paging Requests #1914

Open
alexanderkiel opened this issue Jul 22, 2024 · 0 comments
Open

Add System ID to Paging Requests #1914

alexanderkiel opened this issue Jul 22, 2024 · 0 comments
Labels
enhancement New feature or request operation Operational issues like monitoring and maintenance.

Comments

@alexanderkiel
Copy link
Member

In case two different Blaze systems exist, it's possible that the paging URL's point from one system to the other. In case the other system has a lower database point in time (t) a timeout error like this is returned:

<OperationOutcome>
  <issue>
    <severity value="error"/>
    <code value="timeout"/>
    <diagnostics value="Timeout while trying to acquire the database state with t=<t>. The indexer has probably fallen behind. Please try to lower the transaction load or increase the timeout of 10000 ms by setting DB_SYNC_TIMEOUT to a higher value if you see this often."/>
  </issue>
</OperationOutcome>

In case the t isn't lower, the request will be answered but the answer would be just wrong.

A system ID could solve the problem. We could save it into the default column family of the index database.

@alexanderkiel alexanderkiel added enhancement New feature or request operation Operational issues like monitoring and maintenance. labels Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request operation Operational issues like monitoring and maintenance.
Projects
None yet
Development

No branches or pull requests

1 participant