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] [Updated] (HBASE-16739) Timed out exception message should include encoded region name
Date Mon, 03 Oct 2016 04:11:20 GMT

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

Ted Yu updated HBASE-16739:
---------------------------
       Resolution: Fixed
         Assignee: Ted Yu
     Hadoop Flags: Reviewed
    Fix Version/s: 1.4.0
                   2.0.0
           Status: Resolved  (was: Patch Available)

Thanks for the review, Jerry.

> Timed out exception message should include encoded region name
> --------------------------------------------------------------
>
>                 Key: HBASE-16739
>                 URL: https://issues.apache.org/jira/browse/HBASE-16739
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: 16739.v1.txt
>
>
> Saw the following in region server log repeatedly:
> {code}
> 2016-09-26 10:13:33,219 WARN org.apache.hadoop.hbase.regionserver.HRegion: Failed getting
lock in batch put, row=1
> java.io.IOException: Timed out waiting for lock for row: 1
>   at org.apache.hadoop.hbase.regionserver.HRegion.getRowLockInternal(HRegion.java:5151)
>   at org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3046)
>   at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2902)
>   at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2844)
>   at org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:692)
>   at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:654)
>   at org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2040)
> {code}
> Region name was not logged - making troubleshooting a bit difficult.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message