dlmarion commented on PR #3262: URL: https://github.com/apache/accumulo/pull/3262#issuecomment-1830612379
> How will user assign tables to manager resource groups? Regarding this, the current mechanism is described in the **Resource Groups** section of https://cwiki.apache.org/confluence/display/ACCUMULO/A+More+Cost+Efficient+Accumulo. I was thinking that it would make sense to promote the `table.custom.assignment.group` property to a fixed property. Users would set this property on a table and would need to define a resource group with the same name so that the Manager could manage its tablets. Clients that connect to the Manager to perform table operations or initiate user Fate transactions would need to use the table property to determine which Manager to connect to (using the Resource Group name). The resource group name is already part of the ServiceLock object, so for example, we would modify `ClientContext.getManagerLocations` to iterate over the Managers in ZooKeeper and return the one with the correct resource group. Another option, if resource groups are a first class citizen, is to put the resource group name in the ZK path altho ugh that could lead to needing cleanup if a resource group was created and then removed. I haven't thought of everything, but this approach does solve some problems. > What manager would RPC operations that are not table related use? I think for instance-level operations and maybe even namespace level operations, any Manager could be used. > Thinking confluence documents would be a better place to explore this rather than here in issue. I can start a new Confluence page -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
