Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 11 Oct 2012 19:57:02 +0000 (UTC)
From: "Aleksandr Shulman (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <2002427933.32832.1349985422985.JavaMail.jiratomcat@arcas>
In-Reply-To: <508183190.32493.1349979424914.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HBASE-6978) Minor typo in ReplicationSource
 SocketTimeoutException error handling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksandr Shulman updated HBASE-6978:
-------------------------------------

    Attachment: patch-hbase-6978.patch

A proposed fix for this issue. Added a space.
                
> Minor typo in ReplicationSource SocketTimeoutException error handling
> ---------------------------------------------------------------------
>
>                 Key: HBASE-6978
>                 URL: https://issues.apache.org/jira/browse/HBASE-6978
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 0.92.1, 0.94.2, 0.96.0
>            Reporter: Aleksandr Shulman
>            Priority: Trivial
>             Fix For: 0.94.2, 0.94.3, 0.96.0
>
>         Attachments: patch-hbase-6978.patch
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> The user gets an error message on socket timeout exception:
> The words "the" and "call" need a space between them. Fix is trivial.
> 2012-10-11 11:09:06,154 DEBUG org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Encountered a SocketTimeoutException. Since thecall to the remote cluster timed out, which is usually caused by a machine failure or a massive slowdown, sleeping 1000 times 100
> The error is present in .92 and onward all the way through to the trunk. Fix should go into all those branches.

--
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