[GitHub] [accumulo] keith-turner commented on pull request #3644: ReentrantLock.getOwner() to help clean up scan sessions

["keith-turner (via GitHub)" <gi...@apache.org>]

keith-turner commented on PR #3644:
URL: https://github.com/apache/accumulo/pull/3644#issuecomment-1650148155

   > @keith-turner - would running your new scan consistency test for an extended period also stress these lock changes?
   
   The test will definitely stress the read method modified in this PR.  However I do not think it will stress the close method. 
   
   I think to stress this the test would need to do the following
   
    1. Start a scan over range x to +inf
    2. Do not read all data, leaving a scan session on the tserver to be cleaned up
   
   I don't think the test does this, but it should if it does not.  Some of its scans should randomly be open ended and not read all the data.  On a long running test this would trigger the session clean up that calls close on an idle session.


-- 
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