[
https://issues.apache.org/jira/browse/HBASE-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913381#comment-13913381
]
Nicolas Liochon commented on HBASE-10525:
-----------------------------------------
bq. Why would we not have interrupt on by default given you have done all this
work to make it work?
The name may not be perfect: when the option is not activated, an interrupt may
cut the tcp connection. activated, the write will be in a different thread, so
it won't be cut. However, it adds a Thread per region server, so I didn't
activated it by default. In interruption will still be possible, but if they
cut the tcp connection, the calls in progress will have to be retried.
Now that the rpc timeout issue is fixed, I hope to be able to have a single
thread pool, so then the option will become useless, but there are a few days
of work ahead before removing this... The issue, as usual, is to have something
that works well under failures...
> Allow the client to use a different thread for writing to ease interrupt
> ------------------------------------------------------------------------
>
> Key: HBASE-10525
> URL: https://issues.apache.org/jira/browse/HBASE-10525
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.99.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.99.0
>
> Attachments: 10525.v1.patch, 10525.v2.patch, 10525.v3.patch,
> 10525.v4.patch, 10525.v5.patch, 10525.v6.patch, 10525.v7.patch,
> HBaseclient-EventualConsistency.pdf
>
>
> This is an issue in the HBASE-10070 context, but as well more generally if
> you want to interrupt an operation with a limited cost.
> I will attach a doc with a more detailed explanation.
> This adds a thread per region server; so it's otional. The first patch
> activates it by default to see how it behaves on a full hadoop-qa run. The
> target is to be unset by default.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
