[HBASE-12570] Improve table configuration sanity checking

• Type: Umbrella
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: James R. Taylor
• Created: 25/Nov/14 02:21
• Updated: 17/Jun/22 18:24
• Resolved: 11/Nov/16 18:05

Description

See PHOENIX-1473. If a split policy class cannot be resolved, then your HBase cluster will be brought down as each region server that successively attempts to open the region will not find the class and will bring itself down.

One idea to prevent this would be to fail the CREATE TABLE or ALTER TABLE admin call if the split policy class cannot be found.

Issue Links

• duplicates: HBASE-12573 Backport HBASE-10591 Sanity check table configuration in createTable
• relates to: PHOENIX-1473 Connecting with Phoenix client when Phoenix is not deployed on region server(s) takes down region server(s).

Sub-Tasks

• Backport HBASE-10591 Sanity check table configuration in createTable: Closed
• Sanity check encryption configuration before opening WAL or onlining regions: Closed
• Sanity check table coprocessor classes are loadable: Closed
• Sanity check other loadable classes from configuration: Closed