i have curator in linux environment which is in live so i can't experiment with that . i need one clarification regarding the command
i have curator files in /home/hero/.curator . If i run the below cron job command whether it will run in dry-run mode correctly or it will delete the indices in the live environment.
If you're using the --dry-run flag in the cron job, it will still be a dry run. No changes will be made.
As far as logging is concerned, that will depend on how you have logging set in your curator.yml file. If it's unset, then yes, your logs will go to /home/hero/.curator/log.txt. If you have chosen a log file in the configuration, then that's where your log files will go.
It's totally fine to send the entire command in cron, just like you have here. The older, Curator v3 approach had very long command lines, which could sometimes cause errors in cron. You shouldn't have that problem with the current version of Curator.
When i executed the below command manually it am getting status
hero@1423:~/.curator$ curator --dry-run --config curator.yml create.yml >> log.txt
hero@1423:~/.curator$ cat log.txt
2017-03-28 07:59:54,071 INFO Preparing Action ID: 1, "create_index"
2017-03-28 07:59:54,082 INFO Trying Action ID: 1, "create_index": Create the index as named, with the specified extra settings.
2017-03-28 07:59:54,082 INFO DRY-RUN MODE. No changes will be made.
2017-03-28 07:59:54,082 INFO DRY-RUN: create_index "myindex" with arguments: {}
2017-03-28 07:59:54,082 INFO Action ID: 1, "create_index" completed.
2017-03-28 07:59:54,082 INFO Job completed.
When i did the same thing in cron tab using the above command it is showing empty log.txt file.
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.