hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4014) Coprocessors: Flag the presence of coprocessors in logged exceptions
Date Sun, 25 Sep 2011 03:52:26 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114125#comment-13114125
] 

Ted Yu commented on HBASE-4014:
-------------------------------

Since Jonathan asked, I felt that I must give an answer on the same day.
Here is my analysis for why TestRegionServerCoprocessorExceptionWithAbort failed occasionally.

The following call would create 25 regions for the test table:
{noformat}
    TEST_UTIL.createMultiRegions(table, TEST_FAMILY);
{noformat}
If we look at HBaseTestingUtility:
{noformat}
  public static final byte[][] KEYS = {
    HConstants.EMPTY_BYTE_ARRAY, Bytes.toBytes("bbb"),
{noformat}
We can see that the row in the test
{noformat}
      final byte[] ROW = Bytes.toBytes("bbb");
{noformat}
actually doesn't belong to the first region.

This means regionServer which we were waiting for may not host the region where NPE happened.
I modified the above line slightly and the test passed reliably:
{noformat}
      final byte[] ROW = Bytes.toBytes("aaa");
{noformat}

> Coprocessors: Flag the presence of coprocessors in logged exceptions
> --------------------------------------------------------------------
>
>                 Key: HBASE-4014
>                 URL: https://issues.apache.org/jira/browse/HBASE-4014
>             Project: HBase
>          Issue Type: Improvement
>          Components: coprocessors
>            Reporter: Andrew Purtell
>            Assignee: Eugene Koontz
>             Fix For: 0.92.0
>
>         Attachments: HBASE-4014.patch, HBASE-4014.patch, HBASE-4014.patch, HBASE-4014.patch,
HBASE-4014.patch
>
>
> For some initial triage of bug reports for core versus for deployments with loaded coprocessors,
we need something like the Linux kernel's taint flag, and list of linked in modules that show
up in the output of every OOPS, to appear above or below exceptions that appear in the logs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message