Log keyspace xxx does not exist at WARN level

Description

We have few clients connecting to nodes of another cluster due to some operational mistakes. We can detect such issues sooner if we log the invalid keyspave below at ERROR WARN level. (Note: level changed after the issue was open, see discussion below)

Environment

None

Pull Requests

None

Activity

Show:
Vishy Kasar
February 12, 2015, 6:14 PM

The team that encountered the issue requested it to be logged at the ERROR level. I can settle for WARN.

Olivier Michallat
April 1, 2015, 1:33 PM

WARN it is then. I updated the issue title and description.

Olivier Michallat
April 1, 2015, 3:09 PM

: given the simplicity, I've pushed this to 2.0 directly.

Andy Tolbert
April 1, 2015, 3:42 PM

Sounds good to me . I'll do a super quick validation and move to resolved.

Andy Tolbert
April 1, 2015, 5:41 PM

Validated on 2.0 that a warning is now surfaced in this case:

Fixed

Assignee

Olivier Michallat

Reporter

Vishy Kasar

Labels

None

PM Priority

None

Affects versions

None

Fix versions

Pull Request

None

Doc Impact

None

Size

None

External issue ID

None

External issue ID

None

Priority

Major
Configure