Cassandra multi-DC:write on LOCAL and read from any DC
We use a multi-data center (DC) cassandra cluster. During write on to the cluster, I want only LOCAL DC to perform writes on its nodes as we are already routing the write requests to the desired DC only based on the source from where write is initiated. So, I want only LOCAL DC to process the write and no other DC to perform the writes on its nodes. But later on by virtue of replication among nodes across DCs, I want the written data to be replicated across DCs. Is this replication across DCs possible when I am restricting the write to only one DC in the first place.If I do not open connections to REMOTE hosts lying in different DCs during my write operation, is data replication possible amongst DCs later on. Why I definitely need replicas of data in all DCs is because during data read from cluster, we want the data to be read from any DC the read request falls on, not necessarily the LOCAL one.
Do anyone has solution to this?
cassandra
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
We use a multi-data center (DC) cassandra cluster. During write on to the cluster, I want only LOCAL DC to perform writes on its nodes as we are already routing the write requests to the desired DC only based on the source from where write is initiated. So, I want only LOCAL DC to process the write and no other DC to perform the writes on its nodes. But later on by virtue of replication among nodes across DCs, I want the written data to be replicated across DCs. Is this replication across DCs possible when I am restricting the write to only one DC in the first place.If I do not open connections to REMOTE hosts lying in different DCs during my write operation, is data replication possible amongst DCs later on. Why I definitely need replicas of data in all DCs is because during data read from cluster, we want the data to be read from any DC the read request falls on, not necessarily the LOCAL one.
Do anyone has solution to this?
cassandra
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
We use a multi-data center (DC) cassandra cluster. During write on to the cluster, I want only LOCAL DC to perform writes on its nodes as we are already routing the write requests to the desired DC only based on the source from where write is initiated. So, I want only LOCAL DC to process the write and no other DC to perform the writes on its nodes. But later on by virtue of replication among nodes across DCs, I want the written data to be replicated across DCs. Is this replication across DCs possible when I am restricting the write to only one DC in the first place.If I do not open connections to REMOTE hosts lying in different DCs during my write operation, is data replication possible amongst DCs later on. Why I definitely need replicas of data in all DCs is because during data read from cluster, we want the data to be read from any DC the read request falls on, not necessarily the LOCAL one.
Do anyone has solution to this?
cassandra
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
We use a multi-data center (DC) cassandra cluster. During write on to the cluster, I want only LOCAL DC to perform writes on its nodes as we are already routing the write requests to the desired DC only based on the source from where write is initiated. So, I want only LOCAL DC to process the write and no other DC to perform the writes on its nodes. But later on by virtue of replication among nodes across DCs, I want the written data to be replicated across DCs. Is this replication across DCs possible when I am restricting the write to only one DC in the first place.If I do not open connections to REMOTE hosts lying in different DCs during my write operation, is data replication possible amongst DCs later on. Why I definitely need replicas of data in all DCs is because during data read from cluster, we want the data to be read from any DC the read request falls on, not necessarily the LOCAL one.
Do anyone has solution to this?
cassandra
cassandra
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
asked Jul 20 '18 at 11:34
Parul ChourasiaParul Chourasia
1
1
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The data is always written to all DCs, the LOCAL consistency levels are just saying that confirmation should come from the local nodes, not from other DCs...
From the DSE Architecture guide (also look to image there):
In multiple datacenter deployments, DataStax Enterprise (DSE) optimizes write performance by choosing one coordinator node. The coordinator node contacted by the client application forwards the write request to one replica in each of the other datacenters, with a special tag to forward the write to the other local replicas.
If the write write consistency levels is
LOCAL_ONEorLOCAL_QUORUM, only the nodes in the same datacenter as the coordinator node must respond to the client request for the request to succeed. Use eitherLOCAL_ONEorLOCAL_QUORUMto reduce geographical latency and lessen the impact on response times of client write requests.
P.S. I recommend to read this guide to understand how Cassandra/DSE works - it makes things much simpler if you have this information.
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f212765%2fcassandra-multi-dcwrite-on-local-and-read-from-any-dc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The data is always written to all DCs, the LOCAL consistency levels are just saying that confirmation should come from the local nodes, not from other DCs...
From the DSE Architecture guide (also look to image there):
In multiple datacenter deployments, DataStax Enterprise (DSE) optimizes write performance by choosing one coordinator node. The coordinator node contacted by the client application forwards the write request to one replica in each of the other datacenters, with a special tag to forward the write to the other local replicas.
If the write write consistency levels is
LOCAL_ONEorLOCAL_QUORUM, only the nodes in the same datacenter as the coordinator node must respond to the client request for the request to succeed. Use eitherLOCAL_ONEorLOCAL_QUORUMto reduce geographical latency and lessen the impact on response times of client write requests.
P.S. I recommend to read this guide to understand how Cassandra/DSE works - it makes things much simpler if you have this information.
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
add a comment |
The data is always written to all DCs, the LOCAL consistency levels are just saying that confirmation should come from the local nodes, not from other DCs...
From the DSE Architecture guide (also look to image there):
In multiple datacenter deployments, DataStax Enterprise (DSE) optimizes write performance by choosing one coordinator node. The coordinator node contacted by the client application forwards the write request to one replica in each of the other datacenters, with a special tag to forward the write to the other local replicas.
If the write write consistency levels is
LOCAL_ONEorLOCAL_QUORUM, only the nodes in the same datacenter as the coordinator node must respond to the client request for the request to succeed. Use eitherLOCAL_ONEorLOCAL_QUORUMto reduce geographical latency and lessen the impact on response times of client write requests.
P.S. I recommend to read this guide to understand how Cassandra/DSE works - it makes things much simpler if you have this information.
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
add a comment |
The data is always written to all DCs, the LOCAL consistency levels are just saying that confirmation should come from the local nodes, not from other DCs...
From the DSE Architecture guide (also look to image there):
In multiple datacenter deployments, DataStax Enterprise (DSE) optimizes write performance by choosing one coordinator node. The coordinator node contacted by the client application forwards the write request to one replica in each of the other datacenters, with a special tag to forward the write to the other local replicas.
If the write write consistency levels is
LOCAL_ONEorLOCAL_QUORUM, only the nodes in the same datacenter as the coordinator node must respond to the client request for the request to succeed. Use eitherLOCAL_ONEorLOCAL_QUORUMto reduce geographical latency and lessen the impact on response times of client write requests.
P.S. I recommend to read this guide to understand how Cassandra/DSE works - it makes things much simpler if you have this information.
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
The data is always written to all DCs, the LOCAL consistency levels are just saying that confirmation should come from the local nodes, not from other DCs...
From the DSE Architecture guide (also look to image there):
In multiple datacenter deployments, DataStax Enterprise (DSE) optimizes write performance by choosing one coordinator node. The coordinator node contacted by the client application forwards the write request to one replica in each of the other datacenters, with a special tag to forward the write to the other local replicas.
If the write write consistency levels is
LOCAL_ONEorLOCAL_QUORUM, only the nodes in the same datacenter as the coordinator node must respond to the client request for the request to succeed. Use eitherLOCAL_ONEorLOCAL_QUORUMto reduce geographical latency and lessen the impact on response times of client write requests.
P.S. I recommend to read this guide to understand how Cassandra/DSE works - it makes things much simpler if you have this information.
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
answered Jul 20 '18 at 12:27
Alex OttAlex Ott
41815
41815
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f212765%2fcassandra-multi-dcwrite-on-local-and-read-from-any-dc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
