albertogpz commented on pull request #6601:
URL: https://github.com/apache/geode/pull/6601#issuecomment-872783056


   > I also ran this test:
   > 
   > 2 servers on site1
   > 1 server on site2
   > Partitioned region with parallel sender
   > 1,000,000 entries
   > Wan copy from site1 to site2
   > 
   > I see the correct behavior:
   > 
   > ```
   > Member | Status | Message
   > ------ | ------ | -----------------------
   > ln-2   | OK     | Entries copied: 504,400
   > ln-1   | OK     | Entries copied: 495,600
   > ```
   > 
   > If I redo the test and kill one of the site1 servers while the copy is 
happening, I see:
   > 
   > ```
   > Member | Status | Message
   > ------ | ------ | 
---------------------------------------------------------------------------------------------------------------------------
   > ln-1   | ERROR  | Execution failed. Error: 
org.apache.geode.distributed.PoolCancelledException: Pool PoolImpl@1539660778 
name=ny is shut down
   > ln-2   | OK     | Entries copied: 673,422
   > ```
   > 
   > or:
   > 
   > ```
   > Member | Status | Message
   > ------ | ------ | 
-------------------------------------------------------------------------------------------------------------------------------------------------
   > ln-1   | ERROR  | Execution failed. Error: 
org.apache.geode.InternalGemFireError: expected int part to be of type BYTE, 
part = partCode=unknown code 6 partLength=0
   > ln-2   | OK     | Entries copied: 844,202
   > ```
   > 
   > I'm not sure if this is ok or not. I guess I expected the function to be 
retried.
   
   My idea was that the function is not retried if there is an error in any of 
the servers. Automatic retrying could get tricky depending on the cases so I 
would rather have the command fail and let the user retry manually.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to