[HBASE-10525] Allow the client to use a different thread for writing to ease interrupt

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.99.0
• Fix Version/s: 0.99.0, hbase-10070
• Component/s: Client
• Hadoop Flags: Reviewed

Release Note

If hbase.ipc.client.allowsInterrupt is set to true (default being false), the writes are performed in a different thread. This workarounds a Java limitation with interruptions and i/o; and limits the impact of interrupting a client call. It's strongly recommended to activate this parameter when using tables with multiple replicas.

• Assignee: Nicolas Liochon
• Reporter: Nicolas Liochon
• Created: 13/Feb/14 15:10
• Updated: 21/Feb/15 23:35
• Resolved: 24/Feb/14 10:14

Description

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.

Issue Links

• is related to: HBASE-10355 Failover RPC's from client using region replicas
• is required by: HBASE-10070 HBase read high-availability using timeline-consistent region replicas