db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-3205) Replication: Add connection url command options for starting and stopping slave
Date Mon, 14 Jan 2008 15:20:34 GMT

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

oysteing edited comment on DERBY-3205 at 1/14/08 7:18 AM:
-----------------------------------------------------------------

I applied the startSlave_1a.diff patch, and was able to start a slave, and a master was able
to connect.

However, I am not quite satisfied with the messages I got:

> java -jar jars/sane/derbyrun.jar ij
ij version 10.4
ij> connect 'jdbc:derby:slaveDB;startSlave=true';
ERROR 08004: Connection refused to database 'slaveDB' because it is in replication slave mode.
ij> connect 'jdbc:derby:slaveDB';
ERROR XJ001: Java exception: 'ASSERT FAILED Unexpected - There is no valid authentication
service for the database!: org.apache.derby.shared.common.sanity.AssertFailure'.
ij> connect 'jdbc:derby:slaveDB;startSlave=true';
ERROR XJ001: Java exception: 'ASSERT FAILED Unexpected - There is no valid authentication
service for the database!: org.apache.derby.shared.common.sanity.AssertFailure'.
ij> 

For the first connection, I think it would be good if it said something
about the slave having been started.  The current message may lead one
to think that the database was already in slave mode before the
connection was attempted.

For the second connection, I would have expected the first message.  I
have not tried to run an insane version to see what happens when the
assert is not hit.

For the third connection, it would be good if a warning was given that
the database was already in slave mode.


      was (Author: oysteing):
    I applied the startSlave_1a.diff patch, and was able to start a slave
, and a master was able to connect.

However, I am not quite the messages I got:

> java -jar jars/sane/derbyrun.jar ij
ij version 10.4
ij> connect 'jdbc:derby:slaveDB;startSlave=true';
ERROR 08004: Connection refused to database 'slaveDB' because it is in replication slave mode.
ij> connect 'jdbc:derby:slaveDB';
ERROR XJ001: Java exception: 'ASSERT FAILED Unexpected - There is no valid authentication
service for the database!: org.apache.derby.shared.common.sanity.AssertFailure'.
ij> connect 'jdbc:derby:slaveDB;startSlave=true';
ERROR XJ001: Java exception: 'ASSERT FAILED Unexpected - There is no valid authentication
service for the database!: org.apache.derby.shared.common.sanity.AssertFailure'.
ij> 

For the first connection, I think it would be good if it said something
about the slave having been started.  The current message may lead one
to think that the database was already in slave mode before the
connection was attempted.

For the second connection, I would have expected the first message.  I
have not tried to run an insane version to see what happens when the
assert is not hit.

For the third connection, it would be good if a warning was given that
the database was already in slave mode.

  
> Replication: Add connection url command options for starting and stopping slave
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-3205
>                 URL: https://issues.apache.org/jira/browse/DERBY-3205
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: V.Narayanan
>         Attachments: derby-3205_startslave_dontcommit.diff, derby-3205_startslave_dontcommit.stat,
failover_impl_3205_NotForCommit_v1.diff, failover_impl_3205_NotForCommit_v1.stat, startSlave_1a.diff,
startSlave_1a.stat, StopSlave_impl_3205_NotForCommit_v1.diff, StopSlave_impl_3205_NotForCommit_v1.stat
>
>
> Add commands to start and stop the replication slave using properties or connection url.
Example:
> 'jdbc:derby:<host><dbname>;startSlave=true';
> 'jdbc:derby:<host><dbname>;stopSlave=true';
> 'jdbc:derby:<host><dbname>;failover=true;
> Connection url options that must be recognized:
> startSlave=true
> stopSlave=true
> failover=true
> slaveHost=<host> (optional, defaults to localhost) (only for startSlave)
> slavePort=<port> (optional, defaults to 8001) (only for startSlave)
> See functional specification on Derby-2872 for further details.

-- 
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