I've created a new rollup job using the PUT _rollup/job/<job_id> api. I received an acknowledged response and the new rollup index is created. However, when I try to start the job using POST _rollup/job/<job_id>/_start, there is a resource not found exception and the reason being "Task for Rollup Job [<job_id>] not found".
When I run GET _rollup/job/*, the job_id I just created does not appear in the response (thus I am unable to start it). Has anyone faced this issue before and how do I solve it? I think this is similar to the issue discussed in https://github.com/elastic/elasticsearch/issues/45247 but the fix doesn't seem to solve my problem.
Sure, so I have a few indices which store historical data. Those indices name start with datalog.gl_* (for eg: datalog.gl_sep20). I then create the rollup job through this:
However when I try to start the rollup job through curl -X POST "localhost:9200/_rollup/job/compress/_start?pretty", there is an error saying resource not found task for rollup job not found.
What response do you get from Elasticsearch for that curl?
Can you please post the full command and response when you request the job to start?
What is the output from GET /_rollup/job
Hi @warkolm just as a follow up to what do you think of this problem. It seems really similar to the issue raised in the github (I included the link on my first thread)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.