[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Complexity: Normal (was: Low Hanging Fruit) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0, 3.11.8, 4.0-beta2, 4.0-beta4, 3.11.10 > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Fix Version/s: 3.11.10 4.0-beta4 > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0, 3.11.8, 4.0-beta2, 4.0-beta4, 3.11.10 > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Fix Version/s: 4.0 > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0, 3.11.8, 4.0-beta2 > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Fix Version/s: (was: 4.0-beta) (was: 3.11.x) 4.0-beta2 3.11.8 > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.8, 4.0-beta2 > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Reviewers: ZhaoYang (was: Michael Semb Wever, ZhaoYang) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.8, 4.0-beta2 > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Since Version: 3.4 Source Control Link: https://github.com/apache/cassandra/commit/116e9c1678a1e96748236962e71319f337e07f8d Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [116e9c1678a1e96748236962e71319f337e07f8d|https://github.com/apache/cassandra/commit/116e9c1678a1e96748236962e71319f337e07f8d]. > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Reviewers: ZhaoYang, Michael Semb Wever (was: Michael Semb Wever, ZhaoYang) ZhaoYang, Michael Semb Wever (was: ZhaoYang) Status: Review In Progress (was: Patch Available) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Status: Ready to Commit (was: Review In Progress) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Test and Documentation Plan: CI running. Unit test added. (was: CI running) Status: Patch Available (was: In Progress) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Test and Documentation Plan: CI run. Unit test added. (was: CI running. Unit test added.) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Status: In Progress (was: Patch Available) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-16071: - Test and Documentation Plan: CI running Status: Patch Available (was: In Progress) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-16071: - Reviewers: ZhaoYang > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Description: In CASSANDRA-12662, [~scottcarey] [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly interpreted in bytes rather than megabytes as its name implies. {quote} 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is actually memory in BYTES. If you take it at face value, and set it to say, '512' thinking that means 512MB, you will produce a million temp files rather quickly in a large compaction, which will exhaust even large values of max_map_count rapidly, and get the OOM: Map Error issue above and possibly have a very difficult situation to get a cluster back into a place where nodes aren't crashing while initilaizing or soon after. This issue is minor if you know about it in advance and set the value IN BYTES. {quote} was: In CASSANDRA-12662 [~scottcarey] [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly interpreted in bytes rather than megabytes as its name implies. {quote} 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is actually memory in BYTES. If you take it at face value, and set it to say, '512' thinking that means 512MB, you will produce a million temp files rather quickly in a large compaction, which will exhaust even large values of max_map_count rapidly, and get the OOM: Map Error issue above and possibly have a very difficult situation to get a cluster back into a place where nodes aren't crashing while initilaizing or soon after. This issue is minor if you know about it in advance and set the value IN BYTES. {quote} > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662, [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes
[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16071: --- Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Implementation(12988) Complexity: Low Hanging Fruit Discovered By: User Report Fix Version/s: 4.0-beta 3.11.x Severity: Normal Status: Open (was: Triage Needed) > max_compaction_flush_memory_in_mb is interpreted as bytes > - > > Key: CASSANDRA-16071 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16071 > Project: Cassandra > Issue Type: Bug > Components: Feature/SASI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > > In CASSANDRA-12662 [~scottcarey] > [reported|https://issues.apache.org/jira/browse/CASSANDRA-12662?focusedCommentId=17070055=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17070055] > that the {{max_compaction_flush_memory_in_mb}} setting gets incorrectly > interpreted in bytes rather than megabytes as its name implies. > {quote} > 1. the setting 'max_compaction_flush_memory_in_mb' is a misnomer, it is > actually memory in BYTES. If you take it at face value, and set it to say, > '512' thinking that means 512MB, you will produce a million temp files > rather quickly in a large compaction, which will exhaust even large values of > max_map_count rapidly, and get the OOM: Map Error issue above and possibly > have a very difficult situation to get a cluster back into a place where > nodes aren't crashing while initilaizing or soon after. This issue is minor > if you know about it in advance and set the value IN BYTES. > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org