HBase
  1. HBase
  2. HBASE-4458

HBase should give actionable information when a region is compressed with a codec that is not available.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.90.3
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      A cluster that previously used LZO codec was upgraded with the intent of moving away from the codec to another. Several regions failed to deploy because the LZO codec was no longer present. However, there was little indication that this as the problem.

      Ideally, the master web ui or hbck would detect these problems and provide why it fails to deploy and also provide an actionable error message.

        Issue Links

          Activity

          Hide
          Jonathan Hsieh added a comment -

          From reading the description it looks like HBASE-2515 worked. However, in this particular scenario, none of the regions servers had LZO installed. The goal was to move to another codec and somehow during the migration some regions were missed.

          The symptom we saw was that regions failed to be deployed. Admittedly, we didn't initially look at the logs. We tried assigning from the shell, but I don't recall seeing any class not found exceptions when the shell command failed. We ended up figuring out the problem by using HFile on the data in the hdfs region data and getting the ClassNotFound there.

          This brings up four potential places for an error message – in the shell, in hbck, in the web ui, as well as in the logs.

          Show
          Jonathan Hsieh added a comment - From reading the description it looks like HBASE-2515 worked. However, in this particular scenario, none of the regions servers had LZO installed. The goal was to move to another codec and somehow during the migration some regions were missed. The symptom we saw was that regions failed to be deployed. Admittedly, we didn't initially look at the logs. We tried assigning from the shell, but I don't recall seeing any class not found exceptions when the shell command failed. We ended up figuring out the problem by using HFile on the data in the hdfs region data and getting the ClassNotFound there. This brings up four potential places for an error message – in the shell, in hbck, in the web ui, as well as in the logs.
          Hide
          stack added a comment -

          So HBASE-2514 didn't work? Or, wasn't used I suppose. Here is doc on lzo: http://hbase.apache.org/book.html#lzo.compression It wasn't followed? I agree it'd be better having issue show on master UI if we can.

          Show
          stack added a comment - So HBASE-2514 didn't work? Or, wasn't used I suppose. Here is doc on lzo: http://hbase.apache.org/book.html#lzo.compression It wasn't followed? I agree it'd be better having issue show on master UI if we can.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jonathan Hsieh
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development