[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707971#comment-17707971 ] Maxim Muzafarov commented on CASSANDRA-18131: - [~mck] Thank you for your review and time! > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable, Test/burn >Reporter: Michael Semb Wever >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.9, 5.0, 4.1.2 > > Time Spent: 50m > Remaining Estimate: 0h > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707804#comment-17707804 ] Michael Semb Wever commented on CASSANDRA-18131: bq. I think we can reduce the value to perThreadTrees = 10, my local runs show exactly 5 min execution time. I'll do that on commit. Thanks. > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > Time Spent: 50m > Remaining Estimate: 0h > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[
https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707732#comment-17707732
]
Maxim Muzafarov commented on CASSANDRA-18131:
-
[~mck]
I have reused the value from the
[{{cassandra-3.11}}|https://github.com/apache/cassandra/blob/cassandra-3.11/test/burn/org/apache/cassandra/utils/LongBTreeTest.java#L61]
branch, where the test completed successfully in ~20-40 min, depending on the
CI agent used.
Here is an example of the lastest run for 3.11:
https://ci-cassandra.apache.org/view/Cassandra%203.11/job/Cassandra-3.11-test-burn/496/
I tested the patch with perThreadTrees = 100 (the same as for 3.11) and it
finished within 38 min which looks pretty much the same.
https://ci-cassandra.apache.org/job/Cassandra-devbranch-test-burn/1810/
I think we can reduce the value to perThreadTrees = 10, my local runs show
exactly 5 min execution time.
> LongBTreeTest times out after btree improvements from CASSANDRA-15510
> -
>
> Key: CASSANDRA-18131
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18131
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Memtable
>Reporter: Michael Semb Wever
>Assignee: Maxim Muzafarov
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Happening in both ci-cassandra.a.o and circleci.
> LongBTreeTest is timing out on 4.0, 4.1, trunk branches.
> Started back in mid April
> (https://github.com/apache/cassandra/commit/018c8e0d5e and
> https://github.com/apache/cassandra/commit/596daeb7f08).
> Nightlies shows when the failures started, evident by the
> 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the
> following…
> -
> https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/
> -
> https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707718#comment-17707718 ] Michael Semb Wever commented on CASSANDRA-18131: [~mmuzaf], before I commit, i'm thinking about this… bq. ~ 45 min for the perThreadTrees = 500 The longest split we have currently in Cassandra-trunk-test-burn is ~30 minutes. The burn tests are intended here only to be tested that they run, not to actually perform the burn (there's no point on non-dedicated servers and homogeneous agents), so short runs are fine (so long as it's easy and obvious that developers need parameterise it properly). Can you reduce it sensibly to ~5 minutes? (when running on the ci-cassandra.a.o agents) > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > Time Spent: 50m > Remaining Estimate: 0h > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707673#comment-17707673 ] Maxim Muzafarov commented on CASSANDRA-18131: - [~benedict], [~blambov], [~blerer] Hello everyone, just a friendly reminder, can you take a look at the patch? Hope you can find some time. The fix is simple, the whole suite #7 still hangs: https://ci-cassandra.apache.org/view/Cassandra%205.0/job/Cassandra-trunk-test-burn/1586/ > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698583#comment-17698583 ] Brandon Williams commented on CASSANDRA-18131: -- /cc [~blerer] > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17695025#comment-17695025 ] Maxim Muzafarov commented on CASSANDRA-18131: - The build results here (~ 45 min): https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2306/flowGraphTable/ > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[
https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694782#comment-17694782
]
Maxim Muzafarov commented on CASSANDRA-18131:
-
[~mck], [~benedict],
The reason the test suite hangs is that the number of running tests configured
by the {{perThreadTrees}} configuration parameter is too large to complete
within a reasonable time (the test suite timeout is 90 minutes). There is no
such problem for the {{cassandra-3.11}} branch, as {{perThreadTrees}} is set to
100, so the test completes within 15 minutes. See
[LongBTreeTest.java#L61|https://github.com/apache/cassandra/blob/cassandra-3.11/test/burn/org/apache/cassandra/utils/LongBTreeTest.java#L61].
The total number of "runs" has been changed several times to fit the timeout,
so the issues seem to be common:
||JIRA||Change||
|CASSANDRA-15487|iterations from 1 to 1|
|CASSANDRA-9989|perThreadTrees from 1 to 100|
|CASSANDRA-9932|from 1 to perThreadTrees / 10 (in total 1000)|
It seems to me that the perThreadTrees was unintentionally changed in
CASSANDRA-15510, so we should revert to the old value. I've also fixed a few
places where the perThreadTrees is not used for the right purpose (like for
iterations in the testRandomRangeAndBatches), so the whole {{LongBTreeTest}} is
scaled incorrectly.
Please, take a look.
I have got successful results here, but still waiting for the final run:
https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2301/flowGraphTable/
> LongBTreeTest times out after btree improvements from CASSANDRA-15510
> -
>
> Key: CASSANDRA-18131
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18131
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Memtable
>Reporter: Michael Semb Wever
>Assignee: Maxim Muzafarov
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Happening in both ci-cassandra.a.o and circleci.
> LongBTreeTest is timing out on 4.0, 4.1, trunk branches.
> Started back in mid April
> (https://github.com/apache/cassandra/commit/018c8e0d5e and
> https://github.com/apache/cassandra/commit/596daeb7f08).
> Nightlies shows when the failures started, evident by the
> 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the
> following…
> -
> https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/
> -
> https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693183#comment-17693183 ] Maxim Muzafarov commented on CASSANDRA-18131: - Hello everyone, I'll try to take a look at the cause. Please let me know if your vision has changed or if the issue is no longer relevant. > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18131) LongBTreeTest times out after btree improvements from CASSANDRA-15510
[ https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654170#comment-17654170 ] Michael Semb Wever commented on CASSANDRA-18131: [~benedict], [~blambov], [~blerer] > LongBTreeTest times out after btree improvements from CASSANDRA-15510 > - > > Key: CASSANDRA-18131 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18131 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > Happening in both ci-cassandra.a.o and circleci. > LongBTreeTest is timing out on 4.0, 4.1, trunk branches. > Started back in mid April > (https://github.com/apache/cassandra/commit/018c8e0d5e and > https://github.com/apache/cassandra/commit/596daeb7f08). > Nightlies shows when the failures started, evident by the > 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the > following… > - > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/ > - > https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
