You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2022/04/08 16:13:37 UTC

[GitHub] [accumulo] DomGarguilo commented on issue #2606: Scanner.setTimeout() does not work

DomGarguilo commented on issue #2606:
URL: https://github.com/apache/accumulo/issues/2606#issuecomment-1093052097

   I've looked into this a bit and from what I can tell the timeout set here only gets applied to the thrift scan. I've created a branch and added some logs and it looks like the timeout will trigger an exception if the thrift scan duration is longer than the timeout. Below are some logs from my branch that (might) help illustrate this:
   ```
   2022-04-08T11:57:13,978 [functional.TimeoutIT] DEBUG: NOW ADDING 2 SECOND TIMEOUT TO SCANNER ---------------
   2022-04-08T11:57:13,978 [functional.TimeoutIT] DEBUG: Scanner timeout: 2s
   2022-04-08T11:57:13,979 [clientImpl.ScannerImpl] DEBUG: ScannerImpl timeout: 2s
   2022-04-08T11:57:13,979 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:13,979 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.0s Timeout: 2s
   2022-04-08T11:57:14,986 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:14,987 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.001s Timeout: 2s
   2022-04-08T11:57:15,990 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:15,991 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.0s Timeout: 2s
   2022-04-08T11:57:16,995 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:16,995 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.0s Timeout: 2s
   2022-04-08T11:57:17,998 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:17,999 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.0s Timeout: 2s
   2022-04-08T11:57:19,002 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:19,003 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.0s Timeout: 2s
   2022-04-08T11:57:20,006 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:20,007 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.001s Timeout: 2s
   2022-04-08T11:57:21,010 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   2022-04-08T11:57:21,011 [clientImpl.ThriftScanner] INFO : Duration of scan: 0.0s Timeout: 2s
   2022-04-08T11:57:21,989 [clientImpl.ScannerIterator] DEBUG: Starting thrift scan with timeout: 2s
   ```
   I'm not sure if this is the expected behavior and the slow iterator attached to the scanner just does not slow this scan down, or if this timeout should also be applied elsewhere and be triggered on some other condition as well.
   
   [Here is a link to the diff of a branch I added these logs to](https://github.com/apache/accumulo/compare/main...DomGarguilo:scannerTimeoutInvestigation?expand=1). I refactored TimeoutIT so that the tests can be run independently (which may be a good standalone improvement).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org