Minor Description
Currently, since there is no split policy defined for SYSTEM.CHILD_LINK, it can split by default.
If SYSTEM.CHILD_LINK does split, then when the client invokes ConnectionQueryServices.childLinkMetaDataCoprocessorExec(), we always invoke the endpoint on the first region that contains linking rows for that parent (see this).
Thus, no matter which region would actually contain the parent→child link, the first region is the one that has to always service the request and its RS finally issues the mutation to the correct region. Note that the mutateRowsWithLocks() call inside ChildLinkMetaDataEndpoint.createViewAddChildLink() doesn’t fail even if the region doesn’t contain that row since we pass in an empty list for rowsToLock.
During view creation, this request will lead to a Put of just 1 row and we have all the information to be able to pass in the exact row key instead of just the prefix (parent tenantId, parent schema, parent name). This should distribute load to all regions of SYSTEM.CHILD_LINK.
Attachments
Attachments
Issue Links
- links to