accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From keith-turner <>
Subject [GitHub] accumulo pull request: ACCUMULO-3509: Allow cleanup state to be ke...
Date Mon, 04 Jan 2016 16:59:31 GMT
Github user keith-turner commented on a diff in the pull request:
    --- Diff: server/tserver/src/main/java/org/apache/accumulo/tserver/tablet/
    @@ -38,100 +40,126 @@
       private ScanDataSource isolatedDataSource;
       private boolean sawException = false;
       private boolean scanClosed = false;
    +  protected Semaphore scannerSemaphore;
       Scanner(Tablet tablet, Range range, ScanOptions options) {
         this.tablet = tablet;
         this.range = range;
         this.options = options;
    +    scannerSemaphore = new Semaphore(1, true);
    --- End diff --
    This semaphore replaces a synchronized block with a fair semaphore.  AFAICT from searching
around on the web, synchronized blocks are not fair.   Do we need fairness here?  The javadocs
say its more expensive.   If its not needed, not sure should set it.
    I was trying to determine the difference between the semaphore and a lock for this case.
 It seems like the only difference is re-entrance, which it does not seem is needed in this

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message