geo: Add ability to create new txn status tables #10157
Comments
|
An easy way to test this locally could be by using custom placement info per tserver. We can start a 1 node cluster in zone A, then start 2 new TS, one in zone B and 3rd in zone C. Then we can update the cluster placement to RF3 across zones A,B,C. This will apply to all new tables by default. Finally, we can create 3 new txn tables and then set placement on them to RF1 and place them 1 each in zones A, B and C. In a unit test, this should also be pretty easy to replicate, as there we have explicit ways to start tservers with custom flags. cc @sanketkedia maybe for an example of test with custom placement. |
|
Small minor point: |
Summary: Added `yb-admin create_transaction_table` which creates a transaction status table of the passed in name, e.g. ``` yb-admin create_transaction_table transactions_us ``` to create `system.transactions_us`. This table's placement can be modified normally with `yb-admin modify_table_placement_info`. Test Plan: Added test to create three transaction tables with placement set in different zones. `ybd --cxx-test tools_yb-admin-test --gtest_filter AdminCliTest.TestCreateTransactionStatusTablesWithPlacements` Reviewers: bogdan, skedia, rthallam, dsrinivasan Reviewed By: dsrinivasan Subscribers: ybase Differential Revision: https://phabricator.dev.yugabyte.com/D13356
|
Added with 10f931b. |
Context: #9980
We need to be able to create new txn status tables and set custom placement policies for them.
CatalogManager::CreateTransactionsStatusTableIfNeeded, so we could figure out how to reuse that / retrofit that. Perhaps a new yb-admin command that creates a similar CreateTableRPC.modify_table_placement_info, per table, which Deepthi added back when we added YCQL support for geo-partition.The text was updated successfully, but these errors were encountered: