You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Damodar Reddy T (JIRA)" <ji...@apache.org> on 2014/01/03 14:16:53 UTC

[jira] [Resolved] (CLOUDSTACK-5679) No Error message is shown when the Connection from the MS is lost Db server in case of multiple MS and DB HA enabled.

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

Damodar Reddy T resolved CLOUDSTACK-5679.
-----------------------------------------

    Resolution: Cannot Reproduce

When we are adding a rule to the iptables to block the connection it is not dropping connections which are already established and new connections are rejected to that DB node.. 

Kiran: I am not sure how to add a rule to drop even established connections as well, so I tested by stopping the db node and able to see exceptions in logs of 2nd MS node..

> No Error message is shown when the Connection from the MS is lost Db server in case of multiple MS and DB HA enabled.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5679
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5679
>             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
>
>
> Setup and issue details:
> 1)Created a CS setup with multiple MS say MS1 and MS2 with DBHA enabled. 
> 2)Created a DB replication has 2 db servers say DB1 and DB2. 
> 3)Initially the setup was in such a way that both MS1 and MS2 are talking to the DB1 and DB2 was acting as a slave. 
> 4)Then Blocked the communication from the MS2 to DB1 using the IPtables. 
> 5)When the connection is blocked from the MS2 to DB1 there is no error message shown in the logs and it simply switches to the DB2 . 



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