Re: [VOTE] Apache Helix 1.2.0 Release

[Lei Xia]

+1

On Mon, May 1, 2023 at 10:17 AM Wang Jiajun  wrote:

> +1
>
> Best Regards,
> Jiajun
>
>
> On Thu, Apr 27, 2023 at 7:53 PM Quincy Qu  wrote:
>
> > +1
> >
> > On Thu, Apr 27, 2023 at 19:13 Junkai Xue  wrote:
> >
> > > Hi,
> > >
> > > This is to call for a vote on releasing the following candidate as
> > > Apache Helix 1.2.0. This is the 27th release of Helix as an Apache
> > > project, as well as the 23rd release as a top-level Apache project.
> > >
> > > Apache Helix is a generic cluster management framework that makes it
> > > easy to build partitioned and replicated, fault-tolerant and scalable
> > > distributed systems.
> > >
> > > Release notes:
> > > https://helix.apache.org/1.2.0-docs/releasenotes/release-1.2.0.html
> > > Release artifacts:
> > > https://repository.apache.org/content/repositories/orgapachehelix-1057
> > >
> > > Distribution:
> > > * binaries:
> https://dist.apache.org/repos/dist/dev/helix/1.2.0/binaries/*
> > > sources:https://dist.apache.org/repos/dist/dev/helix/1.2.0/src/
> > > The 1.2.0 release
> > > tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-1.2.0
> > > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> > > Please vote on the release. The vote will be open for at least 72
> hours.
> > >
> > > [+1] -- "YES, release"
> > > [0] -- "No opinion"
> > > [-1] -- "NO, do not release"
> > >
> > > Thanks,
> > > The Apache Helix Team
> > >
> >
>
-- 
Lei Xia

Re: [VOTE] Apache Helix 1.1.0 Release

[Lei Xia]

+1

On Wed, Dec 14, 2022 at 12:46 PM Wang Jiajun  wrote:

> +1
>
> Best Regards,
> Jiajun
>
>
> On Tue, Dec 13, 2022 at 6:25 PM Junkai Xue  wrote:
>
> > Hi,
> >
> > This is to call for a vote on releasing the following candidate as
> > Apache Helix 1.1.0. This is the 26th release of Helix as an Apache
> > project, as well as the 22nd release as a top-level Apache project.
> >
> > Apache Helix is a generic cluster management framework that makes it
> > easy to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> > Release notes:
> > https://helix.apache.org/1.1.0-docs/releasenotes/release-1.1.0.html
> > Release artifacts:
> > https://repository.apache.org/content/repositories/orgapachehelix-1055
> >
> > Distribution:
> > * binaries:https://dist.apache.org/repos/dist/dev/helix/1.1.0/binaries/*
> > sources:https://dist.apache.org/repos/dist/dev/helix/1.1.0/src/
> > The 1.1.0 release
> > tag:
> >
> https://gitbox.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-1.1.0
> >
> > KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> > [+1] -- "YES, release"
> > [0] -- "No opinion"
> > [-1] -- "NO, do not release"
> >
> > Thanks,
> > The Apache Helix Team
> >
>
-- 
Lei Xia

Re: [VOTE] Apache Helix 1.0.3 Release

[Lei Xia]

+1

On Mon, Apr 18, 2022 at 3:36 PM Hunter Lee  wrote:

> +1
>
> On Mon, Apr 18, 2022 at 6:26 PM Junkai Xue  wrote:
>
> > Hi,
> >
> > This is to call for a vote on releasing the following candidate as
> > Apache Helix 1.0.3. This is the 24th release of Helix as an Apache
> > project, as well as the 20th release as a top-level Apache project.
> >
> > Apache Helix is a generic cluster management framework that makes it
> > easy to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> > (*ATTENTION: Due to webpage publishing problem, we use source code for
> > release to unblock the Apache release. We are asking Apache Folks
> > helping us now!*)
> > Release notes:
> >
> https://github.com/apache/helix/blob/master/website/1.0.3/src/site/apt/releasenotes/release-1.0.3.apt
> >
> > Release artifacts:
> > https://repository.apache.org/content/repositories/orgapachehelix-1050
> >
> > Distribution:
> > * binaries:https://dist.apache.org/repos/dist/dev/helix/1.0.3/binaries/
> > * sources:https://dist.apache.org/repos/dist/dev/helix/1.0.3/src/
> >
> > The [VERSION] release
> > tag:
> >
> https://gitbox.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-1.0.3
> >
> > KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> > [+1] -- "YES, release"
> > [0] -- "No opinion"
> > [-1] -- "NO, do not release"
> >
> > Thanks,
> > The Apache Helix Team
> >
>

Re: [VOTE] Apache Helix 0.9.10 Release

[Lei Xia]

+1

On Tue, Apr 5, 2022 at 10:42 AM Hunter Lee  wrote:

> +1
>
> On Tue, Apr 5, 2022 at 1:10 PM Junkai Xue  wrote:
>
> > Hi,
> >
> > We would like to do a retrospective vote for Apache Helix 0.9.10 since
> > 0.9.10 was a replacement of 0.9.9, which did not reflect the latest
> change
> > when it was released.
> >
> > Content wise, there is no change on release note for 0.9.10 from 0.9.9.
> >
> > * binaries:
> > https://dist.apache.org/repos/dist/release/helix/0.9.10/binaries/
> >
> > * sources:
> > https://dist.apache.org/repos/dist/release/helix/0.9.10/src/
> >
> > Thanks,
> >
> > The Apache Helix Team
> >
>
-- 
Lei Xia

Re: [VOTE] Apache Helix 0.9.9 Release

[Lei Xia]

+1

On Mon, Nov 15, 2021 at 12:27 PM kishore g  wrote:

> +1
>
> On Mon, Nov 15, 2021 at 12:19 PM Junkai Xue  wrote:
>
> > Hi,
> >
> > This is to call for a vote on releasing the following candidate as
> > Apache Helix 0.9.9. This is the 23rd release of Helix as an Apache
> > project, as well as the 19th release as a top-level Apache project.
> >
> > Apache Helix is a generic cluster management framework that makes it
> > easy to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> > Release notes:
> >- Add additional ZK serializer configuration to active ZNRecord
> > compression even if the node size is smaller than write size limit.
> >
> > Release artifacts:
> > https://repository.apache.org/content/repositories/orgapachehelix-1047
> > Distribution:
> > * binaries:https://dist.apache.org/repos/dist/dev/helix/0.9.9/binaries/*
> > sources:https://dist.apache.org/repos/dist/dev/helix/0.9.9/src/
> > The 0.9.9 release
> > tag:
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.9
> > KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> > [+1] -- "YES, release"
> > [0] -- "No opinion"
> > [-1] -- "NO, do not release"
> >
> > Thanks,
> > The Apache Helix Team
> >
>

Re: [VOTE] Apache Helix 1.0.2 Release

[Lei Xia]

+1

On Thu, Aug 19, 2021 at 1:24 PM Hunter Lee  wrote:

> +1
>
> On Thu, Aug 19, 2021 at 2:34 PM Junkai Xue  wrote:
>
> > Hi,
> >
> >
> > This is to call for a vote on releasing the following candidate as Apache
> > Helix 1.0.2. This is the 22nd release of Helix as an Apache project, as
> > well as the 18th release as a top-level Apache project.
> >
> >
> > Apache Helix is a generic cluster management framework that makes it easy
> > to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> >
> > Release notes:
> >
> > https://helix.apache.org/1.0.2-docs/releasenotes/release-1.0.2.html
> >
> >
> > Release artifacts:
> >
> > https://repository.apache.org/content/repositories/orgapachehelix-1046
> >
> >
> > Distribution:
> >
> > * binaries:
> >
> > https://dist.apache.org/repos/dist/dev/helix/1.0.2/binaries/
> >
> > * sources:
> >
> > https://dist.apache.org/repos/dist/dev/helix/1.0.2/src/
> >
> >
> > The 1.0.2 release tag:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-
> > 1.0.2
> >
> >
> > KEYS file available here:
> >
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> >
> > [+1] -- "YES, release"
> >
> > [0] -- "No opinion"
> >
> > [-1] -- "NO, do not release"
> >
> >
> > Thanks,
> >
> > The Apache Helix Team
> >
>

Re: [VOTE] Apache Helix 1.0.2 Release

[Lei Xia]

+1

On Tue, Jun 8, 2021 at 8:34 PM Junkai Xue  wrote:

> Yes. I also need to work on the sign part and update our helix release step
> doc.
> Please take your time!
>
> Best,
>
> Junkai
>
> On Tue, Jun 8, 2021 at 8:25 PM Justin Mclean  wrote:
>
> > HI,
> >
> > > Thanks Justin! Could you please help with the license part? Highly
> > > appreciated.
> >
> > Sure might take me a couple of days if that's OK.
> >
> > > Also, could you please share any docs about the Sha-1 related docs for
> > > guidance?
> >
> > See https://infra.apache.org/release-distribution#sigs-and-sums
> >
> > Thanks,
> > Justin
> >
>
>
> --
> Junkai Xue
>

Re: [VOTE] Apache Helix 0.9.9 Release

[Lei Xia]

+1

On Fri, Nov 20, 2020 at 8:04 PM Xue Junkai  wrote:

> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.9.9. This is the 24th release of Helix as an Apache project, as
> well as the 20th release as a top-level Apache project.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
> Release notes:
> http://helix.apache.org/0.9.9-docs/releasenotes/release-0.9.9.html
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-1043
>
> Distribution:
> * binaries: https://dist.apache.org/repos/dist/dev/helix/0.9.9/binaries/
> * sources: https://dist.apache.org/repos/dist/dev/helix/0.9.9/src/
>
> The 0.9.9 release tag:
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.9
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
> Please vote on the release.
> The vote will be open for at least 72 hours.
> [+1] -- "YES, release"
> [0] -- "No opinion"
> [-1] -- "NO, do not release"
>
> Thanks,
>
> The Apache Helix Team
>

Re: [VOTE] Apache Helix 0.9.8 Release

[Lei Xia]

+1

On Wed, Oct 14, 2020 at 9:03 PM Hunter Lee  wrote:

> +1. Thanks for putting this together!
>
> On Wed, Oct 14, 2020 at 6:25 PM Wang Jiajun 
> wrote:
>
> > Hi,
> >
> > This is to call for a vote on releasing the following candidate as Apache
> > Helix 0.9.8. This is the 23rd release of Helix as an Apache project, as
> > well as the 19th release as a top-level Apache project. This release is
> > supporting the customers who are using the 0.9 series.
> >
> > Apache Helix is a generic cluster management framework that makes it easy
> > to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> > Release notes:
> > https://helix.apache.org/0.9.8-docs/releasenotes/release-0.9.8.html
> >
> > Release artifacts:
> > https://repository.apache.org/content/repositories/orgapachehelix-1042/
> >
> > Distribution:
> > * binaries:
> > https://dist.apache.org/repos/dist/dev/helix/0.9.8/binaries/
> > * sources:
> > https://dist.apache.org/repos/dist/dev/helix/0.9.8/src/
> >
> > The 0.9.8 release tag:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.8
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> > [+1] -- "YES, release"
> > [0] -- "No opinion"
> > [-1] -- "NO, do not release"
> >
> > Thanks,
> > The Apache Helix Team
> >
>

[jira] [Commented] (HELIX-694) Cannot Add a Cluster

[Lei Xia (Jira)]

[ 
https://issues.apache.org/jira/browse/HELIX-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169000#comment-17169000
 ] 

Lei Xia commented on HELIX-694:
---

[~dasahcc] Has this been fixed in lastest 1.0.1 release?
 * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13306177]

> Cannot Add a Cluster
> 
>
> Key: HELIX-694
> URL: https://issues.apache.org/jira/browse/HELIX-694
> Project: Apache Helix
>  Issue Type: Bug
>Reporter: Lahiru Jayasekara
>Priority: Blocker
>
> When adding a cluster using the command,
> {{./helix-admin.sh --zkSvr localhost:2181 --addCluster MyCluster}}
> There will be an exception generated as follows, 
> Exception in thread "main" org.apache.helix.HelixException: cluster MyCluster 
> is not setup yet
>     at 
> org.apache.helix.manager.zk.ZKHelixAdmin.addStateModelDef(ZKHelixAdmin.java:708)
>     at 
> org.apache.helix.tools.ClusterSetup.addStateModelDef(ClusterSetup.java:343)
>     at org.apache.helix.tools.ClusterSetup.addCluster(ClusterSetup.java:152)
>     at 
> org.apache.helix.tools.ClusterSetup.processCommandLineArgs(ClusterSetup.java:1009)
>     at org.apache.helix.tools.ClusterSetup.main(ClusterSetup.java:1454)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (HELIX-823) run-helix-controller.sh command gives error

[Lei Xia (Jira)]

[ 
https://issues.apache.org/jira/browse/HELIX-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168999#comment-17168999
 ] 

Lei Xia commented on HELIX-823:
---

[~dasahcc] Has this been fixed in lastest 1.0.1 release?

> run-helix-controller.sh command gives error
> ---
>
> Key: HELIX-823
> URL: https://issues.apache.org/jira/browse/HELIX-823
> Project: Apache Helix
>  Issue Type: Bug
>  Components: helix-core
> Environment: Linux Red Hat 4.8.5-4
>Reporter: anil
>Priority: Blocker
>
> Download helix verversion 1.0.0 binary and setup two node cluster. Every 
> thing work fine.
> but when fire below command 
> ./run-helix-controller.sh --zkSvr localhost:2181 --cluster jbpm-cluster
> It gives error - 
> sterName:jbpm-cluster, controllerName:null, mode:STANDALONE
> Exception in thread "main" *java.lang.NoSuchFieldError: Rebalancer*
>  at org.apache.helix.InstanceType.(InstanceType.java:39)
>  at 
> org.apache.helix.controller.HelixControllerMain.startHelixController(HelixControllerMain.java:156)
>  at 
> org.apache.helix.controller.HelixControllerMain.main(HelixControllerMain.java:212)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (HELIX-824) best work shoes for overweight

[Lei Xia (Jira)]

[ 
https://issues.apache.org/jira/browse/HELIX-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168998#comment-17168998
 ] 

Lei Xia commented on HELIX-824:
---

Spam, close it.

> best work shoes for overweight
> --
>
> Key: HELIX-824
> URL: https://issues.apache.org/jira/browse/HELIX-824
> Project: Apache Helix
>  Issue Type: Bug
>Reporter: Irinano
>Priority: Major
>
> When choosing shoes, you need to consider all the features of your body and 
> legs. After all, unsuitable shoes will not only wear out quickly but also can 
> cause you inconvenience. Therefore, for people who are overweight, the [best 
> work shoes for 
> overweight|https://gym-expert.com/best-walking-shoes-for-overweight-walkers/] 
> are best suited.
>   
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Apache Helix 1.0.1 Release

[Lei Xia]

+1

On Wed, Jul 1, 2020 at 2:51 PM Xue Junkai  wrote:

> Hi,
>
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 1.0.1. This is the 21st release of Helix as an Apache project, as
> well as the 17th release as a top-level Apache project.
>
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
>
> Release notes:
>
> http://helix.apache.org/1.0.1-docs/releasenotes/release-1.0.1.html
>
>
> Release artifacts:
>
> https://repository.apache.org/content/repositories/orgapachehelix-1040
>
>
> Distribution:
>
> * binaries:
>
> https://dist.apache.org/repos/dist/dev/helix/1.0.1/binaries/
>
> * sources:
>
> https://dist.apache.org/repos/dist/dev/helix/1.0.1/src/
>
>
> The 1.0.1 release tag:
>
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-1.0.1
>
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
>
> [+1] -- "YES, release"
>
> [0] -- "No opinion"
>
> [-1] -- "NO, do not release"
>
>
> Thanks,
>
> The Apache Helix Team
>

Re: [VOTE] Apache Helix 0.9.7 Release

[Lei Xia]

+1

On Mon, May 11, 2020 at 5:25 PM Hunter Lee  wrote:

> +1
>
> On Mon, May 11, 2020 at 4:23 PM Xue Junkai  wrote:
>
> > Hi,
> >
> >
> > This is to call for a vote on releasing the following candidate as Apache
> > Helix 0.9.7. This is the 22nd release of Helix as an Apache project, as
> > well as the 18th release as a top-level Apache project. This release is
> > supporting the customers are using 0.9 series.
> >
> >
> > Apache Helix is a generic cluster management framework that makes it easy
> > to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> >
> > Release notes:
> >
> > http://helix.apache.org/0.9.7-docs/releasenotes/release-0.9.7.html
> >
> >
> > Release artifacts:
> >
> > https://repository.apache.org/content/repositories/orgapachehelix-1039
> >
> >
> > Distribution:
> >
> > * binaries:
> >
> > https://dist.apache.org/repos/dist/dev/helix/0.9.7/binaries/
> >
> > * sources:
> >
> > https://dist.apache.org/repos/dist/dev/helix/0.9.7/src/
> >
> >
> > The 0.9.7 release tag:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.7
> >
> >
> > KEYS file available here:
> >
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> >
> > [+1] -- "YES, release"
> >
> > [0] -- "No opinion"
> >
> > [-1] -- "NO, do not release"
> >
> >
> > Thanks,
> >
> > The Apache Helix Team
> >
>


-- 
Lei Xia

Re: [VOTE] Apache Helix 1.0.0 Release

[Lei Xia]

+1

On Tue, May 5, 2020 at 11:50 AM Wang Jiajun  wrote:

> +1
>
> Best Regards,
> Jiajun
>
>
> On Mon, May 4, 2020 at 5:42 PM Xue Junkai  wrote:
>
> > Hi,
> >
> >
> > This is to call for a vote on releasing the following candidate as Apache
> > Helix 1.0.0. This is the 21st release of Helix as an Apache project, as
> > well as the [16th release as a top-level Apache project.
> >
> >
> > Apache Helix is a generic cluster management framework that makes it easy
> > to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> >
> > Release notes:
> >
> > http://helix.apache.org/1.0.0-docs/releasenotes/release-1.0.0.html
> >
> >
> > Release artifacts:
> >
> > https://repository.apache.org/content/repositories/orgapachehelix-1037
> >
> >
> > Distribution:
> >
> > * binaries:
> >
> > https://dist.apache.org/repos/dist/dev/helix/1.0.0/binaries/
> >
> > * sources:
> >
> > https://dist.apache.org/repos/dist/dev/helix/1.0.0/src/
> > 
> >
> >
> > The 1.0.0 release tag:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-1.0.0
> >
> >
> > KEYS file available here:
> >
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> >
> > [+1] -- "YES, release"
> >
> > [0] -- "No opinion"
> >
> > [-1] -- "NO, do not release"
> >
> >
> > Thanks,
> >
> > The Apache Helix Team
> >
>

Re: [VOTE] Apache Helix 0.9.4 Release

[Lei Xia]

+1


Lei

On Wed, Jan 22, 2020 at 6:30 PM Hunter Lee  wrote:

> It is up now.
>
> Hunter
>
> On Wed, Jan 22, 2020 at 8:48 AM Lei Xia  wrote:
>
> > Thanks Hunter, the release notes link seems not work?
> >
> >
> > Lei
> >
> > On Tue, Jan 21, 2020 at 11:40 PM Hunter Lee  wrote:
> >
> > > Hi,
> > >
> > > This is to call for a vote on releasing the following candidate as
> Apache
> > > Helix 0.9.4. This is the 19th release of Helix as an Apache project, as
> > > well as the 15th release as a top-level Apache project.
> > >
> > > Apache Helix is a generic cluster management framework that makes it
> easy
> > > to build partitioned and replicated, fault-tolerant and scalable
> > > distributed systems.
> > >
> > > Release notes:
> > > https://helix.apache.org/0.9.4-docs/releasenotes/release-0.9.4.html
> > >
> > > Release artifacts:
> > >
> https://repository.apache.org/content/repositories/orgapachehelix-1036/
> > >
> > > Distribution:
> > > * binaries:
> > > https://dist.apache.org/repos/dist/dev/helix/0.9.4/binaries/
> > > * sources:
> > > https://dist.apache.org/repos/dist/dev/helix/0.9.4/src/
> > >
> > > The 0.9.4 release tag:
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.4
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/dev/helix/KEYS
> > >
> > > Please vote on the release. The vote will be open for at least 72
> hours.
> > >
> > > [+1] -- "YES, release"
> > > [0] -- "No opinion"
> > > [-1] -- "NO, do not release"
> > >
> > > Thanks,
> > > The Apache Helix Team
> > >
> >
>

Re: [VOTE] Apache Helix 0.9.4 Release

[Lei Xia]

Thanks Hunter, the release notes link seems not work?


Lei

On Tue, Jan 21, 2020 at 11:40 PM Hunter Lee  wrote:

> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.9.4. This is the 19th release of Helix as an Apache project, as
> well as the 15th release as a top-level Apache project.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
> Release notes:
> https://helix.apache.org/0.9.4-docs/releasenotes/release-0.9.4.html
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-1036/
>
> Distribution:
> * binaries:
> https://dist.apache.org/repos/dist/dev/helix/0.9.4/binaries/
> * sources:
> https://dist.apache.org/repos/dist/dev/helix/0.9.4/src/
>
> The 0.9.4 release tag:
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.4
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
> [+1] -- "YES, release"
> [0] -- "No opinion"
> [-1] -- "NO, do not release"
>
> Thanks,
> The Apache Helix Team
>

Re: [VOTE] Apache Helix 0.9.1 Release

[Lei Xia]

+1

On Wed, Aug 14, 2019 at 2:08 PM Xue Junkai  wrote:

> +1
>
> On Wed, Aug 14, 2019 at 2:07 PM Wang Jiajun 
> wrote:
>
> > Hi,
> >
> > This is to call for a vote on releasing the following candidate as Apache
> > Helix 0.9.1. This is the 18th release of Helix as an Apache project, as
> > well as the 14th release as a top-level Apache project.
> >
> > Apache Helix is a generic cluster management framework that makes it easy
> > to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> > Release notes:
> > https://helix.apache.org/0.9.1-docs/releasenotes/release-0.9.1.html
> >
> > Release artifacts:
> > https://repository.apache.org/content/repositories/orgapachehelix-1032/
> >
> > Distribution:
> > * binaries:
> > https://dist.apache.org/repos/dist/dev/helix/0.9.1/binaries/
> > * sources:
> > https://dist.apache.org/repos/dist/dev/helix/0.9.1/src/
> >
> > The 0.9.1 release tag:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.1
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> > [+1] -- "YES, release"
> > [0] -- "No opinion"
> > [-1] -- "NO, do not release"
> >
> > Thanks,
> > The Apache Helix Team
> >
>
>
> --
> Junkai Xue
>

Re: [VOTE] Apache Helix 0.9.0 Release

[Lei Xia]

+1

On Tue, Jun 11, 2019 at 3:07 PM Hunter Lee  wrote:

> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.9.0. This is the 17th release of Helix as an Apache project, as
> well as the 13th release as a top-level Apache project.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
> Release notes:
> https://helix.apache.org/0.9.0-docs/releasenotes/release-0.9.0.html
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-1029/
> <
> https://repository.apache.org/content/repositories/orgapachehelix-%5B%5D
> >
>
> Distribution:
> * binaries:
> https://dist.apache.org/repos/dist/dev/helix/0.9.0/binaries/
> 
> * sources:
> https://dist.apache.org/repos/dist/dev/helix/0.9.0/src/
> 
>
> The [VERSION] release tag:
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.9.0
> <
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-[VERSION]
> >
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
> [+1] -- "YES, release"
> [0] -- "No opinion"
> [-1] -- "NO, do not release"
>
> Thanks,
> The Apache Helix Team
>

Re: Zookeeper connection errors in Helix Controller

[Lei Xia]

Before our new release is out,  if you see that is a problem in your prod
deployment,  one thing you may try is to add a newer zookeeper version as
an explicit dependency in your project, then during the build time,  maven
(or other build tool) will pick new version instead the one specified in
helix.  This could  be a workaround for you now.


Lei

On Fri, May 31, 2019 at 10:57 PM DImuthu Upeksha 
wrote:

> Hi Lee,
>
> Understood and thanks for the heads up. We are currently in middle of
> production deployment with 0.8.2 and most of the users are already notified
> with the schedule.  Basically we are a happy with the stability and
> functional correctness of 0.8.2 except for above mentioned case where we
> pushed the cluster above its limits in stress testing. So we will go with
> this version for this deployment and once you have released the new
> version, we will perform the functional tests and stress tests on it within
> our staging environment and if it looks good, we will patch it to the
> production environment.
>
> Thanks
> Dimuthu
>
> On Fri, May 31, 2019 at 5:07 PM Hunter Lee  wrote:
>
> > Hey Dimuthu -
> >
> > We are actually in the process of preparing a new release, and this will
> > come with the previously mentioned bug fixes in Task Framework. It also
> > contains various ZK-related fixes - I don't know what your deployment
> > schedule is but it might be worth the wait of another week or so.
> >
> > Hunter
> >
> > On Fri, May 31, 2019 at 10:27 AM DImuthu Upeksha <
> > dimuthu.upeks...@gmail.com>
> > wrote:
> >
> > > Now I'm seeing following error in controller log. Restarting the
> > controller
> > > fixed the issue. We are time to time seeing this in controller with zk
> > > connection issues. Is this also something to do with zk client version?
> > >
> > > 2019-05-31 13:21:46,669 [Thread-0-SendThread(localhost:2181)] WARN
> > >  o.apache.zookeeper.ClientCnxn  - Session 0x16b0ebbee1d000e for server
> > > localhost/127.0.0.1:2181, unexpected error, closing socket connection
> > and
> > > attempting reconnect
> > > java.io.IOException: Broken pipe
> > > at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
> > > at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
> > > at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
> > > at sun.nio.ch.IOUtil.write(IOUtil.java:65)
> > > at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
> > > at
> > >
> >
> org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:102)
> > > at
> > >
> > >
> >
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:291)
> > > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
> > >
> > > Thanks
> > > Dimuthu
> > >
> > > On Fri, May 31, 2019 at 1:14 PM DImuthu Upeksha <
> > > dimuthu.upeks...@gmail.com>
> > > wrote:
> > >
> > > > Hi Lei,
> > > >
> > > > We use 0.8.2. We initially had 0.8.4 but it contains an issue with
> task
> > > > retry logic so we downgraded to 0.8.2. We are planning to go into
> > > > production with 0.8.2 by next week so can you please advice a better
> > way
> > > to
> > > > solve this without upgrading to 0.8.4.
> > > >
> > > > Thanks
> > > > Dimuthu
> > > >
> > > > On Fri, May 31, 2019 at 1:04 PM Lei Xia  wrote:
> > > >
> > > >> Which Helix version do you use?  This may caused by this Zookeeper
> > bug (
> > > >> https://issues.apache.org/jira/browse/ZOOKEEPER-706).  We have
> > upgraded
> > > >> ZkClient in later Helix versions.
> > > >>
> > > >>
> > > >> Lei
> > > >>
> > > >> On Fri, May 31, 2019 at 7:52 AM DImuthu Upeksha <
> > > >> dimuthu.upeks...@gmail.com> wrote:
> > > >>
> > > >>> Hi Folks,
> > > >>>
> > > >>> I'm getting following error in controller log and seems like
> > controller
> > > >>> is
> > > >>> not moving froward after that point
> > > >>>
> > > >>> 2019-05-31 10:47:37,084 [main] INFO  o.a.a.h.i.c.HelixController  -
> > > >>> Starting helix controller
> > > >>> 2019-05-31 10:47:37,089 [main] INFO
> o.a.a.c.u.ApplicationSettings  -
> > > >>> Se

Re: [ANNOUNCE] New Committer: Hunter Lee

[Lei Xia]

Welcome, Hunter!

On Thu, Mar 28, 2019 at 5:54 PM Xue Junkai  wrote:

> Hi, All
>
>
>   The Project Management Committee (PMC) for Apache Helix has asked Hunter
> Lee 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
> better productivity.
>
>
>   Welcome Hunter!
>
>
> Helix Team
>

Re: Proposal: Moving Helix to Java 1.8 and upgrading Maven version

[Lei Xia]

+1

On Sun, Mar 24, 2019 at 10:56 PM Hunter Lee  wrote:

> I would like to start a discussion on making Java 8 a minimum requirement
> and upgrading the Maven version for Helix's next feature release. I'd like
> to see how people feel about it.
>
> Did some homework on this and dug up a few precedences that are also
> top-level Apache projects dependent on ZooKeeper. The following
> documentation lists many pros of moving to Java 8 as well, many of which I
> will not include in this email for the sake of brevity (see the links
> below).
>
> Open-source community discussions for
>
> Apache Samza: link1
> <
> https://mail-archives.apache.org/mod_mbox/samza-dev/201610.mbox/%3CCAHUevGGnOQD_VmLWEdpFNq3Lv%2B6gQQmw_JKx9jDr5Cw%2BxFfGtQ%40mail.gmail.com%3E
> >
>
> Apache Kafka: link1  link2
> <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-118%3A+Drop+Support+for+Java+7
> >
>
> I've also had informal chats with PMC members of both Samza and Kafka about
> this specifically for more context, and from what they said, the transition
> has been very smooth.
>
> Here are Helix-specific reasons why I think the move would be beneficial:
>
> - Other Apache open-source platforms built on Helix such as Pinot and
> Gobblin all cite Java 8 as the minimum requirement. Building Helix in Java
> 8 will help contributors of Helix respond to feature/debugging requests in
> a more timely manner (without having to jump back and forth between Java 7
> and 8).
>
> - The recent change in Maven
> <
> https://central.sonatype.org/articles/2018/May/04/discontinued-support-for-tlsv11-and-below/
> >
> (Central
> Repository). Long story short, Helix build using JDK 7 on Maven 3.0.5+ will
> fail. Using JDK 8 solves this problem.
>
> The cost of moving to Java 8 is relatively low. Java 7 is forward
> compatibile with Java 8. However, there may be some backporting work needed
> due to the way Java 8 changed the ConcurrentHashMap implementation.
>
> As for Maven, Helix's requirement currently is 3.0.4 which is a version
> just below the required version other dependent Apache projects use (say,
> Pinot ). Again,
> to save the contributors the trouble of having to navigate between Maven
> versions, I am also suggesting that we update this requirement.
>
>
> -Hunter
>

Re: [VOTE] Apache Helix 0.8.4 Release

[Lei Xia]

+1

On Wed, Feb 27, 2019 at 2:07 PM Xue Junkai  wrote:

> Hi,
>
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.8.4. This is the 16th release of Helix as an Apache project, as
> well as the 12th release as a top-level Apache project.
>
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
>
> Release notes:
>
> *https://helix.apache.org/0.8.4-docs/releasenotes/release-0.8.4.html
> *
>
>
> Release artifacts:
>
> https://repository.apache.org/content/repositories/orgapachehelix-1026
>
>
> Distribution:
>
> * binaries:
>
> *https://dist.apache.org/repos/dist/dev/helix/0.8.4/binaries/
> *
>
> * sources:
>
> https://dist.apache.org/repos/dist/dev/helix/0.8.4/src/
>
>
> The 0.8.4 release tag:
>
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.8.4
>
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
>
> [+1] -- "YES, release"
>
> [0] -- "No opinion"
>
> [-1] -- "NO, do not release"
>
>
> Thanks,
>
> The Apache Helix Team
>

Re: [VOTE] Apache Helix 0.8.3 Release

[Lei Xia]

+1

On Mon, Feb 4, 2019 at 6:56 PM Wang Jiajun  wrote:

> ＋1
>
> On Feb 4, 2019 2:43 PM, "Hao Zhang"  wrote:
>
> > +1
> > On Mon, Feb 4, 2019 at 14:23 Xue Junkai  wrote:
> >
> > > Hi,
> > >
> > >
> > > This is to call for a vote on releasing the following candidate as
> Apache
> > > Helix 0.8.3. This is the 15th release of Helix as an Apache project, as
> > > well as the 11th release as a top-level Apache project.
> > >
> > >
> > > Apache Helix is a generic cluster management framework that makes it
> easy
> > > to build partitioned and replicated, fault-tolerant and scalable
> > > distributed systems.
> > >
> > >
> > > Release notes:
> > >
> > > *https://helix.apache.org/0.8.3-docs/releasenotes/release-0.8.3.html
> > > <https://helix.apache.org/0.8.3-docs/releasenotes/release-0.8.3.html>*
> > >
> > >
> > > Release artifacts:
> > >
> > > https://repository.apache.org/content/repositories/orgapachehelix-1022
> > >
> > >
> > > Distribution:
> > >
> > > * binaries:
> > >
> > > *https://dist.apache.org/repos/dist/dev/helix/0.8.3/binaries/
> > > <https://dist.apache.org/repos/dist/dev/helix/0.8.3/binaries/>*
> > >
> > > * sources:
> > >
> > > https://dist.apache.org/repos/dist/dev/helix/0.8.3/src/
> > >
> > >
> > > The 0.8.3 release tag:
> > >
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=
> > refs/tags/helix-
> > > 0.8.3
> > >
> > >
> > > KEYS file available here:
> > >
> > > https://dist.apache.org/repos/dist/dev/helix/KEYS
> > >
> > >
> > > Please vote on the release. The vote will be open for at least 72
> hours.
> > >
> > >
> > > [+1] -- "YES, release"
> > >
> > > [0] -- "No opinion"
> > >
> > > [-1] -- "NO, do not release"
> > >
> > >
> > > Thanks,
> > >
> > > The Apache Helix Team
> > >
> >
>


-- 
Lei Xia

Re: [NOTICE] Mandatory migration of git repos to gitbox.apache.org - one week left!

[Lei Xia]

+1

On Wed, Jan 30, 2019 at 11:28 AM Wang Jiajun  wrote:

> +1
>
> Best Regards,
> Jiajun
>
>
> On Wed, Jan 30, 2019 at 12:34 AM Xue Junkai  wrote:
>
> > Thanks Tommaso! Shall we have have a separate voting and link it? Or this
> > email thread is fair enough?
> >
> > Best,
> >
> > Junkai
> >
> > On Wed, Jan 30, 2019 at 12:30 AM Tommaso Teofili <
> > tommaso.teof...@gmail.com>
> > wrote:
> >
> > > I think we should cast a vote, isn't it?
> > >
> > > Regards,
> > > Tommaso
> > >
> > > Il giorno mer 30 gen 2019 alle ore 09:27 Xue Junkai 
> > > ha scritto:
> > > >
> > > > Thanks for the reminder. We are agree to move the gitbox.
> > > >
> > > > Best,
> > > >
> > > > Junkai
> > > >
> > > > On Wed, Jan 30, 2019 at 12:10 AM Apache Infrastructure Team <
> > > infrastruct...@apache.org> wrote:
> > > >>
> > > >> Hello again, helix folks.
> > > >> This is a reminder that you have *one week left* before the
> mandatory
> > > >> mass-migration from git-wip-us to gitbox.
> > > >>
> > > >> As stated earlier in 2018, and reiterated a few times, all git
> > > >> repositories must be migrated from the git-wip-us.apache.org URL to
> > > >> gitbox.apache.org, as the old service is being decommissioned. Your
> > > >> project is receiving this email because you still have repositories
> on
> > > >> git-wip-us that needs to be migrated.
> > > >>
> > > >> The following repositories on git-wip-us belong to your project:
> > > >>  - helix.git
> > > >>
> > > >>
> > > >> We are now entering the remaining one week of the mandated
> > > >> (coordinated) move stage of the roadmap, and you are asked to please
> > > >> coordinate migration with the Apache Infrastructure Team before
> > February
> > > >> 7th. All repositories not migrated on February 7th will be mass
> > migrated
> > > >> without warning, and we'd appreciate it if we could work together to
> > > >> avoid a big mess that day :-).
> > > >>
> > > >> As stated earlier, moving to gitbox means you will get full write
> > access
> > > >> on GitHub as well, and be able to close/merge pull requests and much
> > > >> more. The move is mandatory for all Apache projects using git.
> > > >>
> > > >> To have your repositories moved, please follow these steps:
> > > >>
> > > >> - Ensure consensus on the move (a link to a lists.apache.org thread
> > > will
> > > >>   suffice for us as evidence).
> > > >> - Create a JIRA ticket at
> https://issues.apache.org/jira/browse/INFRA
> > > >>
> > > >> Your migration should only take a few minutes. If you wish to
> migrate
> > > >> at a specific time of day or date, please do let us know in the
> > ticket,
> > > >> otherwise we will migrate at the earliest convenient time.
> > > >>
> > > >> There will be redirects in place from git-wip to gitbox, so requests
> > > >> using the old remote origins should still work (however we encourage
> > > >> people to update their remotes once migration has completed).
> > > >>
> > > >> As always, we appreciate your understanding and patience as we move
> > > >> things around and work to provide better services and features for
> > > >> the Apache Family.
> > > >>
> > > >> Should you wish to contact us with feedback or questions, please do
> so
> > > >> at: us...@infra.apache.org.
> > > >>
> > > >>
> > > >> With regards,
> > > >> Apache Infrastructure
> > > >>
> > >
> >
>
-- 
Lei Xia

[GitHub] helix pull request #297: ZkClient related improvments

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/297#discussion_r250807912
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/manager/zk/zookeeper/ZkConnection.java
 ---
@@ -84,6 +83,25 @@ public void close() throws InterruptedException {
 }
   }
 
+  protected void reconnect(Watcher watcher) throws InterruptedException {
+_zookeeperLock.lock();
+try {
+  if (_zk == null) {
+throw new IllegalStateException("zk client has not been connected 
or already been closed");
+  }
+  ZooKeeper prevZk = _zk;
+  try {
+LOG.debug("Creating new ZookKeeper instance to reconnect to " + 
_servers + ".");
--- End diff --

LOG.info?


---

[GitHub] helix pull request #297: ZkClient related improvments

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/297#discussion_r250795524
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/manager/zk/CallbackHandler.java ---
@@ -674,12 +684,24 @@ public void handleChildChange(String parentPath, 
List currentChilds) {
   /**
* Invoke the listener for the last time so that the listener could 
clean up resources
*/
+  @Deprecated
   public void reset() {
+reset(true);
+  }
+
+  void reset(boolean isShutdown) {
 logger.info("Resetting CallbackHandler: " + this.toString());
--- End diff --

include isShutdown here in the log?


---

Re: [VOTE] Apache Helix 0.8.3 Release

[Lei Xia]

+1

On Mon, Nov 26, 2018 at 5:48 PM Xue Junkai  wrote:

> Hi,
>
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.8.3. This is the 15th release of Helix as an Apache project, as
> well as the 11th release as a top-level Apache project.
>
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
>
> Release notes:
>
> *https://helix.apache.org/0.8.3-docs/releasenotes/release-0.8.3.html
> *
>
>
> Release artifacts:
>
> https://repository.apache.org/content/repositories/orgapachehelix-1021
>
>
> Distribution:
>
> * binaries:
>
> https://dist.apache.org/repos/dist/dev/helix/0.8.3]/binaries/
>
> * sources:
>
> https://dist.apache.org/repos/dist/dev/helix/0.8.3/src/
>
>
> The 0.8.3 release tag:
>
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.8.3
>
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
>
> [+1] -- "YES, release"
>
> [0] -- "No opinion"
>
> [-1] -- "NO, do not release"
>
>
> Thanks,
>
> The Apache Helix Team
>

[GitHub] helix pull request #267: Fix P2P message logic in controller to avoid sendin...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/267

Fix P2P message logic in controller to avoid sending duplicated messages to 
participants



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/267.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 #267


commit 880f885121afecab4e186282fbf94a146a2cf04a
Author: Lei Xia 
Date:   2018-04-25T01:18:40Z

Fix P2P message logic in controller to avoid sending duplicated messages to 
participants.

commit 74145e8ad3b34753186d53526bab825de4432c31
Author: Lei Xia 
Date:   2018-07-28T00:28:17Z

Temorary workaround to fix P2P race-condition for old helix participant 
(0.8.1 or older).




---

[GitHub] helix pull request #254: Use polling verifier instead of hard-coded sleep in...

[lei-xia]

Github user lei-xia closed the pull request at:

https://github.com/apache/helix/pull/254


---

Re: [VOTE] Apache Helix 0.8.2 Release

[Lei Xia]

+1

On Wed, Jul 25, 2018 at 5:08 PM Vivo Xu  wrote:

> +1
>
> On Wed, Jul 25, 2018 at 4:47 PM, Xue Junkai  wrote:
>
> > +1
> >
> > On Wed, Jul 25, 2018 at 4:46 PM, Wang Jiajun 
> > wrote:
> >
> > > Hi,
> > >
> > > This is to call for a vote on releasing the following candidate as
> Apache
> > > Helix 0.8.2. This is the 14th release of Helix as an Apache project, as
> > > well as the 10th release as a top-level Apache project.
> > >
> > > Apache Helix is a generic cluster management framework that makes it
> easy
> > > to build partitioned and replicated, fault-tolerant and scalable
> > > distributed systems.
> > >
> > > Release notes:
> > > http://helix.apache.org/0.8.2-docs/releasenotes/release-0.8.2.html
> > >
> > > Release artifacts:
> > > https://repository.apache.org/content/repositories/orgapachehelix-1018
> > >
> > > Distribution:
> > > * binaries:
> > > https://dist.apache.org/repos/dist/dev/helix/0.8.2/binaries/
> > > * sources:
> > > https://dist.apache.org/repos/dist/dev/helix/0.8.2/src/
> > >
> > > The 0.8.2 release tag:
> > > https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=
> > > refs/tags/helix-
> > > 0.8.2
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/dev/helix/KEYS
> > >
> > > Please vote on the release. The vote will be open for at least 72
> hours.
> > >
> > > [+1] -- "YES, release"
> > > [0] -- "No opinion"
> > > [-1] -- "NO, do not release"
> > >
> > > Thanks,
> > > The Apache Helix Team
> > >
> >
> >
> >
> > --
> > Junkai Xue
> >
>

[GitHub] helix pull request #254: Use polling verifier instead of hard-coded sleep in...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/254

Use polling verifier instead of hard-coded sleep in tests to reduce test 
time



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/254.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 #254


commit 4c4bd006fa1344024a3008be781068901c2cc995
Author: Lei Xia 
Date:   2018-06-19T00:33:16Z

Use polling verifier instead of hard-coded sleep in tests to reduce test 
time.




---

[ANNOUNCE] New committer: Jiajun Wang

[Lei Xia]

Hi, All

  The Project Management Committee (PMC) for Apache Helix has asked Jiajun
Wang 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
better productivity.

  Welcome Jiajun!

Helix Team



-- 
Lei Xia

[GitHub] helix pull request #244: Some refactors to deduplicate test codes and reduce...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/244

Some refactors to deduplicate test codes and reduce total test times.



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/244.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 #244


commit 4609d94488f4e97e6bf1c233281ca39433c4f72e
Author: Lei Xia 
Date:   2018-06-12T20:57:09Z

Fix a couple of tests, and reduce the total test times.

commit cc9956beab3cd7064db981abdf97286dd6fe13e1
Author: Lei Xia 
Date:   2018-06-18T15:25:09Z

Fix deleteCluster in test code.

commit 4385d01a3673efa631d9837507c21ccab9f69be4
Author: Lei Xia 
Date:   2018-06-18T17:21:53Z

Refactor tests to use deleteCluster in test base class to deduplicate codes.




---

[GitHub] helix pull request #240: Properly remove clusters after each test, and clean...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/240

Properly remove clusters after each test, and clean up duplicated codes in 
tests and move them into base test classes.

…es in tests and move them into base test classes.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/240.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 #240


commit c0d5792b745c67b6fee56ba79df02be89d1f049e
Author: Lei Xia 
Date:   2018-06-08T00:15:54Z

Properly remove clusters after each test, and clean up duplicated codes in 
tests and move them into base test classes.




---

[GitHub] helix pull request #235: Improve RoutingDataCache to use zk version based se...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/235

Improve RoutingDataCache to use zk version based selective update when 
reading the ExternalViews and TargetExternalView.

Change RoutingDataCache to use zk version based selective update when 
reading the ExternalViews and TargetExternalView.


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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/235.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 #235


commit b81ef06103f2349c32b36abcef8de62cbcba3d5d
Author: Lei Xia 
Date:   2018-05-29T21:25:32Z

Should not start periodical refresh in RoutingTableProvider if helixmanager 
is not set.

commit 8527a5ae03053d2c1293bad1e60f351681f7ad0b
Author: Lei Xia 
Date:   2018-05-30T17:22:10Z

Fix bugs in ClusterStateVerifier and StrictMatchExternalViewVerifier.

commit d02083e652797673e4826a45fc19896f610803c2
Author: Lei Xia 
Date:   2018-05-11T19:11:09Z

Change RoutingDataCache to use zk version based selective update when 
reading the ExternalViews and TargetExternalView.

RB=1317410
BUG=HELIX-929
G=helix-reviewers
A=jxue




---

Re: [VOTE] Apache Helix 0.8.1 Release

[Lei Xia]

+1



On Thu, Apr 26, 2018 at 11:57 AM Vivo Xu <x...@xuxu.name> wrote:

> +1
> On Thu, Apr 26, 2018 at 11:34 AM Lei Xia <l...@linkedin.com> wrote:
>
> > +1
> >
> >
> >
> > Lei Xia
> >
> > 
> > From: Eric Kim <er...@linkedin.com>
> > Sent: Thursday, April 26, 2018 10:47:58 AM
> > To: dev@helix.apache.org
> > Subject: [VOTE] Apache Helix 0.8.1 Release
> >
> > Hi,
> >
> >
> >
> > This is to call for a vote on releasing the following candidate as Apache
> > Helix 0.8.1. This is the thirteenth release of Helix as an Apache
> project,
> > as well as the ninth release as a top-level Apache project.
> >
> >
> >
> > Apache Helix is a generic cluster management framework that makes it easy
> > to build partitioned and replicated, fault-tolerant and scalable
> > distributed systems.
> >
> >
> >
> > Release notes:
> >
> > https://helix.apache.org/0.8.1-docs/releasenotes/release-0.8.1.html
> >
> >
> >
> > Release artifacts:
> >
> > https://repository.apache.org/content/repositories/orgapachehelix-1016
> >
> >
> >
> > Distribution:
> >
> > * binaries:
> >
> > https://dist.apache.org/repos/dist/dev/helix/0.8.1/binaries/
> >
> > * sources:
> >
> > https://dist.apache.org/repos/dist/dev/helix/0.8.1/src/
> >
> >
> >
> > The 0.8.1 release tag:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.8.1
> >
> >
> >
> > KEYS file available here:
> >
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> >
> >
> >
> > Please vote on the release. The vote will be open for at least 72 hours.
> >
> >
> >
> > [+1] -- "YES, release"
> >
> > [0] -- "No opinion"
> >
> > [-1] -- "NO, do not release"
> >
> >
> >
> > Thanks,
> >
> > The Apache Helix Team
> >
> >
>

Re: [VOTE] Apache Helix 0.8.1 Release

[Lei Xia]

+1



Lei Xia


From: Eric Kim <er...@linkedin.com>
Sent: Thursday, April 26, 2018 10:47:58 AM
To: dev@helix.apache.org
Subject: [VOTE] Apache Helix 0.8.1 Release

Hi,



This is to call for a vote on releasing the following candidate as Apache Helix 
0.8.1. This is the thirteenth release of Helix as an Apache project, as well as 
the ninth release as a top-level Apache project.



Apache Helix is a generic cluster management framework that makes it easy to 
build partitioned and replicated, fault-tolerant and scalable distributed 
systems.



Release notes:

https://helix.apache.org/0.8.1-docs/releasenotes/release-0.8.1.html



Release artifacts:

https://repository.apache.org/content/repositories/orgapachehelix-1016



Distribution:

* binaries:

https://dist.apache.org/repos/dist/dev/helix/0.8.1/binaries/

* sources:

https://dist.apache.org/repos/dist/dev/helix/0.8.1/src/



The 0.8.1 release tag:

https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.8.1



KEYS file available here:

https://dist.apache.org/repos/dist/dev/helix/KEYS



Please vote on the release. The vote will be open for at least 72 hours.



[+1] -- "YES, release"

[0] -- "No opinion"

[-1] -- "NO, do not release"



Thanks,

The Apache Helix Team

[GitHub] helix pull request #196: Move all command tool classes into a separate sub-f...

[lei-xia]

Github user lei-xia closed the pull request at:

https://github.com/apache/helix/pull/196


---

[GitHub] helix pull request #193: Fix a few of unstable integration tests.

[lei-xia]

Github user lei-xia closed the pull request at:

https://github.com/apache/helix/pull/193


---

[GitHub] helix issue #145: [HELIX-674] Introducing constraints based rebalancing mech...

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/145
  
Can you rebase to HEAD?


---

[GitHub] helix pull request #193: Fix a few of unstable integration tests.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/193

Fix a few of unstable integration tests.



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/193.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 #193


commit 3ccc5944eca00c9b7ec6438a02638bd4205e1422
Author: Lei Xia <lxia@...>
Date:   2018-04-20T23:11:27Z

Fix a few of unstable integration tests.




---

[GitHub] helix pull request #185: Add forcefully workflow and job delete API into Hel...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/185

Add forcefully workflow and job delete API into HelixAdmin and Helix Rest.

This will allow application to clean up any hanging and/or half-deleted 
workflows and jobs.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/185.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 #185


commit 19c9db03620e87e985e78508234e623fa68dbb3a
Author: Lei Xia <lxia@...>
Date:   2018-04-11T17:28:22Z

Add forcefully workflow and job delete API into HelixAdmin and Helix Rest.




---

[GitHub] helix issue #180: Two minor fixes

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/180
  
Can you rebase to HEAD?


---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/179
  
merged, thanks!


---

[GitHub] helix pull request #183: Fix race-condition issue that could block ZkClient ...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/183

Fix race-condition issue that could block ZkClient event thread in 
CallbackHandler.

1) Replace native batch callback handling thread with 
DedupEventCallbackProcessor, so the queue is deduplicated when event gets 
enqueued, instead of at the time of dequeue.

2) Shutdown and clean up the processor properly when CallbackHanlder is 
reset().

3) Add a flag to indicated whether the CallbackHandler is reset. If reset, 
do not enqueue further event into the batch callback queue.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/183.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 #183


commit a25305eb83c3226d028e39c27a70293c2576756e
Author: Lei Xia <lxia@...>
Date:   2018-04-16T18:38:26Z

Fix race-condition issue that could block ZkClient event thread in 
CallbackHandler.




---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/179
  
Could you please rebase to the current HEAD of master branch?  Thanks


---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/179
  
With this incremented id, you can not tell which thread runs which task 
either, right?


---

[GitHub] helix pull request #178: A few minor fixes.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/178

A few minor fixes.



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/178.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 #178


commit a2fc41a3c3df396995637d50c8b7737a477799b0
Author: Lei Xia <lxia@...>
Date:   2018-04-02T21:33:29Z

Wrap these high frequent called debug log statements with debug level check 
to reduce memory footprint.

commit 538a49b724ab0fbe2590b2f98f159199d7e1
Author: Harry Zhang <zhan849@...>
Date:   2018-03-28T18:42:44Z

Remove excessive logs about controller message cleanup

commit 92ad02f1e0f939dea221842514a8b395e9b73fc5
Author: Lei Xia <lxia@...>
Date:   2018-04-03T21:01:07Z

Fix NPE exception in CurrentStateOutput when getting currentstate for a 
task.

commit cc4ced0ef718460d27416c806534ba07987e22ad
Author: Lei Xia <lxia@...>
Date:   2018-04-04T00:24:30Z

Fix NPE in TestRoutingTableProvider.

commit 4201f6d56d88dfbf22f92157d1c73c9a493404d9
Author: Lei Xia <lxia@...>
Date:   2018-04-03T20:46:05Z

Add error->offline state transition callback in 
DistClusterControllerStateModel.




---

[GitHub] helix pull request #172: Fix performance issue in ClusterDataCache by using ...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/172

Fix performance issue in ClusterDataCache by using set instead of list.



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/172.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 #172


commit 3561845fafbda75055e22f4393c939645d515a4e
Author: Lei Xia <lxia@...>
Date:   2018-03-28T20:38:23Z

Fix performance issue in ClusterDataCache by using set instead of list.




---

[GitHub] helix pull request #159: Improvements to Helix's Callback handling.

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/159#discussion_r177537725
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/common/DedupEventBlockingQueue.java 
---
@@ -0,0 +1,139 @@
+package org.apache.helix.common;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import com.google.common.collect.Lists;
+import com.google.common.collect.Maps;
+import java.util.Map;
+import java.util.Queue;
+import java.util.concurrent.BlockingQueue;
+
+/**
+ * A blocking queue of events, which automatically deduplicate events with 
the same "type" within
+ * the queue, i.e, when putting an event into the queue, if there is 
already an event with the
+ * same type existing in the queue, the new event won't be inserted into 
the queue.
+ * This class is meant to be a limited implementation of the {@link 
BlockingQueue} interface.
+ *
+ * T -- the Type of an event.
+ * E -- the event itself.
+ */
+public class DedupEventBlockingQueue<T, E> {
+  private final Map<T, Entry<T, E>> _eventMap;
+  private final Queue _eventQueue;
+
+  class Entry <T, E> {
+private T _type;
+private E _event;
+
+Entry (T type, E event) {
+  _type = type;
+  _event = event;
+}
+
+T getType() {
+  return _type;
+}
+
+E getEvent() {
+  return _event;
+}
+  }
+
+  /**
+   * Instantiate the queue
+   */
+  public DedupEventBlockingQueue() {
+_eventMap = Maps.newHashMap();
+_eventQueue = Lists.newLinkedList();
+  }
+
+  /**
+   * Remove all events from the queue
+   */
+  public synchronized void clear() {
+_eventMap.clear();
+_eventQueue.clear();
+  }
+
+  /**
+   * Add a single event to the queue, overwriting events with the same name
+   */
+  public synchronized void put(T type, E event) {
+Entry entry = new Entry(type, event);
+
+if (!_eventMap.containsKey(entry.getType())) {
+  // only insert to the queue if there isn't a same-typed event 
already present
+  boolean result = _eventQueue.offer(entry);
+  if (!result) {
+return;
+  }
+}
+// always overwrite the existing entry in the map in case the entry is 
different
+_eventMap.put((T) entry.getType(), entry);
+notify();
+  }
+
+  /**
+   * Remove an element from the front of the queue, blocking if none is 
available. This method
+   * will return the most recent event seen with the oldest enqueued event 
name.
+   * @return ClusterEvent at the front of the queue
+   * @throws InterruptedException if the wait for elements was interrupted
+   */
+  public synchronized E take() throws InterruptedException {
+while (_eventQueue.isEmpty()) {
+  wait();
--- End diff --

This is a good point, I copied the old implementation from 
ClusterEventBlockingQueue here, but use Java's blockingQueue implementation 
could make it more concise and reliable.  I will make the change.


---

[GitHub] helix pull request #159: Improvements to Helix's Callback handling.

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/159#discussion_r177537463
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/common/DedupEventBlockingQueue.java 
---
@@ -0,0 +1,139 @@
+package org.apache.helix.common;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import com.google.common.collect.Lists;
+import com.google.common.collect.Maps;
+import java.util.Map;
+import java.util.Queue;
+import java.util.concurrent.BlockingQueue;
+
+/**
+ * A blocking queue of events, which automatically deduplicate events with 
the same "type" within
+ * the queue, i.e, when putting an event into the queue, if there is 
already an event with the
+ * same type existing in the queue, the new event won't be inserted into 
the queue.
+ * This class is meant to be a limited implementation of the {@link 
BlockingQueue} interface.
+ *
+ * T -- the Type of an event.
+ * E -- the event itself.
+ */
+public class DedupEventBlockingQueue<T, E> {
+  private final Map<T, Entry<T, E>> _eventMap;
+  private final Queue _eventQueue;
+
+  class Entry <T, E> {
+private T _type;
+private E _event;
+
+Entry (T type, E event) {
+  _type = type;
+  _event = event;
+}
+
+T getType() {
+  return _type;
+}
+
+E getEvent() {
+  return _event;
+}
+  }
+
+  /**
+   * Instantiate the queue
+   */
+  public DedupEventBlockingQueue() {
+_eventMap = Maps.newHashMap();
+_eventQueue = Lists.newLinkedList();
+  }
+
+  /**
+   * Remove all events from the queue
+   */
+  public synchronized void clear() {
+_eventMap.clear();
+_eventQueue.clear();
+  }
+
+  /**
+   * Add a single event to the queue, overwriting events with the same name
+   */
+  public synchronized void put(T type, E event) {
+Entry entry = new Entry(type, event);
+
+if (!_eventMap.containsKey(entry.getType())) {
+  // only insert to the queue if there isn't a same-typed event 
already present
+  boolean result = _eventQueue.offer(entry);
+  if (!result) {
+return;
+  }
+}
+// always overwrite the existing entry in the map in case the entry is 
different
+_eventMap.put((T) entry.getType(), entry);
+notify();
+  }
+
+  /**
+   * Remove an element from the front of the queue, blocking if none is 
available. This method
+   * will return the most recent event seen with the oldest enqueued event 
name.
+   * @return ClusterEvent at the front of the queue
+   * @throws InterruptedException if the wait for elements was interrupted
+   */
+  public synchronized E take() throws InterruptedException {
--- End diff --

Both put() and take() methods are synchronized, so they will be exlcuded to 
each other, it should be fine, right?


---

[GitHub] helix pull request #159: Improvements to Helix's Callback handling.

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/159#discussion_r177534964
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/manager/zk/CallbackHandler.java ---
@@ -153,7 +195,12 @@ private void parseListenerProperties() {
 BatchMode batchMode = 
_listener.getClass().getAnnotation(BatchMode.class);
 PreFetch preFetch = _listener.getClass().getAnnotation(PreFetch.class);
 
-String asyncBatchModeEnabled = 
System.getProperty("isAsyncBatchModeEnabled");
+String asyncBatchModeEnabled = 
System.getProperty("helix.callbackhandler.isAsyncBatchModeEnabled");
--- End diff --

it is backcompatible, the code reads 
""helix.callbackhandler.isAsyncBatchModeEnabled"" first, if it is not set, it 
reads "isAsyncBatchModeEnabled" instead (see the lines 199-202 following) 


---

[GitHub] helix issue #160: Couple fixes and improvements for Helix

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/160
  
Can you please rebase to the HEAD.


---

[GitHub] helix pull request #159: Improvements to Helix's Callback handling.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/159

Improvements to Helix's Callback handling.

- Improve CallbackHandler by avoiding unnessary re-subscripe to the data 
change event.Resubscribe to zk changes only when there is any child chanage, 
with async subscription to ensure not missing any new child paths.

- Add new config name for batch callback handing in CallbackHandler.

- Support configurable data prefetch in ZkClient during watch event 
callback.

- Add TotalEventCount and TotalHandledEventCount metrics into 
ZkClientMonitor Mbean.

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

$ git pull https://github.com/lei-xia/helix callback_improvements

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

https://github.com/apache/helix/pull/159.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 #159


commit 49c3da71c63a323005457688cb18ec7ad5f07bba
Author: Lei Xia <lxia@...>
Date:   2018-03-03T00:03:37Z

Add TotalEventCount and TotalHandledEventCount metrics into ZkClientMonitor 
Mbean.

commit 6f1c4d8ae20c694e2d9ec7a78731a4ae62c363bd
Author: Lei Xia <lxia@...>
Date:   2018-03-19T17:16:38Z

Support configurable data prefetch in ZkClient during watch event callback.

commit 7c28aaab31413d3b35aeb54ae00a52fa24347490
Author: Lei Xia <lxia@...>
Date:   2018-03-25T02:59:49Z

Add new config name for batch callback handing in CallbackHandler.

commit 77163dba762959c949aa6aa884198036739db9ff
Author: Lei Xia <lxia@...>
Date:   2018-03-19T17:48:49Z

Fix TestZkCallbackHandlerLeak, and refine some log outputs.

commit 5de511ab160c61ff6c9006d5f332b6d92f1c8a55
Author: Lei Xia <lxia@...>
Date:   2018-03-25T03:55:17Z

Improve CallbackHandler by avoiding unnessary re-subscripe to the data 
change event.Resubscribe to zk changes only when there is any child chanage, 
with async subscription to ensure not missing any new child paths.




---

[GitHub] helix issue #156: [HELIX-682] controller should delete obsolete messages wit...

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/156
  
Please rebase to HEAD


---

[GitHub] helix issue #152: [HELIX-681] don't fail state transition task if we fail to...

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/152
  
Could you rebase to HEAD?


---

[GitHub] helix issue #155: Features and improvements to Helix RoutingTableProvider.

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/155
  
Thanks!


---

[GitHub] helix pull request #157: A few of minor improvements.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/157

A few of minor improvements.

1. Include resource name in the log.

2. Fix a bug in AutoRebalancer that it fails to compute ideal mapping if 
"ANY_LIVEINSTANCE" is specified as the replica.

3. Persist preferenceLists into TargetExternalView.

4. Add cluster level metrics to show whether cluster is in maintenance mode 
or paused.

5. Including version number in Participant and Controller history, and add 
additional logs.

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

$ git pull https://github.com/lei-xia/helix small-improvements

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

https://github.com/apache/helix/pull/157.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 #157


commit 9477946d689bf5a034e854c707c0d4c3fbdd5432
Author: Lei Xia <lxia@...>
Date:   2018-02-17T07:05:49Z

Including version number in Participant and Controller history, and add 
additional logs.

commit 1c6e76bda8b9a3816e0de35ac9296ecf453f8dd9
Author: Lei Xia <lxia@...>
Date:   2018-02-21T20:25:52Z

Add cluster level metrics to show whether cluster is in maintenance mode or 
paused.

commit 47aeb616add1620ddad9c7a2082f6e1e2c579d6a
Author: Lei Xia <lxia@...>
Date:   2018-03-08T18:19:23Z

Persist preferenceLists into TargetExternalView.

commit 2141f27ee101845f1f6b99d64abf1df46b5e9ddb
Author: Lei Xia <lxia@...>
Date:   2018-03-15T00:29:53Z

Fix a bug in AutoRebalancer that it fails to compute ideal mapping if 
"ANY_LIVEINSTANCE" is specified as the replica.

commit e0bbc516c2431524c7b57b20479d31097e28bff4
Author: Lei Xia <lxia@...>
Date:   2017-12-02T01:58:06Z

Include resource name in the log.




---

[GitHub] helix issue #151: Tutorial update for task framework new features in 0.8

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/151
  
Already merged. thanks!


---

[GitHub] helix issue #155: Features and improvements to Helix RoutingTableProvider.

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/155
  
Is controller code depending on the Routing table code by any chance? I saw 
RouterCache, could not figure out if thats used in controller or specator?

--  No, RouterCache depends on the BasicClusterCache which is in the  
org.apache.helix.commons module, which the controller's ClusterDataCache also 
depends on. 


---

[GitHub] helix pull request #155: Features and improvements to Helix RoutingTableProv...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/155#discussion_r176492004
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/spectator/RoutingTableSnapshot.java 
---
@@ -0,0 +1,151 @@
+package org.apache.helix.spectator;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import java.util.Collection;
+import java.util.List;
+import java.util.Set;
+import org.apache.helix.model.InstanceConfig;
+import org.apache.helix.model.LiveInstance;
+
+/**
+ * The snapshot of RoutingTable information.  It is immutable, it reflects 
the routing table
+ * information at the time it is generated.
+ */
+public class RoutingTableSnapshot {
--- End diff --

So we add this feature to return a snapshot of routingtable at that time.  
The routingTable in the provider will keep update, but the snapshot is a 
read-only view of routingtable at the time it was created.


---

[GitHub] helix pull request #155: Features and improvements to Helix RoutingTableProv...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/155#discussion_r176491654
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/spectator/RoutingTableSnapshot.java 
---
@@ -0,0 +1,151 @@
+package org.apache.helix.spectator;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import java.util.Collection;
+import java.util.List;
+import java.util.Set;
+import org.apache.helix.model.InstanceConfig;
+import org.apache.helix.model.LiveInstance;
+
+/**
+ * The snapshot of RoutingTable information.  It is immutable, it reflects 
the routing table
+ * information at the time it is generated.
+ */
+public class RoutingTableSnapshot {
--- End diff --

The routingtable information in RoutingTableProvider keeps changing as long 
as there are externalview changes, however, we have a  use case that the 
application wants a consitent view of a whole routingtable (externalviews). 
Their code will iterate through the routingtable, if anything changes the table 
during their iteration, it breaks their code assumption.


---

[GitHub] helix pull request #155: Features and improvements to Helix RoutingTableProv...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/155#discussion_r176490668
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/manager/zk/CallbackHandler.java ---
@@ -576,8 +573,8 @@ public void handleDataChange(String dataPath, Object 
data) {
 
   @Override
   public void handleChildChange(String parentPath, List 
currentChilds) {
-logger.debug("Data change callback: child changed, path: " + 
parentPath + ", current childs: "
-+ currentChilds);
+logger.info("Data change callback: child changed, path: " + parentPath 
+ ", current child count: "
--- End diff --

Sure, I will change it to debug, we use that information to investigate our 
occusion callback lost issue, and now we know the cause, so will fix this.


---

[GitHub] helix pull request #152: [HELIX-681] don't fail state transition task if we ...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/152#discussion_r176143399
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTask.java ---
@@ -168,7 +169,14 @@ public HelixTaskResult call() {
 
   // forward relay messages attached to this message to other 
participants
   if (taskResult.isSuccess()) {
-forwardRelayMessages(accessor, _message, 
taskResult.getCompleteTime());
+try {
+  forwardRelayMessages(accessor, _message, 
taskResult.getCompleteTime());
+} catch (Exception e) {
+  // Fail to send relay message should not result in a task 
execution failure
+  // Currently we don't log error to ZK to reduce writes as when 
accessor throws
+  // exception, ZK might not be in good condition.
+  logger.error("Failed to send relay messages.", e);
--- End diff --

logger.warn should be fine, this is not fatal error.


---

[GitHub] helix pull request #152: [HELIX-681] don't fail state transition task if we ...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/152#discussion_r176144284
  
--- Diff: helix-core/src/main/java/org/apache/helix/util/HelixUtil.java ---
@@ -219,4 +220,22 @@ public static String serializeByComma(List 
objects) {
 
 return idealStateMap;
   }
+
+  /**
+   * Remove the given message from ZK using the given accessor. This 
function will
+   * not throw exception
+   * @param accessor HelixDataAccessor
+   * @param msg message to remove
+   * @param instanceName name of the instance on which the message sits
+   * @return true if success else false
+   */
+  public static boolean removeMessageFromZK(HelixDataAccessor accessor, 
Message msg,
+  String instanceName) {
+try {
+  return accessor.removeProperty(msg.getKey(accessor.keyBuilder(), 
instanceName));
+} catch (Exception e) {
--- End diff --

Do we throw NoNodeException here, if there is, NoNodeException should be 
treated as success?


---

[GitHub] helix pull request #155: Features and improvements to Helix RoutingTableProv...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/155

Features and improvements to Helix RoutingTableProvider.

This PR includes a few of features and improvements to existing Helix's 
RoutingTableProvider interface and implements. There are:

1)   Add to getResources() into RoutingTableProvider.
2)   RoutingTableProvider to support direct aggregating routing information 
from CurrentStates in each liveinstance. When sourceDataType is set as 
CurrentState, RoutingTableProvider will listen on CurrentStateChanges and 
refresh routing table from CurrentStates upon changes.
3)   Add RoutingTableSnapshot class to hold a snapshot of routing table 
information and provide API to return RoutingTableSnapshot from 
RoutingTableProvider.
4)   Support RoutingTableChangeListener in RoutingTableProvider, which will 
be called when there is anything changed in the RoutingTable information.





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

$ git pull https://github.com/lei-xia/helix routingTableChanges

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

https://github.com/apache/helix/pull/155.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 #155


commit 03656dcc41dfb735e75b970171e9ea80cfe1c0da
Author: Lei Xia <lxia@...>
Date:   2018-02-08T23:52:01Z

Allow to get all resources from RoutingTableProvider class.

commit f908193355e132e149ad9525f7770a15b8bca513
Author: Lei Xia <lxia@...>
Date:   2018-03-20T22:04:30Z

Change RoutingTableProvider to support direct aggregating routing 
information from CurrentStates in each liveinstance. When sourceDataType is set 
as CurrentState, RoutingTableProvider will listen on CurrentStateChanges and 
refresh routing table from CurrentStates upon changes.

commit d2288d61b32f36b08987d06007b2aead68fa1be4
Author: Lei Xia <lxia@...>
Date:   2018-02-17T07:05:49Z

Including version number in Participant and Controller history, and add 
additional logs.

commit 8709e6015930a691b6a72acad207d68b7365bcc1
Author: Lei Xia <lxia@...>
Date:   2018-02-16T00:12:22Z

Add RoutingTableSnapshot class to hold a snapshot of routing table 
information and provide API to return RoutingTableSnapshot from 
RoutingTableProvider.

commit 85537299d46c2f96130671d93d9118bed4a5492f
Author: Junkai Xue <jxue@...>
Date:   2018-02-28T22:12:31Z

Support RoutingTableChangeListener in RoutingTableProvider. Add test for it.




---

[GitHub] helix issue #151: Tutorial update for task framework new features in 0.8

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/151
  
Could you please rebase to head?


---

[GitHub] helix pull request #153: Retrieve cached idealMappings for all Rebalancers i...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/153

Retrieve cached idealMappings for all Rebalancers instead of recomputing it 
during every rebalance round.

Retrieve cached idealMappings for all Rebalancers (AutoRebalancer, 
DelayedRebalancer and CustomRebalancer) for any rebalance strategies. This will 
avoid recompute idealmapping (preference list) if there is no 
idealstate/instanceconfig/LiveInstances changes.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/153.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 #153


commit e2f99412b46f282f626a4734f24459c49bd130e1
Author: Lei Xia <lxia@...>
Date:   2018-02-09T18:28:25Z

Retrieve cached idealMappings for all Rebalancers (AutoRebalancer, 
DelayedRebalancer and CustomRebalancer) for any rebalance strategies. This will 
avoid recompute idealmapping (preference list) if there is no 
idealstate/instanceconfig/LiveInstances changes.




---

[GitHub] helix pull request #145: [HELIX-674] Introducing constraints based rebalanci...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/145#discussion_r175858026
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/controller/rebalancer/constraint/TotalCapacityConstraint.java
 ---
@@ -0,0 +1,79 @@
+package org.apache.helix.controller.rebalancer.constraint;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import 
org.apache.helix.api.rebalancer.constraint.AbstractRebalanceHardConstraint;
+import 
org.apache.helix.api.rebalancer.constraint.dataprovider.CapacityProvider;
+import 
org.apache.helix.api.rebalancer.constraint.dataprovider.PartitionWeightProvider;
+import org.apache.helix.controller.common.ResourcesStateMap;
+import org.apache.helix.controller.rebalancer.util.ResourceUsageCalculator;
+
+import java.util.HashMap;
+import java.util.Map;
+
+public class TotalCapacityConstraint extends 
AbstractRebalanceHardConstraint {
+  private final PartitionWeightProvider _partitionWeightProvider;
+  private final CapacityProvider _capacityProvider;
+  // Use to track any assignments that are proposed during the rebalance 
process.
+  // Note these assignments are not reflected in providers.
+  private final Map<String, Integer> _pendingUsage;
+
+  public TotalCapacityConstraint(PartitionWeightProvider 
partitionWeightProvider,
+  CapacityProvider capacityProvider) {
+super();
+_partitionWeightProvider = partitionWeightProvider;
+_capacityProvider = capacityProvider;
+_pendingUsage = new HashMap<>();
+  }
+
+  private boolean validate(String resource, String partition, String 
participant) {
+int usage = _capacityProvider.getParticipantUsage(participant) + 
(_pendingUsage
+.containsKey(participant) ? _pendingUsage.get(participant) : 0);
+return +_partitionWeightProvider.getPartitionWeight(resource, 
partition) + usage
--- End diff --

why there is a "+" in begining of the statement?


---

[GitHub] helix pull request #145: [HELIX-674] Introducing constraints based rebalanci...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/145#discussion_r175833400
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/api/rebalancer/constraint/AbstractRebalanceSoftConstraint.java
 ---
@@ -0,0 +1,56 @@
+package org.apache.helix.api.rebalancer.constraint;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.helix.controller.common.ResourcesStateMap;
+
+import java.util.Map;
+
+public abstract class AbstractRebalanceSoftConstraint {
+  private static int DEFAULT_IMPORTANCE = 1;
+  protected int _importance = DEFAULT_IMPORTANCE;
+
+  /**
+   * Evaluate how the given assignment fits the constraint.
+   * @param resource Target resource
+   * @param proposedAssignment Map of <PartitionName, lists of possible 
ParticipantName>
+   * @return Evaluation about the assignment. Larger number means better 
fit under this constraint.
+   */
+  public abstract Map<String, int[]> evaluate(String resource,
+  Map<String, String[]> proposedAssignment);
+
+  /**
+   * @return The soft constraint's importance that will be used to compare 
with other soft constraint results.
+   * Aggregated evaluation score = SUM(constraint_evaluation * importance).
+   */
+  public int getConstraintImportance() {
--- End diff --

Is importance same as priority?


---

[GitHub] helix pull request #145: [HELIX-674] Introducing constraints based rebalanci...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/145#discussion_r175833652
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/api/rebalancer/constraint/AbstractRebalanceSoftConstraint.java
 ---
@@ -0,0 +1,56 @@
+package org.apache.helix.api.rebalancer.constraint;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.helix.controller.common.ResourcesStateMap;
+
+import java.util.Map;
+
+public abstract class AbstractRebalanceSoftConstraint {
+  private static int DEFAULT_IMPORTANCE = 1;
+  protected int _importance = DEFAULT_IMPORTANCE;
+
+  /**
+   * Evaluate how the given assignment fits the constraint.
+   * @param resource Target resource
+   * @param proposedAssignment Map of <PartitionName, lists of possible 
ParticipantName>
+   * @return Evaluation about the assignment. Larger number means better 
fit under this constraint.
+   */
+  public abstract Map<String, int[]> evaluate(String resource,
+  Map<String, String[]> proposedAssignment);
+
+  /**
+   * @return The soft constraint's importance that will be used to compare 
with other soft constraint results.
+   * Aggregated evaluation score = SUM(constraint_evaluation * importance).
+   */
+  public int getConstraintImportance() {
--- End diff --

And the larger means more important?


---

[GitHub] helix pull request #150: Refactor ClusterDataCache, break it into small cach...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/150

Refactor ClusterDataCache, break it into small cache components, 

1) Refactor ClusterDataCache, break it into small cache components, 
including CurrentStateCache, InstanceMessageCache and TaskDataCache, and put 
the refresh logic into each cache component itself.

2) Enable our helix-core admin scripts to be able to pump log lines into 
the console by default.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/150.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 #150


commit c456971852c78b424fc1186173eb5a661d26640a
Author: Lei Xia <lxia@...>
Date:   2018-02-06T01:26:24Z

Refactor ClusterDataCache, break it into small cache components, including 
CurrentStateCache, InstanceMessageCache and TaskDataCache, and put the refresh 
logic into each cache component itself.

commit 90e27fd72ddf5d8e734f54a01bc4e57aca042df9
Author: Lei Xia <lxia@...>
Date:   2018-02-08T18:51:31Z

Enable our scripts to be able to pump log lines into the console.




---

[GitHub] helix pull request #149: RoutingTableProvider to support getting routing dat...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/149

RoutingTableProvider to support getting routing data from 
TargetExternalView.

Implement the RoutingTableProvide for TargetExternalView subscription. 
Write several tests for it.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/149.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 #149


commit 07e05a4c1c456b7e09c7750955fa46c34e1a288a
Author: Junkai Xue <jxue@...>
Date:   2018-02-06T01:09:28Z

RoutingTableProvider for TargetExternalView

Implement the RoutingTableProvide for TargetExternalView subscription. 
Write several tests for it.




---

[GitHub] helix issue #146: [HELIX-680] add system setting to unblock TestZkCallbackHa...

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/146
  
Could you rebase to the head?


---

[GitHub] helix pull request #141: Fix the job parents listing logic in REST & Make lo...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/141

 Fix the job parents listing logic in REST  &  Make logs are not printed 
with empty list in intermediate stage 



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/141.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 #141


commit 5c5186bf6f24720875710efe99fd389d4dc91602
Author: Junkai Xue <jxue@...>
Date:   2018-02-02T00:19:21Z

Fix the job parents listing logic in REST

commit 5f142f2ec7dcf718111bbc9e94eb83d7689428f0
Author: Junkai Xue <jxue@...>
Date:   2018-02-02T21:52:50Z

Make logs are not printed with empty list in intermediate stage




---

[GitHub] helix issue #136: [helix-core] _rebalanceTimerPeriod in RebalanceConfig shou...

[lei-xia]

Github user lei-xia commented on the issue:

https://github.com/apache/helix/pull/136
  
@juvenzhu  already merged, somehow github did not close this PR, please go 
ahead to close it.  Thanks!


---

[GitHub] helix pull request #139: Two small changes

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/139

Two small changes

- Remove duplicated log lines
- Fix issue in reporting MissingMinActiveReplicaPartitionGauge metric in 
ResourceMonitor when there is no IdealMapping persisted in IdealState.


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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/139.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 #139


commit d9eb0e5ff9fe859e2ea16028838c4e82ccdf5da0
Author: Lei Xia <lxia@...>
Date:   2018-01-25T19:52:45Z

Remove duplicated log lines.

commit f31d6465944adb4e4a6b66f4e35538610e6f4bbd
Author: Lei Xia <lxia@...>
Date:   2018-01-30T02:12:56Z

Fix issue in reporting MissingMinActiveReplicaPartitionGauge metric in 
ResourceMonitor when there is no IdealMapping persisted in IdealState.




---

[GitHub] helix pull request #138: CallbackHandler to use either java config property ...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/138

CallbackHandler to use either java config property or class annotation n to 
enable batch callback handling

CallbackHandler to use either java config property or class annotation to 
enable batch callback handling.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/138.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 #138


commit 2dbd88ffed2eb84697225a58e8831b740ecd5919
Author: Lei Xia <lxia@...>
Date:   2018-03-02T22:20:14Z

CallbackHandler to use either java config property or class annotation to 
enable batch callback handling.




---

Re: [VOTE] Apache Helix 0.8.0 Release

[Lei Xia]

+1

On Mon, Jan 29, 2018 at 5:13 PM, Xue Junkai  wrote:

> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.8.0. This is the 13th release of Helix as an Apache project, as
> well as the 9th release as a top-level Apache project.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
> Release notes:
> *http://helix.apache.org/0.8.0-docs/releasenotes/release-0.8.0.html
> *
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-1013
>
> Distribution:
> * binaries:
> https://dist.apache.org/repos/dist/dev/helix/0.8.0/binaries/
> * sources:
> https://dist.apache.org/repos/dist/dev/helix/0.8.0/src/
>
> The 0.8.0 release tag:
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=
> refs/tags/helix-0.8.0
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
> [+1] -- "YES, release"
> [0] -- "No opinion"
> [-1] -- "NO, do not release"
>
> Thanks,
> The Apache Helix Team
>

Re: Helix-UI status

[Lei Xia]

Hi, Yulun


   helix-front is our new generation of web UI, which is supposed to fully 
support of monitoring and operating Helix clusters.  The code is already in 
master branch.  We will release new 0.8 version in about one week, new release 
will come with detailed document on how to setup this new UI.  Please stay 
tunned.



Lei


Lei Xia


Data Infra/Helix

l...@linkedin.com<mailto:l...@linkedin.com>
www.linkedin.com/in/lxia1<http://www.linkedin.com/in/lxia1>


From: kishore g <g.kish...@gmail.com>
Sent: Wednesday, January 24, 2018 12:17:50 PM
To: dev@helix.apache.org; gb
Subject: Re: Helix-UI status

I think the google source is just a mirror, you can ignore that.

This was something done by Greg Brandt. We did not have the bandwidth to
bring it to master as we did not deploy it in production. Feel free to take
this as the base and make it work in production and contribute it back to
Helix.

Also, take a look at helix-front. This is the ui currently used at LinkedIn
and is tested in production. It might be a good idea to bring in the
helix-ui code into helix-front.

On Wed, Jan 24, 2018 at 12:07 PM, Yulun Li <yu...@uber.com> wrote:

> We are building tools for our Helix application and we are considering
> helix
> -ui. However, we found a few links, such as
>
> https://apache.googlesource.com/helix/+/master/helix-ui/
> https://github.com/apache/helix/tree/helix-0.7.x/helix-ui
>
> A few questions:
>
>1. Can we just ignore the repo on Google Source?
>2. Are there risks of using Helix-UI with Helix 0.6.8 deployment?
>3. What's the current status and feature roadmap for Helix UI?
>
> Thanks.
>

[GitHub] helix pull request #:

[lei-xia]

Github user lei-xia commented on the pull request:


https://github.com/apache/helix/commit/bada911c7f246cf685c30323e118402cca89111d#commitcomment-26944027
  
In helix-core/src/main/java/org/apache/helix/GroupCommit.java:
In helix-core/src/main/java/org/apache/helix/GroupCommit.java on line 142:
This is for updating partition's CurrentState to ZK.   For regular 
resources (not jobs), if this update fails, controller will send the state 
transition request again, once the participant gets the request, it realizes 
its local currentstate is inconsistent with the one on ZK, so it will try to 
update zk again. So the only consequence is that the state transition latency 
observed by spectators will get longer.

However, since Job's completion is triggered by its update of state to ZK, 
if the update fails, controller has no way to tell whether the job is still 
running or completed.  So the task will be hang there from controller's 
perspective even though it is actually completed in participant.   We added 
retry to reduce this chance, also adding task timeout will be another option to 
avoid a job hang forever if this happens.

To improve the retry, add exponential backoff retry could be another 
option.  Buffering failed updates and retrying it in background could be 
complicated, because we need to make sure the update sequence.  If there is new 
update to the same znode while there is a pending buffered updates in the 
queue, then we need to make sure the old one being written to zk first.  This 
could be non-trival to implement. 

We assume ZK unavailable time will be very minimal, and most of the network 
outage is intermittent (recovered quickly).  If a network outage lasts longer 
than zk timeout (say 30s), the participant will be disconnected from Helix, all 
of its currentStates will be reset anyway.  So comparing to adding more code 
complexity to make sure our write to ZK is gurantteed to be deliverd,  we may 
instead to focus on how we can make sure even if the write fails, participant 
always has other ways to recover it eventually, even though it may take a 
little more delay.   


---

Re: [jira] [Created] (HELIX-671) Introduce github.com/uber-go/go-helix as a Golang participant client library

[Lei Xia]

Hi, Zhijin

   Thanks for the contribution,  we will include a link to your Helix Go
client from Helix Apache website.


Thanks
Lei

On Fri, Jan 5, 2018 at 1:51 PM Zhijin Li (JIRA) <j...@apache.org> wrote:

> Zhijin Li created HELIX-671:
> ---
>
>  Summary: Introduce github.com/uber-go/go-helix as a Golang
> participant client library
>  Key: HELIX-671
>  URL: https://issues.apache.org/jira/browse/HELIX-671
>  Project: Apache Helix
>   Issue Type: Improvement
> Affects Versions: 0.6.x
> Reporter: Zhijin Li
>
>
> TLDR: Trying to get [https://github.com/uber-go/go-helix] listed on [
> https://helix.apache.org/ClientLibraries.html].
>
> Long version:
>
> Uber is building a sharding infrastructure on top of Apache Helix (thanks
> to the awesome framework!). As part of the effort, since Go is a
> first-class citizen at Uber, we have been developing a Helix participant
> module in Go. To contribute back to the open-source community and get all
> the open-source benefits, we open-sourced the library at
> https://github.com/uber-go/go-helix in Dec 2017.
>
> We realized there's a page https://helix.apache.org/ClientLibraries.html
> for listing Helix client libraries, and thought go-helix can be a good
> candidate. Here're the reasons:
> * After researching, we didn't find any known-good Helix library in Go.
> * go-helix is production proven in Uber-scale environment, and still being
> actively developed and maintained.
> * go-helix works with the Apache Helix Java controller (Uber's production
> setup).
> * go-helix contains good documentations.
> * Go is getting non-trivial popularity/attractions in the industry.
> Particularly for go-helix, it has gained 28 stars, 13 unique clones, 154
> unique visitors, 1k+ views on Github since launched recently.
> * With the Helix website's help, go-helix will get better
> visibility/discoverability, making it more likely to get more mature and
> reliable at a quicker speed.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>
-- 
Lei Xia

Re: doc link broken

[Lei Xia]

Hi, William

   Thanks for reporting the issue,  we will fix it asap.


Lei

On Tue, Jan 2, 2018 at 12:35 AM William Guo  wrote:

> hi helix team,
>
> http://helix.apache.org/0.7.1-docs/tutorial_health.html
>
> http://helix.apache.org/0.6.9-docs/tutorial_health.html
>
> Above links are broken, could you fix this?
>
>
> Thanks,
> William
>

Re: Dynamic routing among Jobs

[Lei Xia]

Hi, Dlmuthu

   We have plan to add conditional workflow support into our task
framework, where you can specify next job to execute based on previous
job's status (succeed or failed or aborted, etc). But before we having that
feature ready, one workaround you can do is to create two separate
workflows containing only JobD and JobE in each, and start one of these
workflows within your JobA depends on the output of JobA.


Thanks
Lei

On Fri, Nov 17, 2017 at 6:18 AM, DImuthu Upeksha  wrote:

> Hi Devs
>
> I'm implementing a workflow similar to following image (copied from [1]).
> When the workflow is started, Job A is executed. Depending on the result of
> Job A, it should decide the next job to be executed (JobD or JobE). For
> example, JobA checks for a database entry and if an entry can be found,
> execute JobD otherwise execute JobE. As far as I have understood, we can do
> the static wiring of jobs at the workflow creation phase. Is it possible to
> perform above task in Helix?
> [1] http://helix.apache.org/0.6.9-docs/tutorial_task_framework.html
>
> ​Thanks
> Dimuthu
>

Re: Data synch between replicas

[Lei Xia]

Hi, Leela

  The Master/Slave model does not support that because there is no way
Helix can differeniate two slave replicas unless your application have
customized logic to perform the check.  However, for your case, you can
create your own state model instead of using defaut MasterSlave model.  You
can create a state model with three states,  for example, Master,
PrimarySlave, SecondarySlave, and there is maximal 1 Master and 1
PrimarySlave allowed.

  You can use the MasterSlave model implementation as a sample to implement
your state model (org.apache.helix.model.MasterSlaveSMD) and register the
new model using helix admin API: HelixAdmin.addStateModelDef(String
clusterName, String stateModelDef, StateModelDefinition stateModel).


Thanks
Lei

On Mon, Oct 30, 2017 at 5:48 AM, leela maheswararao <
leela_mahesh...@yahoo.com.invalid> wrote:

> Does anybody got a chance to look into this?
>
>
> On Friday, October 27, 2017, 7:50 AM, leela maheswararao <
> leela_mahesh...@yahoo.com> wrote:
>
> Team,Our scenario consist of 1 Master and 2 slaves per partition.
> Spectator (client) will write to 1 master and 1 slave and we wanted another
> slave to frequently synch with master at server side. To achieve server -
> server synch for given partition, we need to know for given partition
> whether current node acts as 3rd replica. Does helix ensure order of
> replica is always same for given partition? Also what api exists to know
> current node replica number for partition it owns?
> Thanks in advance,Mahesh
>
>
>
>
>
>
>

Re: [VOTE] Apache Helix 0.6.9 Release

[Lei Xia]

+1

On Mon, Oct 9, 2017 at 5:26 PM Xue Junkai  wrote:

> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.6.9. This is the 12th release of Helix as an Apache project, as
> well as the 8th release as a top-level Apache project.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
> Release notes:
> http://helix.apache.org/0.6.9-docs/releasenotes/release-0.6.9.html
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-1011
>
> Distribution:
> * binaries:
> https://dist.apache.org/repos/dist/dev/helix/0.6.9/binaries/
> * sources:
> https://dist.apache.org/repos/dist/dev/helix/0.6.9/src/
>
> The 0.6.9 release tag:
>
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.6.9
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
> [+1] -- "YES, release"
> [0] -- "No opinion"
> [-1] -- "NO, do not release"
>
> Thanks,
> The Apache Helix Team
>

[GitHub] helix pull request #113: A few small features and improvements.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/113

A few small features and improvements.



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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/113.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 #113


commit e530bf5183e7ad2f3a27d0e75448b88e8554efe8
Author: Lei Xia <l...@linkedin.com>
Date:   2017-01-30T23:02:24Z

Clean up jobs in a jobqueue automatically after the job completes and 
passes its expiry time.

commit 0aeb5579d4f7130d6a4310d2d817e0153620cae0
Author: Lei Xia <l...@linkedin.com>
Date:   2017-02-07T22:59:10Z

Support configurable job purge interval for a queue.

commit 1889699269597dd5cb8b10e2eb90dcbcf6c64622
Author: Lei Xia <l...@linkedin.com>
Date:   2017-02-11T01:28:40Z

Persist preference list into IdealState in full-auto mode and allow user to 
choose persisting either bestpossible or intermediate state mapping into the 
mapfield of IS.




---

[GitHub] helix pull request #109: Add state transition throttling feature.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/109

Add state transition throttling feature.

This pull request contains two changes:
- Add state transition throttling feature with adding a new 
IntermediateStateCaluStage into the rebalance pipeline.
- Clean up TaskDriver, separate command line handling to a new TaskAdmin 
file.

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

$ git pull https://github.com/lei-xia/helix master

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

https://github.com/apache/helix/pull/109.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 #109


commit 4e4871967db07cee191debb9d26bfcd53c401945
Author: Lei Xia <l...@linkedin.com>
Date:   2017-01-07T00:31:38Z

Add state transition throttling logic into intermediateStateCalcStage.

commit 55b844657947dea661f6067dbd32237b0ed6afe2
Author: Lei Xia <l...@linkedin.com>
Date:   2017-01-26T21:46:00Z

Clean up TaskDriver, move all command line support code to a new tool class 
TaskAdmin.java, and build a commandline shell script from TaskAdmin.




---

Latest Helix blog

[Lei Xia]

Hi, All

  This is the latest Helix blog we have published,
https://engineering.linkedin.com/blog/2017/07/powering-helix_s-auto-rebalancer-with-topology-aware-partition-p,
please feel free to share it.

  Maybe we should add a page to our Apache website to include all of the
publications, talks and blogs about Helix?  If no one objects it, I will go
ahead and add such page.


Thanks
Lei

Re: Branches rearrangement

[Lei Xia]

Thanks Junkai for working on this!


Lei

On Thu, Jun 22, 2017 at 4:23 PM, Xue Junkai  wrote:

> Hi All,
>
> Branch switches are done now! Now the development work will be started in
> master branch, which is forked from helix-0.6.x. Please update your forked
> repo or refork it if it is necessary.
>
> Feel free to let us know if you have any questions or concerns!
>
> Best,
>
> Junkai
>
> On Mon, Jun 19, 2017 at 4:33 PM, Xue Junkai  wrote:
>
> > Hi All,
> >
> > Here're some heads ups for branch rearrangements:
> >
> >1. There will not be any features checked into helix-0.6.x, except
> >some hot fixes.
> >2. Master branch will be moved to helix-0.7.x for 0.7 version bug
> >fixing.
> >3. Move helix-0.6.x branch to Master branch and try our best to make
> >it compatible with helix-0.7.x
> >
> > Please let us know if you have any suggestions or questions regarding
> this!
> >
> > Best,
> >
> > Junkai
> >
>

Re: [VOTE] Apache Helix 0.6.8 Release

[Lei Xia]

+1

On Mon, Jun 12, 2017 at 4:44 PM, Xue Junkai <j...@apache.org> wrote:

> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.6.8. This is the eleventh release of Helix as an Apache project, as
> well as the seventh release as a top-level Apache project.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault-tolerant and scalable
> distributed systems.
>
> Release notes:
> http://helix.apache.org/0.6.8-docs/releasenotes/release-0.6.8.html
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-1010
>
> Distribution:
> * binaries:
> https://dist.apache.org/repos/dist/dev/helix/0.6.8/binaries/
> * sources:
> https://dist.apache.org/repos/dist/dev/helix/0.6.8/src/
>
> The [VERSION] release tag:
> https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=
> refs/tags/helix-0.6.8
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/helix/KEYS
>
> Please vote on the release. The vote will be open for at least 72 hours.
>
> [+1] -- "YES, release"
> [0] -- "No opinion"
> [-1] -- "NO, do not release"
>
> Thanks,
> The Apache Helix Team
>



-- 
Lei Xia

[GitHub] helix pull request #98: [HELIX-660]Configurable operation timeout for Helix ...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/98

[HELIX-660]Configurable operation timeout for Helix ZKClient.



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

$ git pull https://github.com/lei-xia/helix helix-0.6.x

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

https://github.com/apache/helix/pull/98.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 #98


commit 2ae13d09b8d34b0db45f46a39dea51691e9e7c63
Author: Lei Xia <l...@linkedin.com>
Date:   2017-06-10T00:20:22Z

[HELIX-660]Configurable operation timeout for Helix ZKClient.




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

[GitHub] helix pull request #97: [HELIX-658] Bump Zookeeper version to 3.4.9.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/97

[HELIX-658] Bump Zookeeper version to 3.4.9.



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

$ git pull https://github.com/lei-xia/helix github.lei.master

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

https://github.com/apache/helix/pull/97.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 #97


commit 01f13c9baebc1927b7552f459dc8e09876beac89
Author: Lei Xia <l...@linkedin.com>
Date:   2017-06-09T20:55:34Z

[HELIX-658] Bump Zookeeper version to 3.4.9.




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

[jira] [Commented] (HELIX-658) Upgrade Zookeeper version

[Lei Xia (JIRA)]

[ 
https://issues.apache.org/jira/browse/HELIX-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034714#comment-16034714
 ] 

Lei Xia commented on HELIX-658:
---

Will work on this at this weekend.

> Upgrade Zookeeper version
> -
>
> Key: HELIX-658
> URL: https://issues.apache.org/jira/browse/HELIX-658
> Project: Apache Helix
>  Issue Type: Improvement
>Affects Versions: 0.7.2
>Reporter: Beau Brower
>Assignee: Lei Xia
> Fix For: 0.7.2
>
>
> 0.6.7 has upgraded to 3.4.9
> 0.7.x branch should do the same.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] helix pull request #89: [HELIX-655] Helix per-participant concurrent task th...

[lei-xia]

Github user lei-xia commented on a diff in the pull request:

https://github.com/apache/helix/pull/89#discussion_r119443872
  
--- Diff: 
helix-core/src/main/java/org/apache/helix/model/InstanceConfig.java ---
@@ -408,6 +410,18 @@ public void setInstanceEnabledForPartition(String 
resourceName, String partition
 }
   }
 
+  /**
+   * Get maximum allowed running task count on this instance
+   * @return the maximum task count
+   */
+  public int getMaxConcurrentTask() {
--- End diff --

make this config option also available in cluster config? In most of cases, 
user would choose same value for all of its nodes, this makes them easier to 
set just once instead of in each instance config.

If the value is set in both cluster config and some of instance config, the 
value in instance config can take effect.


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

[GitHub] helix pull request #94: Add support of setting/updating of cluster/resource/...

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/94

Add support of setting/updating of cluster/resource/instance configs from 
ConfigAccessor.

This pull requests contains two commits:

- Add support of setting/updating Cluster/Resource/Instance configs in 
ConfigAccessor.
- Allow user to enable persisting preference list and best possible 
state map into IdealState in full-auto mode.


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

$ git pull https://github.com/lei-xia/helix helix-0.6.x

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

https://github.com/apache/helix/pull/94.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 #94


commit 7c92bf543571daac555f5d8b933805dddced7ca5
Author: Lei Xia <l...@linkedin.com>
Date:   2017-05-23T19:27:23Z

Add support of setting/updating Cluster/Resource/Instance configs in 
ConfigAccessor.

commit 8ba068e7b78aedf4743f2da57670384534d1d4f8
Author: Lei Xia <l...@linkedin.com>
Date:   2017-05-23T20:58:24Z

Allow user to enable persisting preference list and best possible state map 
into IdealState in full-auto mode.




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

Our github repo is down?

[Lei Xia]

Seems our github repo is down?  https://github.com/apache/helix,  or it is
just me can not access it?



Lei

[GitHub] helix pull request #84: Bump to JDK 1.7.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/84

Bump to JDK 1.7.



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

$ git pull https://github.com/lei-xia/helix helix-0.6.x

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

https://github.com/apache/helix/pull/84.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 #84


commit 7dc8884fa306ed05b59d8a557804f075362a556a
Author: Lei Xia <l...@linkedin.com>
Date:   2017-04-07T21:08:54Z

Bump to JDK 1.7.




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

[GitHub] helix pull request #83: Update ivy files with new version name.

[lei-xia]

GitHub user lei-xia opened a pull request:

https://github.com/apache/helix/pull/83

Update ivy files with new version name.



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

$ git pull https://github.com/lei-xia/helix helix-0.6.x

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

https://github.com/apache/helix/pull/83.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 #83


commit 2c72ec6d30f38c44bb161e179a1b287ddc54c6f3
Author: Lei Xia <l...@linkedin.com>
Date:   2017-04-05T16:34:13Z

Update ivy files with new version name.




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