Nick Knize
Nick Knize
> we use another threadpool as below which is most likely getting tracked This is what I was quickly skimming. We need to be sure it is getting tracked so...
Thx @Bukhtawar! I can see a good reason for moving this as a plugin (not module) to core. The progress not perfection here is that we would be adding the...
I'll dig deeper but my initial reaction would be to refactor the java client transport as a core library so we take the dependency on `opensearch-core` and a new `opensearch-transport`...
> The need to capture responses from the primary cluster also removes [Cross-Cluster Replication](https://opensearch.org/docs/latest/replication-plugin/index/) (CCR) as a solution to this problem. There are a lot of good design ideas here,...
> This approach made the request replay a bit complex, but it can avoid the synchronization... Replaying history from the translog is largely what CCR does (with some retention lease...
> @nknize Thanks for finding the time to put this writing up, do you see any particular model appealing to you more than others? I personally have pretty good experience...
Generally, in open source the leaner a process is, the better. Community members usually do not join meetings, so it's best to rely on good async habits (e.g., tldrs, scripts,...
> Thanks for documenting all of this the clarity is a great improvement - could you transform this issue's description into a pull request on the `RELEASING.md` so this is...
> What are the major pieces missing that are not in there? Maybe just add words? Possibly just words? Maybe a complete refactor of this documentation to be more community...