Default read and write consistency levels cause issues

Description

Team,

We uncovered an issue in our system recently where multiple reads were resulting in inconsistent outputs. Until now, we had not customized the read/write consistency parameters.

This documentation helped us understand that the inconsistency was due to the fact that we write using LOCAL_QUORUM as consistency, but read using LOCAL_ONE.

https://datastax-oss.atlassian.net/browse/NODEJS-160?filter=-4&jql=text%20~%20%22read%20consistency%22%20order%20by%20created%20DESC

We have fixed our issue, but do you think it makes sense to revisit the default consistency levels, so that read/writes in the default setup work well together?

For instance, I would expect LOCAL_QUORUM to be the read consistency level, if writes use the same.

Environment

None

Pull Requests

None

Status

Assignee

Jacek Lewandowski

Reporter

Santosh Kewat

Labels

None

Reviewer

None

Reviewer 2

None

Tester

None

Pull Request

None

Components

Affects versions

Priority

Major
Configure