[PHOENIX-3994] Index RPC priority still depends on the controller factory property in hbase-site.xml

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.11.0
• Fix Version/s: 4.12.0
• Labels: secondary_index
• Assignee: Samarth Jain
• Reporter: Sergey Soldatov
• Created: 06/Jul/17 04:31
• Updated: 09/Oct/19 14:19
• Resolved: 22/Aug/17 00:30

Description

During PHOENIX-3360 we tried to remove dependency on hbase.rpc.controllerfactory.class property in hbase-site.xml since it cause problems on the client side (if client is using server side configuration, all client request may go using index priority). Committed solution is using setting the controller factory programmatically for coprocessor environment in Indexer class, but it comes that this solution doesn't work because the environment configuration is not used for the coprocessor connection creation. We need to provide a better solution since this issue may cause accidental locks and failures that hard to identify and avoid.

Issue Links

• causes: PHOENIX-5511 Update documentation on secondary indexing configuration
• relates to: PHOENIX-3983 Index rebuild scans should not be using the ServerRpcControllerFactory
• relates to: PHOENIX-3970 Ensure that automatic partial index rebuilds are served from the index handler pool
• relates to: PHOENIX-3974 Create index may issue a distributed dead lock due lack of handlers
• relates to: PHOENIX-3360 Secondary index configuration is wrong