devmadhuu commented on PR #5430:
URL: https://github.com/apache/ozone/pull/5430#issuecomment-1779329158

   > > the incremental acquisition of OM snapshots in Recon is also normal, but 
the data in the OM snapshots in Recon is different from the content of OM 
snapshots. Therefore, I think there are some unknown issues with the 
incremental acquisition of OM snapshots in Recon
   > 
   > It'd be better to find out what could cause this issue and fix that, I 
know that it's hard to follow up on these, but ideally we shouldn't have these 
problems. Could you look into the logs and maybe share the differences you see? 
I still think that triggering a full update in Recon is expensive and in large 
clusters it can take a lot of time to process all the events that happened 
since startup.
   > 
   > Sometime back we added a button to trigger a delta update in Recon 
(#3821). We talked about having a similar button for full update but I think 
because of the above mentioned reasons we postponed it.
   > 
   > It'd be great to have the opinion of others, I'll tag some people as 
reviewer. If we go with this way I'd suggest to have it turned off by default 
for sure.
   
   I completely agree with @dombizita . We should find out reasons of 
inconsistencies in Recon data with OM data. For few minutes , there might be a 
lag as Recon works on eventual consistency strategy, so over next cycle of 
sync, Recon should be catching up slowly. We should discourage enabling full 
update due to large busy cluster. Anyways due to any raft log sequence number 
inconsistencies, we already have a fall back upon full snapshot update, so this 
seems overkill.


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