[
https://issues.apache.org/jira/browse/DERBY-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581046#action_12581046
]
Øystein Grøvlen commented on DERBY-3562:
----------------------------------------
I think the issue may be that checkpointing is only happening at the master.
Hence, log files are garbage-collected on the master, but not on the slave. If
that is the case, one risk that with a long-running replication, the disk on
the slave side will fill up. 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.
> 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.
