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
Failed to append block because it was to large causes next append to fail #6318
Comments
Let's drop the limit on the Raft/Journal side - we already have a limit in the dispatcher and it is well handled, and there's no reason anymore to limit it downstream. |
Blocked by #6307 |
@deepthidevaki this was not part of alpha 4 right? Because we have a error in alpha4 which seem to cause this again https://console.cloud.google.com/logs/viewer?expandAll=false×tamp=2021-04-06T03:31:52.902000000Z&dateRangeStart=2021-04-06T02:31:52.902Z&dateRangeEnd=2021-04-06T04:31:52.902Z&project=camunda-cloud-240911&authuser=1&minLogLevel=0&customFacets=&limitCustomFacetWidth=true&advancedFilter=%0AlogName:%22stdout%22%0Aresource.type%3D%22k8s_container%22%0Aresource.labels.cluster_name%3D%22ultratest%22%0Aresource.labels.namespace_name%3D%2259d9bd73-099a-4605-b0f6-5d87d994be63-zeebe%22%0Aresource.labels.container_name%3D%22zeebe%22&interval=JUMP_TO_TIME&scrollTimestamp=2021-04-06T03:32:32.158671000Z&pinnedLogId=1wjesayg3vidfmg&pinnedLogTimestamp=2021-04-06T03:31:22.901757Z We can see that a append fails because it is to big and this cause next appends also to fail
|
Probably not part of alpha4. There is no release label. |
Yes this would be also my assumption, just wanted to be sure. |
* fix: disable migrate button if xml could not be fetched * test: add test for migrate button behaviour on process XML load error
Describe the bug
It can happen that we fail to append a Block in the
LeaderRole#appendEntry
, which can cause that additional appends fail since the positions are not incremented by one anymore. The position is generated by the dispatcher and continues to grow.Note: related to a support issue
To Reproduce
Find a way to write a record, which scratches the limit and reaches that via Raft metadata.
Expected behavior
That we reject the write and not generating the position. Or we accept gaps in positions.
Log/Stacktrace
Full Stacktrace
Environment:
Customer Support
The text was updated successfully, but these errors were encountered: