db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3169) Add documentation for replication
Date Mon, 17 Mar 2008 20:30:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579588#action_12579588

Kim Haase commented on DERBY-3169:

Thanks very much, Jørgen. I'm working on the new topics for the Tuning Guide, and I have
a few more followup questions.

Which log are replication messages written to -- the derby.log file, or the transaction log
file that gets shipped from the master to the slave? I'm guessing the derby.log file.

Also, just to clarify -- when you say "min <= (max/10)" does that mean that it is the responsibility
of the user to make sure that the min value is less than or equal to a tenth of the max value?
What would happen if the user set the minLogShippingInterval to 2500 without also changing
the maxLogShippingInterval? I am guessing that this would be allowed but would result in bad
performance -- is that right?

Are these properties system-wide or database-wide, or can they be either? See http://db.apache.org/derby/docs/dev/tuning/ctunproper51399.html
for definitions of these terms. 

Are these properties dynamic or static? See http://db.apache.org/derby/docs/dev/tuning/ctunsetprop824615.html
for definitions of these terms. 

> Add documentation for replication
> ---------------------------------
>                 Key: DERBY-3169
>                 URL: https://issues.apache.org/jira/browse/DERBY-3169
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Jørgen Løland
>            Assignee: Kim Haase
>         Attachments: DERBY-3169-2.diff, DERBY-3169-2.stat, DERBY-3169-2.zip, DERBY-3169-3.diff,
DERBY-3169-3.zip, DERBY-3169.diff, DERBY-3169.stat, DERBY-3169.zip

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

View raw message