amitai stern

Thanks for starting the conversation @dblock I suggest a back tracking method to deduce a process. Assuming a plugin is in the default distribution is a testament to the popularity...

Thanks @rursprung this is a valid point! I will amend the documentation and make sure the path is defined correctly.

@aswath86 making any assumptions on the shards count can cause unpredictable issues. In logging there are sudden spikes, and/or night/day activity patterns of different types (spiking high to a decreasing-saw-tooth...

> This feature was successfully implemented via a python script that runs every hour, which updates the primary count of the index for the sub-sequent rollover, on a large cluster...

@aswath86 I have a different approach to suggest: Rather than have the algorithm added as a feature how about enriching the policy with a way to make whatever shard adjustment...

@aswath86 and I will meet in the next week or so and add a summary of our discussion over here. just so we can expedite the conversation - does anyone...

> Thanks @AmiStrn I'd love to join! > > BTW, > > > enriching the policy with a way to make whatever shard adjustment rule the user wants > >...

@aswath86 Thanks! can you add that to the feature description above? if you want to clarify that it is added later you can append it after adding a line and...

Thanks for the meeting @aswath86 @Jon-AtAWS and Robert (what is your github handle?) Summary: - I am not opposed to the RFC, as we agree that the project should have...

An opt out flag (for this entire proposed module functionality) in the cluster settings is basically the only way to ensure that disregarding security would be done on purpose rather...