Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 54D2610CB4 for ; Sun, 25 Oct 2015 00:18:45 +0000 (UTC) Received: (qmail 20602 invoked by uid 500); 25 Oct 2015 00:18:45 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 20559 invoked by uid 500); 25 Oct 2015 00:18:45 -0000 Mailing-List: contact user-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.apache.org Delivered-To: mailing list user@helix.apache.org Received: (qmail 20176 invoked by uid 99); 25 Oct 2015 00:17:03 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Oct 2015 00:17:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 149B9C17EF for ; Sun, 25 Oct 2015 00:17:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.129 X-Spam-Level: *** X-Spam-Status: No, score=3.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id FPlUN8HP6PGS for ; Sun, 25 Oct 2015 00:17:02 +0000 (UTC) Received: from mail-vk0-f53.google.com (mail-vk0-f53.google.com [209.85.213.53]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 2176342B32 for ; Sun, 25 Oct 2015 00:17:02 +0000 (UTC) Received: by vkgs66 with SMTP id s66so20823151vkg.1 for ; Sat, 24 Oct 2015 17:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=xNeqMB80+zsExlFHgBQRoDXVyz8AVNoSUI6Q8p7MGqQ=; b=sEcZAdU4iYiOhOlHAEE43ftBvdDS+HpmsSfCfSoZheY6vGn8PnJUsFBN9DNfvjbsH5 jSizLiiukuMYzQTIPkV0dTqT89bL0S3VciQJtvn98grEue14pP8hJummQv7eFyKQAFB8 o+ZMfbAN8+pVhzrXMwoWv+T110PM31G8BqFKo12LbkiLchRMSrzqrWMTCm+SRa0oKLks Lu8SMffFg/I6fsYjdOIpMVgLOtSoljybQzn8oO+HRRNmbuDfYyjvF76/geg+M9iEOOoA rqSZdI8X//p2XZxdEQQau6SMSdFUxkYAOAxENz+Xy1RhESJxGhogRwzuX/y5E53//cKt AzFQ== X-Received: by 10.31.52.214 with SMTP id b205mr18517686vka.122.1445732216148; Sat, 24 Oct 2015 17:16:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.99.198 with HTTP; Sat, 24 Oct 2015 17:16:36 -0700 (PDT) In-Reply-To: References: From: Hang Qi Date: Sat, 24 Oct 2015 17:16:36 -0700 Message-ID: Subject: Re: Question about HelixPropertyStore To: user@helix.apache.org Content-Type: multipart/alternative; boundary=001a1143f9322f15c10522e2c3a6 --001a1143f9322f15c10522e2c3a6 Content-Type: text/plain; charset=UTF-8 Hi Kishore, Thanks for providing the info, I will take a look. Previously I am using HelixManager#getHelixPropertyStore to get HelixPropertyStore. Thanks Hang Qi On Fri, Oct 23, 2015 at 4:13 PM, kishore g wrote: > Hi Hang, > > This api is a bit confusing. How are you creating ZkHelixPropertyStore > instance? > > public ZkHelixPropertyStore(ZkBaseDataAccessor accessor, String root, > List subscribedPaths) { > super(accessor, root, null, subscribedPaths); > } > > This is right constructor. For subscribedPaths, you can simply pass in > path to property store which is "/{clusterName}/PROPERTYSTORE" > > > On Fri, Oct 23, 2015 at 10:06 AM, Hang Qi wrote: > >> Hi All, >> >> We are using HelixPropertyStore in helix 0.6.4. The doc says "Helix >> supports caching the data with a write-through cache", so if I have two >> nodes A and B, if A made changes on some property in PropertyStore after B, >> will B get latest one? In our test, we kind of observe that B will still >> use its cached version, is that expected, do we have a way to get latest >> version on B? >> >> Besides, we notice following log, looks like we need to specify paths for >> watchers, but we do not find a way how to do that in HelixPropertyStore. >> >> WARN org.apache.helix.manager.zk.ZkCacheBaseDataAccessor - ZkCachePaths >> is null or empty. Will not start ZkCacheEventThread >> >> Moreover, do we support concurrent set on HelixPropertyStore? Just saw >> following description on AutoFallbackPropertyStore: "Property store that >> does auto fallback to an old location. Assuming no concurrent updates" >> >> Any suggestions ? >> >> Thanks >> Hang Qi >> > > -- Qi hang --001a1143f9322f15c10522e2c3a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Kishore,

Thanks for providing the in= fo, I will take a look.

Previously I am using Heli= xManager#getHelixPropertyStore to get HelixPropertyStore.

Thanks
Hang Qi

On Fri, Oct 23, 2015 at 4:13 PM, kis= hore g <g.kishore@gmail.com> wrote:
Hi Hang,

This api is a bi= t confusing. How are you creating ZkHelixPropertyStore instance?
=
public ZkHelixPropertyStore(ZkBaseDataAccessor<T>= accessor, String root,
=C2=A0 =C2=A0 =C2=A0 List<String> s= ubscribedPaths) {
=C2=A0 =C2=A0 super(accessor, root, null, subsc= ribedPaths);
}

This is right const= ructor. For subscribedPaths, you can simply pass in path to property store = which is=C2=A0"/{clusterName}/PROPERT= YSTORE"


On Fri, Oct 23, 2015 at 10:06 AM, Hang Qi &= lt;hangq.1985@gma= il.com> wrote:
Hi All,

We are using HelixPropertyStore = in helix 0.6.4. The doc says "Helix supports caching the data with a write-through cache= ", so if I have two nodes A and B, if A made changes on some property = in PropertyStore after B, will B get latest one?=C2=A0 In our test, we kind= of observe that B will still use its cached version, is that expected, do = we have a way to get latest version on B?

Besides, we notice following = log, looks like we need to specify paths for watchers, but we do not find a= way how to do that in HelixPropertyStore.

WARN=C2=A0 org.apache.helix.manager.zk.ZkCa= cheBaseDataAccessor=C2=A0 - ZkCacheP= aths is null or empty. Will not start ZkCacheEven= tThread

Moreover, do we suppor= t concurrent set on HelixPropertyStore? Just saw following description on A= utoFallbackPropertyStore: "Property store that does auto fallback to an old= location. Assuming no concurrent updates"

Any suggestions ?

Thanks
Hang Qi




--
=
Qi hang
--001a1143f9322f15c10522e2c3a6--