You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/08/07 04:47:14 UTC
[jira] Resolved: (HBASE-1752) when a regionserver shuts down writes
in progress are no retried by the client
[ https://issues.apache.org/jira/browse/HBASE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-1752.
-----------------------------------
Resolution: Invalid
Never mind. I'm going to mark this as invalid. It's inconvenient but does seem like client side is doing what it is supposed to be doing (and has been configured for). The application in this case should be retrying.
> when a regionserver shuts down writes in progress are no retried by the client
> ------------------------------------------------------------------------------
>
> Key: HBASE-1752
> URL: https://issues.apache.org/jira/browse/HBASE-1752
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Fix For: 0.20.0
>
>
> When a regionserver aborts, there is a window where clients are continuing to try to write to it, but the writes are failing:
> {noformat}
> Aug 4, 2009 6:47:25 AM net.iridiant.heritrix.writer.HBaseWriterProcessor innerProcessResult
> SEVERE: Failed write of Record: http://www.rdc.udel.edu/reports/development/profdev.pdf (in thread 'ToeThread #3: http://www.rdc.udel.edu/reports/development/profdev.pdf'; in processor 'Archiver')
> java.io.IOException: org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact region server 172.20.3.229:60020 for region content,23d6b92bc7eb100fc1294e6b124b7e75,1249198098627, row '23d6b92bc7eb100fc1294e6b124b7e75', but failed after 10 attempts.
> Exceptions:
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> java.net.ConnectException: Call to /172.20.3.229:60020 failed on connection exception: java.net.ConnectException: Connection refused
> at net.iridiant.heritrix.writer.HBaseWriter.write(Unknown Source)
> at net.iridiant.heritrix.writer.HBaseWriterProcessor.write(Unknown Source)
> at net.iridiant.heritrix.writer.HBaseWriterProcessor.innerProcessResult(Unknown Source)
> at org.archive.modules.Processor.process(Unknown Source)
> at org.archive.crawler.framework.ToeThread.processCrawlUri(Unknown Source)
> at org.archive.crawler.framework.ToeThread.run(Unknown Source)
> {noformat}
> The client does not retry, so the data is lost. Maybe we can get this in for RC2?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.