ArafatKhan2198 opened a new pull request, #5100:
URL: https://github.com/apache/ozone/pull/5100

   
   ## What changes were proposed in this pull request?
   
   While analyzing recent acceptance test runs, it has been observed that there 
is an issue with the new OM DB insights in Recon. The logs are flooded with 
messages like the following during tests such as acceptance HA and acceptance 
compat:
   ```
   recon_1  | 2023-07-13 10:09:48,563 [pool-27-thread-1] INFO 
impl.OzoneManagerServiceProviderImpl: Number of updates received from OM : 10, 
SequenceNumber diff: 30, SequenceNumber Lag from OM 0.
   recon_1  | 2023-07-13 10:09:48,563 [pool-27-thread-1] INFO 
impl.OzoneManagerServiceProviderImpl: Delta updates received from OM : 1 loops, 
30 records
   recon_1  | 2023-07-13 10:09:48,636 [pool-49-thread-1] WARN 
tasks.OmTableInsightTask: Update event does not have the old Key Info for 
#TRANSACTIONINFO.
   recon_1  | 2023-07-13 10:09:48,636 [pool-49-thread-1] WARN 
tasks.OmTableInsightTask: Update event does not have the old Key Info for 
/vol-xgtxr/buc-oplxd.
   recon_1  | 2023-07-13 10:09:48,638 [pool-49-thread-1] WARN 
tasks.OmTableInsightTask: Update event does not have the old Key Info for 
#TRANSACTIONINFO.
   recon_1  | 2023-07-13 10:09:48,638 [pool-49-thread-1] WARN 
tasks.OmTableInsightTask: Update event does not have the old Key Info for 
/vol-xgtxr/buc-oplxd....
   ```
   In the OmTableInsightTask, we need to handle update events only for tables 
that belong to the size-related group. For other tables, our focus is solely on 
the count, which is already managed by the PUT and DELETE methods. The size is 
the only factor that requires updating.
   
   Hence, for non-size related tables, we can skip the update step as it is 
unnecessary and not required for those specific tables. This fix will prevent 
unnecessary processing for non-size related tables and reduce excessive log 
messages. 
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-9052
   
   ## How was this patch tested?
   
   I have double-checked the logs for Recon and executed the existing unit 
tests to ensure that no unnecessary log messages are printed and that all 
endpoints work correctly.
   
   
   
   
   
   


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