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
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>
<severityvalue="error"/>
<codevalue="timeout"/>
<diagnosticsvalue="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.
The text was updated successfully, but these errors were encountered:
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: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.
The text was updated successfully, but these errors were encountered: