HBase
  1. HBase
  2. HBASE-9046

Coprocessors can't be upgraded in service reliably

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.94.8, 0.96.0
    • Fix Version/s: None
    • Component/s: Coprocessors
    • Labels:
      None
    • Environment:

      Description

      My team and another user from the mailing list have run into an issue where replacing the coprocessor jar in HDFS and reloading the table does not load the latest jar. It may load the latest version on some percentage of RS but not all of them.

      This may be a config oversight or a lack of understanding of a caching mechanism that has a purge capability, but I thought I would log it here for confirmation.

      Workaround is to name the coprocessor JAR uniquely, place in HDFS, and re-enable the table using the new jar's name.

        Issue Links

          Activity

          iain wright created issue -
          iain wright made changes -
          Field Original Value New Value
          Description My team and another user from the mailing list have run into an issue where replacing the coprocessor jar in HDFS and reloading the table does not load the latest jar. It may load the latest version on some percentage of RS but not all of them.

          This may be a config oversight or a lack of understanding of a caching mechanism that has a purge capability, but I thought I would log it here for confirmation.

          Workaround is to name the coprocessor JAR uniquely, place in HDFS, and re-load the table using the new jar's name.

          My team and another user from the mailing list have run into an issue where replacing the coprocessor jar in HDFS and reloading the table does not load the latest jar. It may load the latest version on some percentage of RS but not all of them.

          This may be a config oversight or a lack of understanding of a caching mechanism that has a purge capability, but I thought I would log it here for confirmation.

          Workaround is to name the coprocessor JAR uniquely, place in HDFS, and re-enable the table using the new jar's name.

          iain wright made changes -
          Summary Some regions keep using an older version of coprocessor Some region servers keep using an older version of coprocessor
          Benoit Sigoure made changes -
          Affects Version/s 0.96.0 [ 12324822 ]
          Ted Yu made changes -
          Assignee Ted Yu [ yuzhihong@gmail.com ]
          Ted Yu made changes -
          Assignee Ted Yu [ yuzhihong@gmail.com ]
          Andrew Purtell made changes -
          Parent HBASE-9945 [ 12678657 ]
          Issue Type Bug [ 1 ] Sub-task [ 7 ]
          Andrew Purtell made changes -
          Fix Version/s 0.98.0 [ 12323143 ]
          Benoit Sigoure made changes -
          Summary Some region servers keep using an older version of coprocessor Coprocessors can't be upgraded in service reliably
          Benoit Sigoure made changes -
          Link This issue is related to HBASE-10119 [ HBASE-10119 ]
          Andrew Purtell made changes -
          Fix Version/s 0.98.0 [ 12323143 ]
          Andrew Purtell made changes -
          Parent HBASE-9945 [ 12678657 ]
          Issue Type Sub-task [ 7 ] Improvement [ 4 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              iain wright
            • Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:

                Development