hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Thomas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1840) RowLock fails when used with IndexTable
Date Tue, 15 Sep 2009 19:35:57 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Thomas updated HBASE-1840:
--------------------------------

    Status: Patch Available  (was: Open)

> RowLock fails when used with IndexTable
> ---------------------------------------
>
>                 Key: HBASE-1840
>                 URL: https://issues.apache.org/jira/browse/HBASE-1840
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: contrib
>    Affects Versions: 0.20.0
>         Environment: Ubuntu desktop 9.0.4, Sun Java 1.6.0_16, HBase 0.20.0, Hadoop 0.20.0
>            Reporter: Keith Thomas
>         Attachments: HBASE-1840.patch
>
>
> The following exception is thrown when using RowLock to update a row in an IndexedTable:
>     [junit] java.io.IOException: java.io.IOException: Invalid row lock
>     [junit] at org.apache.hadoop.hbase.regionserver.HRegion.getLock(HRegion.java:1640)
>     [junit] at org.apache.hadoop.hbase.regionserver.HRegion.put(HRegion.java:1244)
>     [junit] at org.apache.hadoop.hbase.regionserver.tableindexed.IndexedRegion.put(IndexedRegion.java:97)
>     [junit] at org.apache.hadoop.hbase.regionserver.HRegion.put(HRegion.java:1216)
>     [junit] at org.apache.hadoop.hbase.regionserver.HRegionServer.put(HRegionServer.java:1818)
>     [junit] at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
>     [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit] at java.lang.reflect.Method.invoke(Method.java:597)
>     [junit] at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:650)
>     [junit] at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
> NOTE #1: Line numbers in stacktrace may not make sense because I've been hacking in loads
of debug info. 
> NOTE #2: I attaching a fix which includes unit tests

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message