db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3392) Performing failover on a database not being replicated should give a more meaningful error message.
Date Wed, 06 Feb 2008 10:55:14 GMT

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

V.Narayanan commented on DERBY-3392:
------------------------------------

The appropriate error messages are thrown in the RawStore when a
findServiceModule to find the Master Factory module fails indicating
that the database was not replicated in the first place.

I can either follow the suggestion given by Jorgen on this issue

1) "I think SQLState.REPLICATION_UNABLE_TO_STOP_MASTER would give a better 
    error message than REPLICATION_FAILOVER_UNSUCCESSFUL in RawStore#failover
    if that message was slightly changed to "Could not perform replication operation 
    because... ". 
        In this case I will change REPLICATION_UNABLE_TO_STOP_MASTER to 
    something more generic like REPLICATION_UNABLE_TO_PERFORM_OPERATION.
        I will have to change other places where the former message was being used.

2) or add another message specific to Failover and use that.

Unless I contradicted I will go for 2) which requires lesser changes.

> Performing failover on a database not being replicated should give a more meaningful
error message.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3392
>                 URL: https://issues.apache.org/jira/browse/DERBY-3392
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>
> Oystein says
> "If I do failover on a database where replication has not been started, I get the following:
> ij version 10.4
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass';
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass;failover=true';
> ERROR XRE21: Error occurred while performing failover for database 'masterDB', Failover
attempt was aborted.
> I think I should rather get an error that says that database is not being replicated.
(I get that if I try to stop replication on a non-replicated database)."

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