keith-turner opened a new issue, #5661: URL: https://github.com/apache/accumulo/issues/5661
**Is your feature request related to a problem? Please describe.** Ample creates a conditional writer per batch of conditional mutation written using Ample.conditionallyMutateTablets(). Each conditional writer creates new threads. Would it be beneficial to create a single conditional writer object per ample object like #5560 proposed for fate? The benefit would be less threads created in the manager and tservers when they use ample to update tablets metadata. Manager and tsevers would also get the benefit of batching conditional mutations over RPCs for writes to tablet servers that happen around the same time. The only potential drawback is that one thread writing a single mutation could get tied up in the same RPC as a thread writing a large group of mutations, this is probably not a problem for overall throughput but could make that single operation less responsive. Suspect this is ok and if it turns out to be a problem, then improvements could be made to the conditional writer. **Describe the solution you'd like** Explore creating a single conditional writer object when the ample object is created and use this conditional writer for all conditional writes in ample. -- 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]
