hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mayur (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-9109) Null pointer exception while invoking coprocessor.
Date Thu, 01 Aug 2013 14:35:48 GMT
Mayur created HBASE-9109:

             Summary: Null pointer exception while invoking coprocessor.
                 Key: HBASE-9109
                 URL: https://issues.apache.org/jira/browse/HBASE-9109
             Project: HBase
          Issue Type: Bug
          Components: Client, Coprocessors
    Affects Versions: 0.98.0
         Environment: OS - CentOS release 6.2 (Final)
JAVA - java version "1.6.0_22"
       OpenJDK Runtime Environment (IcedTea6 1.10.4) (rhel-
        OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
Configuration: 3 node cluster with Hadoop-3.0
            Reporter: Mayur
             Fix For: 0.98.0

This problem is observed when region server dies while an endpoint coprocessor is executing.
On the client side channel.getLastRegion() returns null and we get null pointer exception
while updating result map. 
Following stack-trace is seen on client:

Caused by: java.lang.NullPointerException
at org.apache.hadoop.hbase.util.Bytes.compareTo(Bytes.java:981)
at org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator.compare(Bytes.java:128)
at org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator.compare(Bytes.java:119)
at java.util.TreeMap.put(TreeMap.java:530)
at java.util.Collections$SynchronizedMap.put(Collections.java:1979)
at org.apache.hadoop.hbase.client.HTable$17.update(HTable.java:1372)
at org.apache.hadoop.hbase.client.HTable$18.call(HTable.java:1401)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message