We notice if we are updating just one column of the document that already indexed in ES for some reason the disk space size of the node temporary double to the document size. And then after it successful indexed roughly 10 minutes after the space size goes back down to its original size.
We just want to know is this normal behaviour?
And the time taken for the space size to go down is it configurable?
we just need these information to plan out the disk space allocation that we need for each nodes that will work for our use cases when go live.