[
https://issues.apache.org/jira/browse/CASSANDRA-10049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693285#comment-14693285
]
Branimir Lambov commented on CASSANDRA-10049:
---------------------------------------------
The link above appears to be broken. A more permanent record of the failure is
[here|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/38/testReport/consistency_test/TestAccuracy/test_network_topology_strategy_users/],
with an error log of
{code}
AssertionError: Unexpected error in node5 node log: ['ERROR
[COMMIT-LOG-ALLOCATOR] 2015-08-11 21:04:28,915 JVMStabilityInspector.java:77 -
Exiting due to error while processing commit log during initialization.
java.lang.NullPointerException: null
at
org.apache.cassandra.db.commitlog.MemoryMappedSegment.createBuffer(MemoryMappedSegment.java:70)
~[main/:na]
at
org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:153)
~[main/:na]
...
at
org.apache.cassandra.db.commitlog.CommitLogSegmentManager$1.runMayThrow(CommitLogSegmentManager.java:123)
~[main/:na]
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
[main/:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]']
{code}
Pushed a patch [here|https://github.com/blambov/cassandra/tree/10049] that
addresses this particular race and moves all thread starting outside of
constructors in the commitlog package to avoid this type of problem.
> Commitlog initialization failure
> --------------------------------
>
> Key: CASSANDRA-10049
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10049
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: Branimir Lambov
> Fix For: 3.0.0 rc1
>
>
> I've encountered this error locally during some dtests.
> It looks like a race condition in the commit log code.
> http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/lastCompletedBuild/testReport/consistency_test/TestAccuracy/test_network_topology_strategy_users_2/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
