Frequent Compaction of OpsCenter.rollup_state on all the nodes consuming CPU cycles
I am using Datastax Cassandra 4.8.16. With cluster of 8 DC and 5 nodes on each DC on VM's. For last couple of weeks we observed below performance issue
1) Increase drop count on VM's.
2) LOCAL_QUORUM for some write operation not achieved.
3) Frequent Compaction of OpsCenter.rollup_state and system.hints are visible in Opscenter.
Appreciate any help finding the root cause for this.
cassandra datastax datastax-enterprise cassandra-3.0
add a comment |
I am using Datastax Cassandra 4.8.16. With cluster of 8 DC and 5 nodes on each DC on VM's. For last couple of weeks we observed below performance issue
1) Increase drop count on VM's.
2) LOCAL_QUORUM for some write operation not achieved.
3) Frequent Compaction of OpsCenter.rollup_state and system.hints are visible in Opscenter.
Appreciate any help finding the root cause for this.
cassandra datastax datastax-enterprise cassandra-3.0
add a comment |
I am using Datastax Cassandra 4.8.16. With cluster of 8 DC and 5 nodes on each DC on VM's. For last couple of weeks we observed below performance issue
1) Increase drop count on VM's.
2) LOCAL_QUORUM for some write operation not achieved.
3) Frequent Compaction of OpsCenter.rollup_state and system.hints are visible in Opscenter.
Appreciate any help finding the root cause for this.
cassandra datastax datastax-enterprise cassandra-3.0
I am using Datastax Cassandra 4.8.16. With cluster of 8 DC and 5 nodes on each DC on VM's. For last couple of weeks we observed below performance issue
1) Increase drop count on VM's.
2) LOCAL_QUORUM for some write operation not achieved.
3) Frequent Compaction of OpsCenter.rollup_state and system.hints are visible in Opscenter.
Appreciate any help finding the root cause for this.
cassandra datastax datastax-enterprise cassandra-3.0
cassandra datastax datastax-enterprise cassandra-3.0
asked Jan 3 at 6:59
Mehul GuptaMehul Gupta
312417
312417
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Presence of dropped mutations means that cluster is heavily overloaded. It could be increase of the main load, so it + load from OpsCenter, overloaded system - you need to look into statistics about number of requests, latencies, etc. per nodes and per tables, to see where increase happened. Please also check the I/O statistics on machines (for example, with iostat
) - sizes of the queues, read/write latencies, etc.
Also it's recommended to use a dedicated OpsCenter cluster to store metrics - it could be smaller size, and doesn't require an additional license for DSE. How it said in the OpsCenter's documentation:
Important: In production environments, DataStax strongly recommends storing data in a separate DataStax Enterprise cluster.
Regarding VMs - usually it's not really recommended setup, but heavily depends on what kind of underlying hardware - number of CPUs, RAM, disk system.
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f54017679%2ffrequent-compaction-of-opscenter-rollup-state-on-all-the-nodes-consuming-cpu-cyc%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
Presence of dropped mutations means that cluster is heavily overloaded. It could be increase of the main load, so it + load from OpsCenter, overloaded system - you need to look into statistics about number of requests, latencies, etc. per nodes and per tables, to see where increase happened. Please also check the I/O statistics on machines (for example, with iostat
) - sizes of the queues, read/write latencies, etc.
Also it's recommended to use a dedicated OpsCenter cluster to store metrics - it could be smaller size, and doesn't require an additional license for DSE. How it said in the OpsCenter's documentation:
Important: In production environments, DataStax strongly recommends storing data in a separate DataStax Enterprise cluster.
Regarding VMs - usually it's not really recommended setup, but heavily depends on what kind of underlying hardware - number of CPUs, RAM, disk system.
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
add a comment |
Presence of dropped mutations means that cluster is heavily overloaded. It could be increase of the main load, so it + load from OpsCenter, overloaded system - you need to look into statistics about number of requests, latencies, etc. per nodes and per tables, to see where increase happened. Please also check the I/O statistics on machines (for example, with iostat
) - sizes of the queues, read/write latencies, etc.
Also it's recommended to use a dedicated OpsCenter cluster to store metrics - it could be smaller size, and doesn't require an additional license for DSE. How it said in the OpsCenter's documentation:
Important: In production environments, DataStax strongly recommends storing data in a separate DataStax Enterprise cluster.
Regarding VMs - usually it's not really recommended setup, but heavily depends on what kind of underlying hardware - number of CPUs, RAM, disk system.
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
add a comment |
Presence of dropped mutations means that cluster is heavily overloaded. It could be increase of the main load, so it + load from OpsCenter, overloaded system - you need to look into statistics about number of requests, latencies, etc. per nodes and per tables, to see where increase happened. Please also check the I/O statistics on machines (for example, with iostat
) - sizes of the queues, read/write latencies, etc.
Also it's recommended to use a dedicated OpsCenter cluster to store metrics - it could be smaller size, and doesn't require an additional license for DSE. How it said in the OpsCenter's documentation:
Important: In production environments, DataStax strongly recommends storing data in a separate DataStax Enterprise cluster.
Regarding VMs - usually it's not really recommended setup, but heavily depends on what kind of underlying hardware - number of CPUs, RAM, disk system.
Presence of dropped mutations means that cluster is heavily overloaded. It could be increase of the main load, so it + load from OpsCenter, overloaded system - you need to look into statistics about number of requests, latencies, etc. per nodes and per tables, to see where increase happened. Please also check the I/O statistics on machines (for example, with iostat
) - sizes of the queues, read/write latencies, etc.
Also it's recommended to use a dedicated OpsCenter cluster to store metrics - it could be smaller size, and doesn't require an additional license for DSE. How it said in the OpsCenter's documentation:
Important: In production environments, DataStax strongly recommends storing data in a separate DataStax Enterprise cluster.
Regarding VMs - usually it's not really recommended setup, but heavily depends on what kind of underlying hardware - number of CPUs, RAM, disk system.
answered Jan 3 at 9:06
Alex OttAlex Ott
28.5k35274
28.5k35274
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
add a comment |
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
How can I stop frequent compaction of Opscenter.rollup_state? I see 50% of cluster node performing compaction on this table.
– Mehul Gupta
Jan 4 at 5:28
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
It looks like that you have too much data in it. Consider decreasing the time to leave for 1 minute tables, and maybe excluding some keyspaces from data collection - both topics are described in documentation: docs.datastax.com/en/opscenter/6.1/opsc/configure/…
– Alex Ott
Jan 4 at 7:33
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f54017679%2ffrequent-compaction-of-opscenter-rollup-state-on-all-the-nodes-consuming-cpu-cyc%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