cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9635) Silent startup failure with filesystem that does not support mmap
Date Mon, 29 Jun 2015 10:48:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605418#comment-14605418
] 

Branimir Lambov commented on CASSANDRA-9635:
--------------------------------------------

Is the commit log failure policy not working correctly, i.e. does the node fail to reach the
state it is supposed to after this happens? I believe a deadlock waiting for allocation is
to be expected as a result of the 'stop' policy.

Perhaps a good simple solution may be for the policy to start as 'die' until we have done
one allocation.

> Silent startup failure with filesystem that does not support mmap
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-9635
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9635
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Kevin McLaughlin
>            Assignee: Stefania
>             Fix For: 2.0.x
>
>         Attachments: c_tdump.txt
>
>
> C* version 2.0.9.
> When running C* in virtualbox on OS X via boot2docker with the data directory on a shared
volume from the host system (vboxfs), C* fails to start without printing any errors.
> I do not know if C* is supposed to support filesystems that do not support mmap (does
not appear so), however, I think the failure exposes a static initialization deadlock (http://ternarysearch.blogspot.ru/2013/07/static-initialization-deadlock.html).
> I believe the virtualbox "bug" is https://www.virtualbox.org/ticket/819.
> Stacktrace of the deadlock is attached.  When placing a t.printStackTrace() between lines
115 and 116 in https://github.com/apache/cassandra/blob/cassandra-2.0.9/src/java/org/apache/cassandra/db/commitlog/CommitLogAllocator.java,
the stack trace at startup is:
> {quote}
> DEBUG 21:16:54,716 Creating new commit log segment /var/lib/cassandra/commitlog/CommitLog-3-1435007814714.log
> FSWriteError in /var/lib/cassandra/commitlog/CommitLog-3-1435007814714.log
>     at org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:143)
>     at org.apache.cassandra.db.commitlog.CommitLogSegment.freshSegment(CommitLogSegment.java:90)
>     at org.apache.cassandra.db.commitlog.CommitLogAllocator.createFreshSegment(CommitLogAllocator.java:263)
>     at org.apache.cassandra.db.commitlog.CommitLogAllocator.access$500(CommitLogAllocator.java:50)
>     at org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(CommitLogAllocator.java:109)
>     at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
>     at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.IOException: Invalid argument
>     at sun.nio.ch.FileChannelImpl.map0(Native Method)
>     at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:893)
>     at org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:133)
>     ... 6 more
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message