[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-17817: Resolution: Fixed Fix Version/s: 1.1.11 1.3.2 1.2.6 1.4.0 2.0.0 Status: Resolved (was: Patch Available) > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche >Assignee: Steen Manniche > Labels: logging > Fix For: 2.0.0, 1.4.0, 1.2.6, 1.3.2, 1.1.11 > > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch, HBASE-17817.master.003.patch, > HBASE-17817.master.004.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Hadoop Flags: Reviewed Release Note: Add table name to exception logging when a coprocessor is removed from a table by the region server Status: Patch Available (was: Open) > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch, HBASE-17817.master.003.patch, > HBASE-17817.master.004.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: HBASE-17817.master.004.patch > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch, HBASE-17817.master.003.patch, > HBASE-17817.master.004.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: HBASE-17817.master.003.patch > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch, HBASE-17817.master.003.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: HBASE-17817.master.001.patch > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: HBASE-17817.master.002.patch > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.002.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: (was: HBASE-17817.master.001.patch) > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: (was: HBASE-17817.master.002.patch) > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: HBASE-17817.master.002.patch > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Attachment: HBASE-17817.master.001.patch > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > Attachments: HBASE-17817.master.001.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steen Manniche updated HBASE-17817: --- Description: When a coprocessor throws a runtime exception (e.g. NPE), the regionserver handles this according to {{hbase.coprocessor.abortonerror}}. If the coprocessor was loaded on a specific table, the output in the logs give no indication as to which table the coprocessor was removed from (or which version, or jarfile is the culprit). This causes longer debugging and recovery times. was: When a coprocessor throws a runtime exception (e.g. NPE), the regionserver handles this according to {{hbase.coprocessor.abortonerror}}. The output in the logs give no indication as to which table the coprocessor was removed from (or which version, or jarfile is the culprit). This causes longer debugging and recovery times. > Make Regionservers log which tables it removed coprocessors from when aborting > -- > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver >Affects Versions: 1.1.2 >Reporter: Steen Manniche > Labels: logging > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)