Details
-
Improvement
-
Resolution: Fixed
-
Major
-
4.5.0
-
None
Description
Current a scan can be canceled for two reasons: One the query that was using the scan has been satisfied, this is normally because the query used the LIMIT keyword. The other case is when the client connection to the query node has been terminated and in turn the query node cancels the operations that the indexer is doing for that query.
Current both these cases are logged as:
2016-07-13T10:52:04.724-04:00 [Error] SCAN##133106 RESPONSE rows:2730, waitTime:2.688µs, totalTime:2.723544ms, status:(error = Client requested cancel), requestId:fcd43d4a-1427-43f7-aa11-ff499e8598f7
|
I suggest that a scan being cancel because of the query being satisfied is not logged as Error and the error message is not "Client requested cancel".
I also think it is a good idea to keep logging at Error level when a scan is cancel because:
- It is an error, that should be investigated.
- It also gives evidence that there might be a problem with the client/network/query service.
Attachments
Issue Links
- blocks
-
MB-20290 4.6.0 Point Release
- Closed