Log

1. src_not_found.log

   Source location not found. When attempting to migrate files from the specified file list, the user is unable to locate the source files.

   Example:

   Java Copy

   12015-12-31 17:13:48.014 bucket1 obj24
   22015-12-31 17:13:48.015 bucket1 obj25
   32015-12-31 17:13:48.016 bucket1 obj26

2. migrate_failed.log

   Migration exceptions (e.g., failure during destination location write, abnormal file information at the destination location during post-migration check, or the data at the source location is inconsistent with that at the destination location) are of probability of occurrence, but require the redo with the FORCE_OVERWRITE strategy.

   Example:

   Java Copy

   12015-12-31 17:13:48.014 bucket1 obj24
   22015-12-31 17:13:48.015 bucket1 obj25
   32015-12-31 17:13:48.016 bucket1 obj26

3. redo_list.log

   Migration tasks may fail due to issues such as abnormal file data or information at the source location during migration, or missing files at the destination location during a post-migration check. In such cases, the task must be redone.

   Example:

   Java Copy

   12015-12-31 17:13:48.014 bucket1 obj24
   22015-12-31 17:13:48.015 bucket1 obj25
   32015-12-31 17:13:48.016 bucket1 obj26

4. dst_not_match.log

   Only check tasks will be created, which indicate inconsistencies between the source and destination locations. Ignore these inconsistencies if they are only for migration purposes.

   Example:

   Java Copy

   12015-12-31 17:13:48.014 bucket1 obj24
   22015-12-31 17:13:48.015 bucket1 obj25
   32015-12-31 17:13:48.016 bucket1 obj26

5. status.log

   It is the current progress, updating every 3 seconds. x/y indicates the processing progress, where x is the number of processed files and y is the total number of files. Y = -1 indicates the file list has not been read fully, and a finished marker will be added after the list migration is completed.

   Example:

   Java Copy

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

6. unsent.log

   Network or server unavailability may result in migration request errors, which indicate that the server rejected specific files during migration attempts.

   Example:

   Java Copy

   12015-12-31 17:13:48.014 bucket1 obj24
   22015-12-31 17:13:48.015 bucket1 obj25
   32015-12-31 17:13:48.016 bucket1 obj26

7. client.log

   Client logs record the distribution of migration tasks as well as the current status of the client. These logs can be analyzed to determine metrics like the average file size and migration time per file, which can help adjust migration parameters for better efficiency.

8. server.log

   Migration server logs primarily document the file migration processes (head, get, put, and verify). The progress of specific migration tasks can be tracked using the request ID.

Logs 1 through 6 follow the same format as the provided file list, with the addition of the generation time for each line at the start.