For taking a snapshot using curator it is showing different results when i used it in cron job?


I use the curator in cron job for taking periodic snapshot, i kept cron job for every minute ,and send the output to another file. When i see the file, sometimes it is executing perfectly but sometimes it is not . I don't why?

FYI-My ES cluster is hosted in azure with 5 nodes consists each node in one VM.

admin@data-2:~/.curator$ cat logs.txt
2017-03-30 10:39:09,174 INFO      Trying Action ID: 1, "snapshot": Snapshot  logstash- prefixed indices older than 1 day (based on index creation_date) with the default snapshot name pattern of 'curator-%Y-%m%-d%'.  Wait for the snapshot to complete.  Do not skip the repository filesystem access check.  Use the other options to create the snapshot.
2017-03-30 10:39:09,215 INFO      DRY-RUN MODE.  No changes will be made.
2017-03-30 10:39:09,215 INFO      DRY-RUN: snapshot: curator-2017-03-30 in repository azure_backup with arguments: {'indices': u'car,vehicle', 'partial': False, 'ignore_unavailable': False, 'include_global_state': True}
2017-03-30 10:39:09,215 INFO      Action ID: 1, "snapshot" completed.
2017-03-30 10:39:09,215 INFO      Job completed.
2017-03-30 10:40:01,364 INFO      Preparing Action ID: 1, "snapshot"
2017-03-30 10:41:01,361 INFO      Preparing Action ID: 1, "snapshot"
2017-03-30 10:42:01,370 INFO      Preparing Action ID: 1, "snapshot"

For 10:39 It is executed fine but for 10:40,10:41 and 10:42 it is not good?

May be this is timeout field or due to lack of azure server performance ?


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.