Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.0
    • Component/s: gc
    • Labels:
      None

      Description

      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.

        Activity

        Josh Elser made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Josh Elser made changes -
        Component/s monitor [ 12316204 ]
        Hide
        ASF subversion and git services added a comment -

        Commit da9e0f40a34b339eaa23093fce1603c98de0d5d9 in branch refs/heads/master from Josh Elser
        [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=da9e0f4 ]

        ACCUMULO-2142 Return the HostAndPort from creating the thrift server

        The GC returned the original HostAndPort object instead of the one
        returned by TServerUtils, and ultimately the HsHaServer. The problem
        here is that TServerUtils is doing some magic to unwind things like
        0.0.0.0 as an addr and a port of 0.

        Show
        ASF subversion and git services added a comment - Commit da9e0f40a34b339eaa23093fce1603c98de0d5d9 in branch refs/heads/master from Josh Elser [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=da9e0f4 ] ACCUMULO-2142 Return the HostAndPort from creating the thrift server The GC returned the original HostAndPort object instead of the one returned by TServerUtils, and ultimately the HsHaServer. The problem here is that TServerUtils is doing some magic to unwind things like 0.0.0.0 as an addr and a port of 0.
        Hide
        ASF subversion and git services added a comment -

        Commit da9e0f40a34b339eaa23093fce1603c98de0d5d9 in branch refs/heads/1.6.0-SNAPSHOT from Josh Elser
        [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=da9e0f4 ]

        ACCUMULO-2142 Return the HostAndPort from creating the thrift server

        The GC returned the original HostAndPort object instead of the one
        returned by TServerUtils, and ultimately the HsHaServer. The problem
        here is that TServerUtils is doing some magic to unwind things like
        0.0.0.0 as an addr and a port of 0.

        Show
        ASF subversion and git services added a comment - Commit da9e0f40a34b339eaa23093fce1603c98de0d5d9 in branch refs/heads/1.6.0-SNAPSHOT from Josh Elser [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=da9e0f4 ] ACCUMULO-2142 Return the HostAndPort from creating the thrift server The GC returned the original HostAndPort object instead of the one returned by TServerUtils, and ultimately the HsHaServer. The problem here is that TServerUtils is doing some magic to unwind things like 0.0.0.0 as an addr and a port of 0.
        Hide
        Josh Elser added a comment -

        Ok, verified on a clean system: "GC_CLIENT=localhost:0" in 1.6

        Show
        Josh Elser added a comment - Ok, verified on a clean system: "GC_CLIENT=localhost:0" in 1.6
        Hide
        Josh Elser added a comment -

        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.

        Show
        Josh Elser added a comment - 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.
        Josh Elser made changes -
        Fix Version/s 1.5.1 [ 12324399 ]
        Josh Elser made changes -
        Field Original Value New Value
        Description 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.

        1.5 *claims* to be able to talk to the monitor, but I'm baffled right now as to how it's actually doing this (if it actually is). The code looks like it should be getting an empty value out of ZooKeeper and nothing parseable as a host:port.
        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.
        Josh Elser created issue -

          People

          • Assignee:
            Josh Elser
            Reporter:
            Josh Elser
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development