-
Notifications
You must be signed in to change notification settings - Fork 7
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
Timed reprocess system sometimes gets stuck #108
Comments
2024-08-18The It is blocked waiting for enqueue table scan to complete.
All of the leaf scans are complete, but 2 of the enqueue task states are left over. This should not be possible. This indicates that the table scan enqueue succeeded (because all of the leaf scans are done) but somehow the enqueue task states got recreated or failed to be deleted somehow. The parameters for the leftover task state record are here: {
"n": "tps.pq",
"v": 1,
"d": {
"sf": 1,
"ss": 1,
"d": 59,
"p": "08584776361820073217-gaxyddyi2cqubp5af23sl7m4ei-r100-B894-",
"m": "08584776361820073217-gaxyddyi2cqubp5af23sl7m4ei-r100-B894-czlovek.files",
"u": "08584776361820073217-gaxyddyi2cqubp5af23sl7m4ei-r100-B894-\uFFFF"
}
} {
"n": "tps.pkq",
"v": 1,
"d": {
"sf": 1,
"ss": 1,
"d": 59,
"p": "08584776361820073217-gaxyddyi2cqubp5af23sl7m4ei-r100-B894-czlovek.files",
"r": "1.0.9"
}
} Task state entities (2 left dangling): The task state entities are added before their corresponding message (which is desired) by perhaps a transient table or queue error, or slowness cause the problem. Insights/src/Worker.Logic/TableScan/TableScanMessageProcessor.cs Lines 233 to 238 in 56ee2ee
The only hint I could from the existing telemetry is that some table batch operations failed with a server timeout. The storage no-op system kicked in, but seemed to be related to other buckets. Next step: enhance telemetry around message enqueue and table entity changes so we can better understand what happened. |
The "timed reprocess" system sometimes gets stuck. For this reason, it's not ready to be enabled by default.
The text was updated successfully, but these errors were encountered: