1. src_not_found.log

   The source end is not found, and when it tries to migrate the files in the given file list, the source file is not found.

   Example

   2015-12-31 17:13:48.014 bucket1 obj24
   2015-12-31 17:13:48.015 bucket1 obj25
   2015-12-31 17:13:48.016 bucket1 obj26

2. migrate_failed.log

   In case of an exception during the migration (including the failure in writing the destination end in the halfway during the migration, and the exception in file information at the read destination end is found during the verification after the migration or the destination end is not consistent with the source end), with low probability of occurrence, the policy FORCE_OVERWRITE is used for redo.

   Example

   2015-12-31 17:13:48.014 bucket1 obj24
   2015-12-31 17:13:48.015 bucket1 obj25
   2015-12-31 17:13:48.016 bucket1 obj26

3. redo_list.log

   If the migration task fails (including the exception in accessing the data or information of the source-end file during the migration, and the destination-end file is found non-existence during the verification after migration), it is required for redo.

   Example

   2015-12-31 17:13:48.014 bucket1 obj24
   2015-12-31 17:13:48.015 bucket1 obj25
   2015-12-31 17:13:48.016 bucket1 obj26

4. dst_not_match.log

   Only the check task is generated, indicating that the destination end is inconsistent with the source end, and it doesn't matter if just for migration.

   Example

   2015-12-31 17:13:48.014 bucket1 obj24
   2015-12-31 17:13:48.015 bucket1 obj25
   2015-12-31 17:13:48.016 bucket1 obj26

5. status.log

   The current progress is updated once every 3 seconds, and x/y indicates the processing progress, x represents the quantity that has been processed, y represents the total amount; when y is -1, it indicate that the list of files has not been read, and the list that has been migrated is marked with finished.

   Example:

   2015-12-31 17:13:42.013 object_list1.txt 2/2 finished 
   2015-12-31 17:13:45.014 object_list2.txt 3/-1 
   2015-12-31 17:13:48.014 object_list3.txt 4/6 

6. unsent.log

   An error is reported when the migration request is sent to server due to the unavailability of the network or server, indicating which files are rejected by server when attempting migration.

   Example

   2015-12-31 17:13:48.014 bucket1 obj24
   2015-12-31 17:13:48.015 bucket1 obj25
   2015-12-31 17:13:48.016 bucket1 obj26

7. client.log

   The client-end log records the distribution of each migration task as well as the situation of current client, and the average size of the file and the migration time of a single file can be analyzed from such log, thus adjusting the migration parameter and achieving efficient migration.

8. server.log

   The migration of server-end log mainly includes the process of file migration (head get put verify), and the request-id allows you to track the processing of a migration task.

The format of the 1st-6th log is the same as that of the file list provided except the generated time of the line at the beginning of each line.