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)
The team that encountered the issue requested it to be logged at the ERROR level. I can settle for WARN.
WARN it is then. I updated the issue title and description.
: given the simplicity, I've pushed this to 2.0 directly.
Sounds good to me . I'll do a super quick validation and move to resolved.
Validated on 2.0 that a warning is now surfaced in this case: