HBase
  1. HBase
  2. HBASE-10293

Master and RS GC logs can conflict when run on same host

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: 0.96.1.1
    • Fix Version/s: None
    • Component/s: scripts
    • Labels:
      None

      Description

      My issue manifests when I uncomment the line export SERVER_GC_OPTS=... in hbase-env.sh and start HBase. It's a single node in distributed mode, so both a Master and RegionServer are started on that host. Both start commands are run in the same minute, so only one gc.log-`date` file is created. `lsof` indicates two processes are writing to that file and the output of `ps` confirms they both received the same -Xloggc:/grid/0/var/log/hbase/gc.log-201401071515 argument.

      Presumably, the same will happen for folks running the thrift and rest gateways on the same box (any java process itemized in the server_cmds array in bin/hbase).

      Related (the reason I discovered this issue in the first place), stopping the master process results in its gc.log being truncated.

        Issue Links

          Activity

          Hide
          Enis Soztutar added a comment -

          I guess we can do a similar thing to the log4j logs, where we will append the username and daemon name to the gc log.

          Show
          Enis Soztutar added a comment - I guess we can do a similar thing to the log4j logs, where we will append the username and daemon name to the gc log.
          Hide
          Andrew Purtell added a comment -

          I run multiple servers on the same box. Each has their own config directory with their own hbase-env.sh. This is trivial to do with Puppet or pick your favorite configuration management tool. Kind of a non issue?

          Show
          Andrew Purtell added a comment - I run multiple servers on the same box. Each has their own config directory with their own hbase-env.sh. This is trivial to do with Puppet or pick your favorite configuration management tool. Kind of a non issue?
          Hide
          Nick Dimiduk added a comment -

          That's probably true for someone with production-level automation infrastructure. I'm thinking of the fellow who downloads a tarball, follows the instructions in the hbase-env.sh comments and is surprised by the outcome. FWIW, I don't think it's common to run each process out of it's own config directory. Likewise, I don't think it's common to set each process to log to it's own log directory either. Rather I tend to see /var/log/hbase containing all the HBase process logs for the machine.

          shrug I don't feel strongly about the issue, it just surprised me while I was setting up some performance infra recently. If you'd prefer to defer this kind of concern to the puppetiers, I guess resolve as not a problem.

          Show
          Nick Dimiduk added a comment - That's probably true for someone with production-level automation infrastructure. I'm thinking of the fellow who downloads a tarball, follows the instructions in the hbase-env.sh comments and is surprised by the outcome. FWIW, I don't think it's common to run each process out of it's own config directory. Likewise, I don't think it's common to set each process to log to it's own log directory either. Rather I tend to see /var/log/hbase containing all the HBase process logs for the machine. shrug I don't feel strongly about the issue, it just surprised me while I was setting up some performance infra recently. If you'd prefer to defer this kind of concern to the puppetiers, I guess resolve as not a problem.
          Hide
          Andrew Purtell added a comment -

          shrug I don't feel strongly about the issue

          Same here.

          Show
          Andrew Purtell added a comment - shrug I don't feel strongly about the issue Same here.
          Hide
          Nick Dimiduk added a comment -

          This is actually an Ambari issue. I've opened AMBARI-4255.

          Sorry for the noise.

          Show
          Nick Dimiduk added a comment - This is actually an Ambari issue. I've opened AMBARI-4255 . Sorry for the noise.

            People

            • Assignee:
              Unassigned
              Reporter:
              Nick Dimiduk
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development