[
https://issues.apache.org/jira/browse/HBASE-12988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613401#comment-14613401
]
Lars Hofhansl commented on HBASE-12988:
---------------------------------------
Thanks [~apurtell]. Absolutely yes on the constant and hbase-defaults.xml.
Not sure I follow the part with the DEBUG message. Future.get() will rethrow
any error it encounters and then the outer catch will process those in the same
way we do now.
So in effect the error handling is unchanged. The only difference is when
multiple tasks encounter an exception we only remember the last one... Is that
part what you meant? I wanted to give the other tasks a chance to run and then
only reschedule those that actually did encounter an error.
> [Replication]Parallel apply edits across regions
> ------------------------------------------------
>
> Key: HBASE-12988
> URL: https://issues.apache.org/jira/browse/HBASE-12988
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: hongyu bi
> Assignee: Lars Hofhansl
> Attachments: 12988-v2.txt, 12988-v3.txt, 12988-v4.txt, 12988.txt,
> HBASE-12988-0.98.patch, ParallelReplication-v2.txt
>
>
> we can apply edits to slave cluster in parallel on table-level to speed up
> replication .
> update : per conversation blow , it's better to apply edits on row-level in
> parallel
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
