db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3562) Number of log files (and log dir size) on the slave increases continuously
Date Tue, 25 Mar 2008 07:57:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581816#action_12581816
] 

Jørgen Løland commented on DERBY-3562:
--------------------------------------

> I do not think this is acceptable, and we need to look into how the recovery thread can
be modified to garbage collect log files when checkpoint log records are encountered.

I agree. This has to be fixed. 

I think it will be possible to use the checkpoints received from the master to discard old
log files on the slave. The checkpoint contains a low water mark pointing to the oldest log
record that needs to be kept. Log older than the LWM should be discardable on the slave as
well. Need some more investigation, though...

> Number of log files (and log dir size) on the slave increases continuously
> --------------------------------------------------------------------------
>
>                 Key: DERBY-3562
>                 URL: https://issues.apache.org/jira/browse/DERBY-3562
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0, 10.5.0.0
>         Environment: -
>            Reporter: Ole Solberg
>         Attachments: master_slave-db_size-6.jpg
>
>
> I did a simple test inserting tuples in a table during replication:
> The attached file 'master_slave-db_size-6.jpg' shows that 
> the size of the log directory (and number of files in the log directory)
> increases continuously during replication, while on master the size 
> (and number of files) never exceeds ~12Mb (12 files?) in this scenario.
> The seg0 directory on the slave stays at the same size as the master 
> seg0 directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message