[
https://issues.apache.org/jira/browse/HBASE-24877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214598#comment-17214598
]
Hudson commented on HBASE-24877:
--------------------------------
Results for branch branch-2
[build #77 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/77/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/77/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/77/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/77/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/77/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/77//console].
> Add option to avoid aborting RS process upon uncaught exceptions happen on
> replication source
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-24877
> URL: https://issues.apache.org/jira/browse/HBASE-24877
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 3.0.0-alpha-1, 2.4.0
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
>
> Currently, we abort entire RS process if any uncaught exceptions happens on
> ReplicationSource initialization. This may be too extreme on certain
> deployments, where custom replication endpoint implementations may choose to
> do so when remote peers are unavailable, but source cluster shouldn't be
> brought down entirely. Similarly, source reader and shipper threads would
> cause RS to abort on any runtime exception occurrence while running.
> This patch adds configuration option (false by default, to keep the original
> behaviour), to avoid aborting entire RS processes under these conditions.
> Instead, if ReplicationSource initialization fails with a RuntimeException,
> it keeps retrying the source startup. In the case of readers/shippers runtime
> errors, it refreshes the replication source, terminating current source and
> its readers/shippers and creating new ones.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
