Hello @TheFixer Thanks for using Cloudera Community. To your queries, Please find the details below: (I) Concerning below log tracing, Each Column Family has their own MemStore & HBase ensure the Flush happens before an Edit is too old. A WAL can't be archived unless the corresponding entries from the WAL remain Un-flushed from the MemStore. These logging aren't a concern, yet PeriodicMemstoreFlusher working as designed. MemstoreFlusherChore requesting flush of table 1. because K has an old edit so flush to free WALs after random delay 65889ms (II) Concerning below log tracing, the same indicates the Flush has Completed by "MemStoreFlusher.1" (Defined by "hbase.hstore.flusher.count") of size ~6.68MB & the SequenceId indicates the Sequence ID associated with the LastEdit flushed. This Sequence ID is used to compare with Edits in WAL prior to archiving the WAL. 2022-10-29 12:21:46,170 INFO [MemStoreFlusher.1] regionserver.HRegion: Finished flush of dataSize ~6.68 MB/7002393, heapSize ~19.57 MB/20517200, currentSize=0 B/0 for ad1bd353d9ae0c52e30a935c5d06ecfa in 335ms, sequenceid=25141679, compaction requested=true (III) Finally, the CompactionQueue indicates the Size of Major (Long) & Minor (Short) Compaction. Compaction/Split Queue summary: compactionQueue=(longCompactions=111975:shortCompactions=35811), splitQueue=0 All the above Logging are HBase Internals & shouldn't be a concern for Customer, unless Customer is observing any impact. Your Team should review (If not done yet) the below links for details around the Flush Internals & Compaction Algorithms: (I) MemStore Flush Configuration (II) Conditions For MemStore Flush (III) Compaction Alogrithm Kindly review & let us know if your Team have any queries. Regards, Smarak
... View more
