[GitHub] helix pull request #82: Add Test for Batch Message ThreadPool

GitHub user dasahcc opened a pull request: https://github.com/apache/helix/pull/82 Add Test for Batch Message ThreadPool Add Test for Batch Message ThreadPool. For easy testing, change the private type to default type. You can merge this pull request into a Git repository by

[jira] [Commented] (HELIX-640) Support job level expiration.

[ https://issues.apache.org/jira/browse/HELIX-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954192#comment-15954192 ] Weihan Kong commented on HELIX-640: --- [~dasahcc] Could you assign this ticket to me? I'll try to merge it.

Re: [ANNOUNCE] New committer: Junkai Xue

Thanks! Very glad to join the team! Best, Junkai On Mon, Apr 3, 2017 at 11:01 AM, kishore g wrote: > Yay!. Welcome to the club. > > On Mon, Apr 3, 2017 at 10:45 AM, Lei Xia wrote: > > > The Project Management Committee (PMC) for Apache Helix has asked

Re: [GitHub] helix issue #81: Creating a separate threadpool to handle batchMessages

Sure! Will add that. On Mon, Apr 3, 2017 at 12:21 PM, kishore g wrote: > +1 on adding an api to enable/disable this at a cluster level. > > On Mon, Apr 3, 2017 at 12:18 PM, dasahcc wrote: > > > Github user dasahcc commented on the issue: > > > >

[GitHub] helix pull request #81: Creating a separate threadpool to handle batchMessag...

Github user asfgit closed the pull request at: https://github.com/apache/helix/pull/81 --- 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

Re: [GitHub] helix issue #81: Creating a separate threadpool to handle batchMessages

+1 on adding an api to enable/disable this at a cluster level. On Mon, Apr 3, 2017 at 12:18 PM, dasahcc wrote: > Github user dasahcc commented on the issue: > > https://github.com/apache/helix/pull/81 > > Looks good to me! I will do the following things for

[GitHub] helix issue #81: Creating a separate threadpool to handle batchMessages

Github user dasahcc commented on the issue: https://github.com/apache/helix/pull/81 Looks good to me! I will do the following things for corresponding change: 1. Will add a test for this. 2. Will provide an API in HelixManager for enabling batch message and support

Re: [ANNOUNCE] New committer: Junkai Xue

Yay!. Welcome to the club. On Mon, Apr 3, 2017 at 10:45 AM, Lei Xia wrote: > The Project Management Committee (PMC) for Apache Helix has asked Junkai > Xue > to become a committer and we are pleased to announce that he has accepted. > > Being a committer enables easier

[ANNOUNCE] New committer: Junkai Xue

The Project Management Committee (PMC) for Apache Helix has asked Junkai Xue to become a committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable

helix - Build # 1351 - Failure

The Apache Jenkins build system has built helix (build #1351) Status: Failure Check console output at https://builds.apache.org/job/helix/1351/ to view the results.

[GitHub] helix pull request #81: Creating a separate threadpool to handle batchMessag...

GitHub user kishoreg opened a pull request: https://github.com/apache/helix/pull/81 Creating a separate threadpool to handle batchMessages batchMessages were using the same threadpool as sub tasks. This works as long the thread pool size is greater than the number of messages with