I'm experiencing some problems with the rollup jobs.
I'm using it to hourly aggregate data from several indices (abc_*).
It worked perfectly until yesterday at 2pm. Since then, it starts the indexing procedure, the trigger count increases, the 'current position' inside the JSON increases, but it doesn't add any document to the index it used until yesterday (hourly_abc).
Now I created a new job with exactly the same characteristics and it doesn't work either.
Though, data keeps flowing into abc_* indices (in fact the 'current position' is updated properly).
The only thing I changed yesterday is the Index Lifecycle Policy for the abc_* index, deleting them after 24h rather than 6h as it used to be. Though, why should it influence the rollup job?
What can be happening?