MeihanLi opened a new issue, #12507: URL: https://github.com/apache/pinot/issues/12507
It seems currently Adaptive Server Selector is partially supported for strictReplicaGroup. But it breaks the assumption that by default, for strictReplicaGroup routing, brokers will route servers from 1 replica group only. I tested and figured out that for an upsert table with 2 replica groups, queries can be routed to servers from 2 replica groups depending on the server performance. For example, a tenant has 4 servers, the table has 2 partitions, 2 replicas, 2 replica groups. For select count(*) query, it can pick serverA and serverD from 2 different RGs to serve the query. ``` RG assignment: RG 0: serverA, serverB RG 1: serverC, serverD ``` ``` segments are assigned as below: partition 0 serverA serverC partition 1 serverB serverD ``` Are there any concerns on turning on adaptive server selector for strictReplicaGroup routing tables except that? Also I was wondering if anyone is looking into supporting numReplicaGroupsToQuery with Adaptive Server Selection. What's the plan on support it? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
