You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The report generated after a migration has either completed or failed is written on a single line in the resulting text file. The "\n\n" characters are printed literally in the file.
Example:
"Report for migration id=286ab45e-e0d7-4a5a-b5be-4df743c9bbc1\n\nStarted time: 2023-10-23T18:59:06.887555Z\n\nStatus: Completed\nCompleted time: 2023-10-23T14:59:07.730024-04:00\n\nThe migration of the following data structures was completed:\n\nIMap:\n- my-map2 (100 entries total) time 0h 0m 0s\n\nThe migration of the following data structures was canceled:\n\nThe migration of the following data structures was failed:\n\nThe migration of the following data structures was not started:\n\n"
This can be reproduced by following the instructions in the README included in the DMT package. These steps are:
docker run -p 127.0.0.1:5701:5701 -e HZ_CLUSTERNAME=source hazelcast/hazelcast:4.2.7
for i in {1..1000}; do clc -c source.yaml map --name my-map set key-$i value-$i --quiet; done && echo OK
github-actionsbot
changed the title
DMT: Migration report is printed on single line
DMT: Migration report is printed on single line [CLC-420]
Oct 24, 2023
The report generated after a migration has either completed or failed is written on a single line in the resulting text file. The "\n\n" characters are printed literally in the file.
Example:
This can be reproduced by following the instructions in the README included in the DMT package. These steps are:
docker run -p 127.0.0.1:5701:5701 -e HZ_CLUSTERNAME=source hazelcast/hazelcast:4.2.7
for i in {1..1000}; do clc -c source.yaml map --name my-map set key-$i value-$i --quiet; done && echo OK
docker run -e HZ_NETWORK_PORT_PORT=5901 -p 127.0.0.1:5901:5901 -e HZ_LICENSEKEY="yourlicensekey" -e HZ_CLUSTERNAME=target hazelcast/hazelcast-enterprise:5.3.2-SNAPSHOT-slim
HZ_NETWORK_PORT_PORT=5702 HZ_CLUSTERNAME=migration ./bin/hz start
./bin/dmt_[platform]_[arch] --config migration.yaml start migration_config --yes
Check the generated
migration_report_*.txt
file.The text was updated successfully, but these errors were encountered: