[
https://issues.apache.org/jira/browse/DERBY-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571702#action_12571702
]
narayanan edited comment on DERBY-3428 at 2/22/08 8:53 PM:
-------------------------------------------------------------
>It's OK with me to solve 3. in a follow-up patch since it involves code
>that was not touched by this patch. You mention that stream.close
>is not handled in this patch, so I guess a follow-up patch (or patch
>in another jira) is needed anyway.
I am NOT OK with resolving this issue in a follow-up patch attached to this
issue either.
This is a generic issue that has been raised in question to all the methods of
the replication
implementation, why should it be resolved in a issue that is related to a
specific problem
of the failover implementation.
I believe a separate JIRA needs to be raised indicating the problem and the fix
needs
to go there. If this JIRA is going to act as a stopper to committing this issue
I would be
OK with that.
was (Author: narayanan):
>It's OK with me to solve 3. in a follow-up patch since it involves code
>that was not touched by this patch. You mention that stream.close
>is not handled in this patch, so I guess a follow-up patch (or patch
>in another jira) is needed anyway.
I am NOT OK with resolving this issue in a follow-up patch attached to this
issue either.
This is a generic issue that has been raised in question to all the methods of
the replication
implementation, why should it be resolved in a issue that is related to a
specific problem
of the replication implementation.
I believe a separate JIRA needs to be raised indicating the problem and the fix
needs
to go there. If this JIRA is going to act as a stopper to committing this issue
I would be
OK with that.
> Doing a replication failover should shutdown the database and the connection
> should no longer be available
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3428
> URL: https://issues.apache.org/jira/browse/DERBY-3428
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: Derby3428.diff, Derby3428.stat
>
>
> Oystein says (as part of comments in Derby-3205)
> After executing a failover, I am told that the database is shut down, but I
> still able to use the connection to access the database:
> ij version 10.4
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass';
> ij> call syscs_util.syscs_freeze_database();
> 0 rows inserted/updated/deleted
> ij> connect
> 'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost';
> ij(CONNECTION1)> call syscs_util.syscs_unfreeze_database();
> 0 rows inserted/updated/deleted
> ij(CONNECTION1)> connect
> 'jdbc:derby:masterDB;user=oystein;password=pass;failover=true';
> ERROR XRE20: Failover performed successfully for database 'null', the
> database has been shutdown.
> ij(CONNECTION1)> select * from t;
> I
> -----------
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> 8
> 9
> 10
> 10
> 11 rows selected
> ij(CONNECTION1)>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
