I have several modified token filter factories that instantiate updated
filters. The contents are derived from a database instead of a flat file
and are refreshed at a set interval. I decide to change the update process
since refreshing periodically is not particularly efficient.
As of now, it is the filter factories' responsibility to update themselves,
but I am going to refactor the code so that the refresh refresh is
externalized. After review the code a bit more, I am going to create a
new NodesOperationRequest with the IndicesAnalysisService injected. Via
the IndicesAnalysisService, I should be able to find the appropriate filter
factories and send a refresh notice.
A NodesOperationRequest will send one request per node, correct? Started
down this path, but there is so much boilerplate code!
--
Ivan
On Tue, Sep 10, 2013 at 3:02 PM, joergprante@gmail.com <
joergprante@gmail.com> wrote:
The broadcast works by enumerating the shards, and yes, if a node hosts
more than one shard, a node has to execute multiple actions, one per shard.
You can't execute less actions. And executing actions on a node in parallel
is no real problem since we have multicore CPUs, thread pools, bandwidth on
I/O etc. plus the opportunity to add more nodes.
Not sure what you intend by refreshing analyzers. What is the challenge?
Reloading config files?
Jörg
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.