Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: dlmarion <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
Message-ID: <git-pr-75-accumulo@git.apache.org>
Subject: [GitHub] accumulo pull request: ACCUMULO-1755: Modified TSBW so that
 all cl...
Content-Type: text/plain
Date: Fri, 26 Feb 2016 16:35:19 +0000 (UTC)

GitHub user dlmarion opened a pull request:

    https://github.com/apache/accumulo/pull/75

    ACCUMULO-1755: Modified TSBW so that all client threads will not bloc…

    I ditched review board and went back to the drawing board.
    
    Before this change all client threads that were adding mutations to a BatchWriter would block
    when the mutations needed to be written to the tablet servers. This change gives each client
    thread their own MutationWriter object using a ThreadLocal. With this change only one client
    should block on adding the mutations to the sendThreadPool object, and allows the other client
    threads to push mutations onto a new MutationSet.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/accumulo ACCUMULO-1755

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/accumulo/pull/75.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #75
    
----
commit 9bd48cdbd25a7baf19bbda007a8e36f8ec81cf07
Author: Dave Marion <dlmarion@apache.org>
Date:   2016-02-26T16:26:53Z

    ACCUMULO-1755: Modified TSBW so that all client threads will not block on binMutations
    
    Before this change all client threads that were adding mutations to a BatchWriter would block
    when the mutations needed to be written to the tablet servers. This change gives each client
    thread their own MutationWriter object using a ThreadLocal. With this change only one client
    should block on adding the mutations to the sendThreadPool object, and allows the other client
    threads to push mutations onto a new MutationSet.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---