You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/01/07 01:42:51 UTC

[jira] [Commented] (ACCUMULO-2142) GC doesn't advertise its port

    [ https://issues.apache.org/jira/browse/ACCUMULO-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863715#comment-13863715 ] 

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=0.0.0.0:0}} 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: https://issues.apache.org/jira/browse/ACCUMULO-2142
>             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
(v6.1.5#6160)