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-3021) Replication: Add a ReplicationSlave controller that will manage replication on the slave side
Date Wed, 05 Sep 2007 09:38:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525034
] 

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

I want to refuse connections to a database that is in the slave mode. To do so, I intend to
add a check in BasicDatabase.java#setupConnection that throws a StandardException stating
"Cannot connect to a database in replication slave mode" or similar.

In SQLStates.java there is now a subset of error codes for repliation: XRExx. Initially, I
intended to use code XRE02.C for this error. However, this exception is thrown on connection,
which has error class 08 in the SQL specification. 

Any thoughts on whether the most appropriate error code for this would be:

* XRE02.C since it is a replication error message with session severity, or
* 0800x (e.g., 08006 - connection failure) since this is a connection error? 

> Replication: Add a ReplicationSlave controller that will manage replication on the slave
side
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3021
>                 URL: https://issues.apache.org/jira/browse/DERBY-3021
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Services
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>
> The replication slave role includes many tasks:
> * set up a network connection with the master
> * receive chunks of log from the master, and parse these into individual log records
> * append log records to the local log file
> * make sure that the recovery process is not allowed to access the logfile we are currently
writing to
> * etc
> This issue is for adding a controller that will start/stop/initiate all services needed
for the replication slave role.

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