Details
-
Bug
-
Status: Resolved
-
Not specified
-
Resolution: Fixed
-
6.0.0, 5.4.6, 5.6.0, 5.6.2
-
None
Description
When the FTSlave initiates and starts to transfer chunks it reports the wrong information about the chunk(s):
00000011 2016-04-26 14:28:51.309 16129 16129 "Progress:" 00000012 2016-04-26 14:28:51.309 16129 16129 "[7] Init 0[0]->0[0]" 00000013 2016-04-26 14:28:51.309 16129 16129 "[32] Init 0[0]->0[0]" 00000014 2016-04-26 14:28:51.309 16129 16129 "[57] Init 0[0]->0[0]" 00000015 2016-04-26 14:28:51.309 16129 16129 "[82] Init 0[0]->0[0]" 00000016 2016-04-26 14:28:51.356 16129 16129 "Begin to transfer chunk 0: Start at length 0" 00000017 2016-04-26 14:32:31.366 16129 16129 "Begin to transfer chunk 1: Start at length 0" 00000018 2016-04-26 14:32:31.412 16129 16129 "Begin to transfer chunk 2: Start at length 0" 00000019 2016-04-26 14:32:31.458 16129 16129 "Begin to transfer chunk 3: Start at length 0" 0000001A 2016-04-26 14:32:31.474 16129 16129 "Results sent from slave 101"
The inits should reports the partition parameters,: input size and output size without [CRC].
When FTSlave reports about the current chunk transfer is started:
"Begin to transfer chunk 0: Start at length 0"
the message is suggesting there is a zero length data, but it isn't.
The "Begin transfer..." message/log entry should report the chunk (partiton) starting offset and size as well as the target/output offset and size:
"Begin to transfer chunk 0 (offset 0, size:60) to target (offset: 0, size: 60) " "Begin to transfer chunk 1 (offset 0, size:0) to target (offset: 60, size: 0) " "Begin to transfer chunk 2 (offset 0, size:0) to target (offset: 60, size: 0) "
jakesmith richardkchapman what is you opinion? What can be the target of it 6.0.2?
