ninsmiracle commented on PR #1908:
URL: 
https://github.com/apache/incubator-pegasus/pull/1908#issuecomment-1965698883

   Now , when user config `force_send_no_idempotent_when_duplication` to true . 
We can dup non-idempotent write to backup cluster , and we can verify the data 
consistency by check the number rows of pegasus app.
   app in master-cluster
   
![image](https://github.com/apache/incubator-pegasus/assets/110282526/f3fc4c9d-198f-43b5-a830-4c16f97b6503)
   
   app in backup-cluster
   
![image](https://github.com/apache/incubator-pegasus/assets/110282526/0323de44-03e0-41df-be9c-7e1e23497994)
   
   
   And because the retries for non-idempotent writes will make influence of the 
 consistency between two clusters. So we should show the metric like following 
picture:
   ![How many non-idempotent write have been retried when doing 
duplication](https://github.com/apache/incubator-pegasus/assets/110282526/5f192af5-66eb-4737-b695-5702c9073778)
   
   show in backup cluster:
   ![How many non-idempotent write have been received by backup cluster 
](https://github.com/apache/incubator-pegasus/assets/110282526/7437dadf-c2e8-4a38-90fd-ecab02f5e776)
   
   
   
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to