Mailing-List: contact user-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.incubator.apache.org
Received-SPF: error (athena.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: curator-x-discovery-server not purging static services after
 specified instanceRefreshMs
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
In-Reply-To: 
 <CAGs_S1jgdbpsDkrMEVwdQaPz5P++17Jbu2Zn9k+N8Ciiqa4Raw@mail.gmail.com>
Date: Fri, 17 May 2013 13:27:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <47DC8D23-BD18-4318-AACA-A98E67B46E6F@jordanzimmerman.com>
References: 
 <CAGs_S1jgdbpsDkrMEVwdQaPz5P++17Jbu2Zn9k+N8Ciiqa4Raw@mail.gmail.com>
To: user@curator.incubator.apache.org

Sorry it's taken so long to reply on this=85

Have you allocated and started a InstanceCleanup instance?

-Jordan

On May 9, 2013, at 8:21 AM, Rob Righter <rob.righter@pardot.com> wrote:

> Hello,
>=20
> I am using Curator's curator-x-discovery-server. It is allowing me to
> putService, getAll and removeService via the REST api and that all
> appears to be working correctly. However, when I call putService with
> a serviceType of "STATIC", the service is not being automatically
> purged from the getAll list after the specified InstanceRefreshMs has
> passed. I had assumed from the documentation (
> =
https://github.com/Netflix/curator/tree/master/curator-x-discovery-server
> ) that a STATIC service would be removed from all lists after that
> InstanceRefreshMs (specified in the DiscoveryContext) expires.
>=20
> If it is helpful, the Json associated with my service is:
>=20
> {
>  "name": "analytics",
>  "id": "ca2fff8e-d756-480c-b59e-8297ff88624b",
>  "address": "10.20.30.40",
>  "port": 1234,
>  "payload": {
>    "datacenter": "dallas",
>    "role": "master"
>  },
>  "registrationTimeUTC": 1368105287000,
>  "serviceType": "STATIC"
> }
>=20
>=20
> My questions are:
>=20
> (1) Is my understanding of the "STATIC" serviceType correct, or am I
> misreading the documentation?
>=20
> (2) If my understanding is correct, is this a known issue, and can
> anybody reproduce this behavior?
>=20
> Thanks,
> Rob