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 657DD179F6 for ; Thu, 16 Oct 2014 05:42:49 +0000 (UTC) Received: (qmail 14926 invoked by uid 500); 16 Oct 2014 05:42:49 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 14879 invoked by uid 500); 16 Oct 2014 05:42:49 -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 14868 invoked by uid 99); 16 Oct 2014 05:42:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Oct 2014 05:42:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of zheilbron@gmail.com designates 74.125.82.48 as permitted sender) Received: from [74.125.82.48] (HELO mail-wg0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Oct 2014 05:42:44 +0000 Received: by mail-wg0-f48.google.com with SMTP id k14so2854785wgh.19 for ; Wed, 15 Oct 2014 22:42:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pRjU3YU7fzxQkab8LKgjMUhTGQh9F0fbELOJ6QMeyu8=; b=JX03c/q0r/LNeuiFF7Pvh4ZVN1Nhk+hFGmjwoF6E65meyjqID8Ezzg6c6YhRpmbp+a e/nCFLhItLZi27UBOBVvb4muNtaxUYOipWBnw2qydlJgWPEByOxHJli0sksGMufXoeCe J3r7pZ52i7JqWl/w9U5LN2J6tqO8/7UYRiep5nfqido4+sYuEZcPZrqlF+wLYmlNfXnI xtKLvkKOrQ619kx1EGHom/dWJ5V2a6TRxptzBozG27ghHrqGAX6N63afmdlybOWG9nhP tiXTg+OoXR6nhxc9dbJQksHH18AmYPqU78WY4XWaACpv0VQLO42FZiMJ0fSx/SYS4Tib 7/OA== MIME-Version: 1.0 X-Received: by 10.194.85.43 with SMTP id e11mr7907472wjz.126.1413438143728; Wed, 15 Oct 2014 22:42:23 -0700 (PDT) Received: by 10.216.22.69 with HTTP; Wed, 15 Oct 2014 22:42:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 15 Oct 2014 22:42:23 -0700 Message-ID: Subject: Re: External view of dropped resources From: Zachary Heilbron To: user@helix.apache.org Content-Type: multipart/alternative; boundary=047d7bfceca6780fb5050583b66b X-Virus-Checked: Checked by ClamAV on apache.org --047d7bfceca6780fb5050583b66b Content-Type: text/plain; charset=UTF-8 You are right. One of issues HELIX-59 or HELIX-132 appear to address this problem, but are in a later version than we are using. Thanks! On Wed, Oct 15, 2014 at 10:20 PM, Kanak Biscuitwala wrote: > This was fixed relatively recently, I believe. What version of Helix are > you using? > > ________________________________ > > Date: Wed, 15 Oct 2014 19:32:32 -0700 > > Subject: External view of dropped resources > > From: zheilbron@x15soft.com > > To: user@helix.apache.org > > > > When a resource is dropped, it's configuration and ideal state are > > removed, but the external view seems to stick around. Is a further > > event or action required by either the user or Helix to remove them or > > is this unintentional? > > > > Note that querying the resources via helix-admin.sh will not show the > > dropped resources, but either using the HelixDataAccessor or looking in > > ZK directly will show them. > > > > Thanks, > > Zach > > --047d7bfceca6780fb5050583b66b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You are right. One of issues HELIX-59 or HELIX-132 appear = to address this problem, but are in a later version than we are using.
=
Thanks!

On Wed, Oct 15, 2014 at 10:20 PM, Kanak Biscuitwala <ka= nak.b@hotmail.com> wrote:
T= his was fixed relatively recently, I believe. What version of Helix are you= using?

________________________________
> Date: Wed, 15 Oct 2014 19:32:32 -0700
> Subject: External view of dropped resources
> From: zheilbron@x15soft.com
> To: user@helix.apache.org=
>
> When a resource is dropped, it's configuration and ideal state are=
> removed, but the external view seems to stick around. Is a further
> event or action required by either the user or Helix to remove them or=
> is this unintentional?
>
> Note that querying the resources via helix-admin.sh will not show the<= br> > dropped resources, but either using the HelixDataAccessor or looking i= n
> ZK directly will show them.
>
> Thanks,
> Zach
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <= /div>

--047d7bfceca6780fb5050583b66b--