cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damodar Reddy T (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-5616) [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA.
Date Tue, 31 Dec 2013 05:29:53 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Damodar Reddy T updated CLOUDSTACK-5616:
----------------------------------------

    Assignee: Damodar Reddy T

> [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA.
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5616
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5616
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Kiran Koneti
>            Assignee: Damodar Reddy T
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> At any instance of time we never know to which database (either M1 or M2) is the CS writing
the db changes changes.
> This creates some problems at the customer environment like
> 1)The customer doesn't have chance to go for maintenance or manual do a switch over from
one db to other if he has some network maintenance to perform.
> 2)There is no chance to check whether the db switch over has happened from the slave
to master after the db.cloud.secondsBeforeRetryMaster interval if the master comes back by
this time. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message