Skip to content

Commit

Permalink
Fix Incorrect Example in ecc.yml for consistencySerial - Issue #645 (#…
Browse files Browse the repository at this point in the history
  • Loading branch information
VictorCavichioli authored Mar 12, 2024
1 parent 5a2ab5c commit 0e1a373
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions application/src/main/resources/ecc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -275,9 +275,9 @@ lock_factory:
## Allow to override consistency level for LWT (lightweight transactions). Possible values are:
## "DEFAULT" - Use consistency level based on remoteRouting.
## "SERIAL" - Use SERIAL consistency for LWT regardless of remoteRouting.
## "LOCAL_SERIAL" - Use LOCAL_SERIAL consistency for LWT regardless of remoteRouting.
## "LOCAL" - Use LOCAL_SERIAL consistency for LWT regardless of remoteRouting.
##
## if you use remoteRouting: false and LOCAL_SERIAL then all locks will be taken locally
## if you use remoteRouting: false and LOCAL then all locks will be taken locally
## in DC. I.e There's a risk that multiple nodes in different datacenters will be able to lock the
## same nodes causing multiple repairs on the same range/node at the same time.
##
Expand Down
4 changes: 2 additions & 2 deletions docs/autogenerated/EccYamlFile.md
Original file line number Diff line number Diff line change
Expand Up @@ -261,9 +261,9 @@
# Allow to override consistency level for LWT (lightweight transactions). Possible values are:
# "DEFAULT" - Use consistency level based on remoteRouting.
# "SERIAL" - Use SERIAL consistency for LWT regardless of remoteRouting.
# "LOCAL_SERIAL" - Use LOCAL_SERIAL consistency for LWT regardless of remoteRouting.
# "LOCAL" - Use LOCAL_SERIAL consistency for LWT regardless of remoteRouting.
#
# if you use remoteRouting: false and LOCAL_SERIAL then all locks will be taken locally
# if you use remoteRouting: false and LOCAL then all locks will be taken locally
# in DC. I.e There's a risk that multiple nodes in different datacenters will be able to lock the
# same nodes causing multiple repairs on the same range/node at the same time.
#
Expand Down

0 comments on commit 0e1a373

Please sign in to comment.