Daniel Widdis
Daniel Widdis
Another thing to consider is how the processes will share/coordinate resources (CPU/threads, memory, etc.). If we were to launch an Extension as a Thread, we could pass it a `Runnable`...
> all the problems of JAR hells and such I'm thinking there are workarounds for that using different classloaders.
> **Approach 1** > > Pass an HTTP Header with each request originating from an extension with an extension identifier. It could be the more public extensionId used in the...
Hi @kokibas, this is a rather broad issue with many things you can do. Which part of it will you be doing?
> Hello @dbwiddis , I suggest using a singleton for each client to avoid sharing the same RestClient between multiple clients. This will allow closing the RestClient only once when...
> If so, it definitely makes sense to pass it around and initialize once. After posting this, the discussion on #616 made me wonder if we should be dealing with...
> when I tried to run OpenSearch with extensions enabled via "run.gradle," OpenSearch didn't pick up on this setting Could you be more specific on what changes you made in...
> The `RestClusterStateAction` class can probably called using the `opensearch-java` client with little overhead. No, it can't. Don't even try. I did, and failed gloriously. See #667 There's a TransportAction...
The underlying issue is that in the plugin model, a copy of the plugin is running on every node in the OpenSearch cluster, so the cluster state is relevant for...
Most of the original request has been handled via other issues. Updated the initial comment to describe the one remaning task to do, (a)synchronizing the initialization sequence.