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-3169) Add documentation for replication
Date Mon, 25 Feb 2008 14:06:54 GMT

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

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

Hi Kim, 

The documentation looks really great! A few minor comments/suggestions:

Admin guide:
* Replicating databases
  - Suggestion: "In Derby, you *start* replicating databases by..."
  - No sharing -> Shared Nothing. The proposed text looks better,
    but "Shared Nothing" is a well-known term in distributed

* Stopping replication
  - this page does not mention the stopSlave command, which can
    be used to shutdown the slave database after the connection
    with the master has been lost. Is this intentional? I don't
    see stopSlave any other place in the admin guide.

* Forcing a failover:
  - Mention that failover must be performed on the master Derby
    instance if the replication network connection is up? The
    slave will only accept this command after loosing the
    connection with the master. I see that this is specified in
    the reference manual, so I'm not sure if it belongs here.

Reference guide:
* startSlave, end of first paragraph: Missing sentence following "See" 

> 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