redis query connection down after cassandra goesdown and comes up

[Vinod Nair]

In a cluster with 1 analytic s/database node, after Cassandra is bought online after going down, redis connection does not auto recover.

Logs are attached

[Vinod Nair (vinodnair)]

Analytic s logs attached

[Vinod Nair (vinodnair)]

analytics-node status

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/18704
Submitter: Sundaresan Rajangam (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/18705
Submitter: Sundaresan Rajangam (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/18704
Committed: http://github.org/Juniper/contrail-controller/commit/c55e3b5d701d238065cdb5f17904bb5994080cfc
Submitter: Zuul
Branch: master

commit c55e3b5d701d238065cdb5f17904bb5994080cfc
Author: Sundaresan Rajangam <email address hidden>
Date: Wed Mar 23 14:00:42 2016 -0700

Removed Redis-Query connection from process_status for analytics-api

There is no need for a separate Redis-Query connection as analytics-node
uses the same redis instance for Redis-UVE and Redis-Query. Even if
analytics-api were to report the status of Redis-Query connection, the
status gets updated only on receiving a query from the client, which is
not correct. Since Redis-UVE connection captures the status of the
redis-server, removed the Redis-Query connection from the
process_status.

Change-Id: Ifb917a49642e53412cea4b551da7cc6bd9894449
Closes-Bug: #1560263

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/18705
Committed: http://github.org/Juniper/contrail-controller/commit/597367641b6c83c30582dc403b0b95e20aaf41a5
Submitter: Zuul
Branch: R3.0

commit 597367641b6c83c30582dc403b0b95e20aaf41a5
Author: Sundaresan Rajangam <email address hidden>
Date: Wed Mar 23 14:00:42 2016 -0700

Removed Redis-Query connection from process_status for analytics-api

There is no need for a separate Redis-Query connection as analytics-node
uses the same redis instance for Redis-UVE and Redis-Query. Even if
analytics-api were to report the status of Redis-Query connection, the
status gets updated only on receiving a query from the client, which is
not correct. Since Redis-UVE connection captures the status of the
redis-server, removed the Redis-Query connection from the
process_status.

Change-Id: Ifb917a49642e53412cea4b551da7cc6bd9894449
Closes-Bug: #1560263
(cherry picked from commit c55e3b5d701d238065cdb5f17904bb5994080cfc)