The region binding in HBase is invalid

The phoenix provides a standard JDBC interface, SQL is presented externally, structured data (the table structure is stored in the metadata table), and aggregate sort operations can be performed. These Phoenix tables are distinguished from the characteristics of ordinary HBase tables, most of them. It is implemented by a coprocessor. Since it is a coprocessor, it is considered to be server-side logic. Here, when the region is re-online, the balancer of the Hbase secondary index will determine whether the binding distribution needs to be made for the region through the list in the cache. It may be that the secondary index feature of Phoenix replaces the balancer, resulting in The cache is always empty, the binding is invalid, you need to add this cache logic in the Phoenix coprocessor, you can follow this idea to troubleshoot.