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

Brad Schoening updated CASSJAVA-98:
-----------------------------------
    Description: 
We get a lot of questions from users about this WARN level message in the Java 
driver 4.3+:
{quote}You specified dc1 as the local DC, but some contact points are from a 
different DC: Node(...); please provide the correct local DC, or check your 
contact points
{quote}
but as [@Erick Ramirez|https://the-asf.slack.com/team/URU06R75L] explains on a 
[StackOverflow 
answer|https://stackoverflow.com/questions/75799274/how-are-quorum-reads-handled-when-the-java-driver-only-contacts-nodes-in-local-d]
 this topic, "The contact points do not have anything to do with replicas and 
consistency levels."
 
This warning was added in 4.3, before cross-DC failover was re-introduced in 
release 4.10. Although I realize cross-DC failover is problematic, this message 
does not seem helpful or at the very least should be INFO instead of WARN.

App 1 may run in DC1 and App 2 in DC2, but they can share the same contact 
lists and implement their own failover when necessary, but without needing to 
update contact points.

It would be more reasonable to WARN when you've configured 
*advanced.load-balancing-policy.dc-failover.allow-for-local-consistency-levels* 
as True. Warning on the contact points specified doesn't seem right.

  was:
We get a lot of questions from users about this WARN level message in the Java 
driver 4.3+:
{quote}You specified dc1 as the local DC, but some contact points are from a 
different DC: Node(...); please provide the correct local DC, or check your 
contact points{quote}
but as [@Erick Ramirez|https://the-asf.slack.com/team/URU06R75L] explains on a 
[StackOverflow 
answer|https://stackoverflow.com/questions/75799274/how-are-quorum-reads-handled-when-the-java-driver-only-contacts-nodes-in-local-d]
 this topic, "The contact points do not have anything to do with replicas and 
consistency levels."
 
This warning was added in 4.3, before cross-DC failover was re-introduced in 
release 4.10. Although I realize cross-DC failover is problematic, this message 
does not seem helpful or at the very least should be INFO instead of WARN.

My App 1 may run in DC1 and App 2 in DC2, but they can share the same contact 
lists and implement their own failover when necessary, but without needing to 
update contact points.

It would be more reasonable to WARN when you've configured 
*advanced.load-balancing-policy.dc-failover.allow-for-local-consistency-levels* 
as True. Warning on the contact points specified doesn't seem right.


> Replace warning message when contact points are from a different DC
> -------------------------------------------------------------------
>
>                 Key: CASSJAVA-98
>                 URL: https://issues.apache.org/jira/browse/CASSJAVA-98
>             Project: Apache Cassandra Java driver
>          Issue Type: Improvement
>            Reporter: Brad Schoening
>            Priority: Normal
>
> We get a lot of questions from users about this WARN level message in the 
> Java driver 4.3+:
> {quote}You specified dc1 as the local DC, but some contact points are from a 
> different DC: Node(...); please provide the correct local DC, or check your 
> contact points
> {quote}
> but as [@Erick Ramirez|https://the-asf.slack.com/team/URU06R75L] explains on 
> a [StackOverflow 
> answer|https://stackoverflow.com/questions/75799274/how-are-quorum-reads-handled-when-the-java-driver-only-contacts-nodes-in-local-d]
>  this topic, "The contact points do not have anything to do with replicas and 
> consistency levels."
>  
> This warning was added in 4.3, before cross-DC failover was re-introduced in 
> release 4.10. Although I realize cross-DC failover is problematic, this 
> message does not seem helpful or at the very least should be INFO instead of 
> WARN.
> App 1 may run in DC1 and App 2 in DC2, but they can share the same contact 
> lists and implement their own failover when necessary, but without needing to 
> update contact points.
> It would be more reasonable to WARN when you've configured 
> *advanced.load-balancing-policy.dc-failover.allow-for-local-consistency-levels*
>  as True. Warning on the contact points specified doesn't seem right.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to