accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2142) GC doesn't advertise its port
Date Tue, 07 Jan 2014 00:42:51 GMT


Josh Elser commented on ACCUMULO-2142:

I was silly for a little bit: I didn't recurse down far enough into the ZK node so I missed
the node that actually had the data.

In 1.6 with gc.port.client, I see {{GC_CLIENT=}} whereas 1.5 with the same gives
me something reasonable like {{GC_CLIENT=localhost:58622}}. Both are using 'localhost' in
the GC file.

> GC doesn't advertise its port
> -----------------------------
>                 Key: ACCUMULO-2142
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: gc, monitor
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 1.6.0
> The monitor expects to use /gc/lock in ZooKeeper to find the host:port that the GC is
running on, but the GC doesn't seem to actually put it there. I'm running with a GC port of
0 to let the process choose its own random port
> 1.6 seems to correctly report that the GC is dead.

This message was sent by Atlassian JIRA

View raw message