reddycharan commented on a change in pull request #1281: Issue #570: 
Introducing EntryLogManager.
URL: https://github.com/apache/bookkeeper/pull/1281#discussion_r176653861
 
 

 ##########
 File path: 
bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/SortedLedgerStorage.java
 ##########
 @@ -209,16 +202,12 @@ public void onSizeLimitReached(final Checkpoint cp) 
throws IOException {
             public void run() {
                 try {
                     LOG.info("Started flushing mem table.");
-                    long logIdBeforeFlush = entryLogger.getCurrentLogId();
                     memTable.flush(SortedLedgerStorage.this);
-                    long logIdAfterFlush = entryLogger.getCurrentLogId();
                     // in any case that an entry log reaches the limit, we 
roll the log and start checkpointing.
                     // if a memory table is flushed spanning over two entry 
log files, we also roll log. this is
                     // for performance consideration: since we don't wanna 
checkpoint a new log file that ledger
                     // storage is writing to.
-                    if (entryLogger.reachEntryLogLimit(0) || logIdAfterFlush 
!= logIdBeforeFlush) {
-                        LOG.info("Rolling entry logger since it reached size 
limitation");
-                        entryLogger.rollLog();
+                    if (entryLogger.rollLogsIfEntryLogLimitReached()) {
 
 Review comment:
   i don't think it is significant to have any perf impact. First of all this 
will be called once EntryMemTable reaches size limit, and in this method I'm 
getting a collection of active entrylogs (in this case just one) and checks its 
size. For entrylogperledger this collection is required but for single entrylog 
it might not be required, but I want common implementation and it is called 
just once per EntryMemTable size limit, so it is not a thing to be concerned 
about.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to