hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4462) Properly treating SocketTimeoutException
Date Tue, 21 Apr 2015 00:47:00 GMT

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

Andrew Purtell updated HBASE-4462:
----------------------------------
    Resolution: Incomplete
      Assignee:     (was: ramkrishna.s.vasudevan)
        Status: Resolved  (was: Patch Available)

> Properly treating SocketTimeoutException
> ----------------------------------------
>
>                 Key: HBASE-4462
>                 URL: https://issues.apache.org/jira/browse/HBASE-4462
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>         Attachments: HBASE-4462_0.90.x.patch, unittest_that_shows_us_retrying_sockettimeout.txt
>
>
> SocketTimeoutException is currently treated like any IOE inside of HCM.getRegionServerWithRetries
and I think this is a problem. This method should only do retries in cases where we are pretty
sure the operation will complete, but with STE we already waited for (by default) 60 seconds
and nothing happened.
> I found this while debugging Douglas Campbell's problem on the mailing list where it
seemed like he was using the same scanner from multiple threads, but actually it was just
the same client doing retries while the first run didn't even finish yet (that's another problem).
You could see the first scanner, then up to two other handlers waiting for it to finish in
order to run (because of the synchronization on RegionScanner).
> So what should we do? We could treat STE as a DoNotRetryException and let the client
deal with it, or we could retry only once.
> There's also the option of having a different behavior for get/put/icv/scan, the issue
with operations that modify a cell is that you don't know if the operation completed or not
(same when a RS dies hard after completing let's say a Put but just before returning to the
client).



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

Mime
View raw message