cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9635) Silent startup failure with filesystem that does not support mmap
Date Fri, 26 Jun 2015 10:05:04 GMT


Stefania commented on CASSANDRA-9635:

Could you attach your cassandra.yaml and the log file? I see what the problem is from code
inspection but I don't have easy access to a virtual box so I am hoping to reproduce this
by 'mocking' the exact exception in your log file.

I think the solution to avoid the deadlock might be a new startup check but I need to consult
with more experienced developers first.

> Silent startup failure with filesystem that does not support mmap
> -----------------------------------------------------------------
>                 Key: CASSANDRA-9635
>                 URL:
>             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 (
> I believe the virtualbox "bug" is
> Stacktrace of the deadlock is attached.  When placing a t.printStackTrace() between lines
115 and 116 in,
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>(
>     at org.apache.cassandra.db.commitlog.CommitLogSegment.freshSegment(
>     at org.apache.cassandra.db.commitlog.CommitLogAllocator.createFreshSegment(
>     at org.apache.cassandra.db.commitlog.CommitLogAllocator.access$500(
>     at org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(
>     at
>     at
> Caused by: Invalid argument
>     at Method)
>     at
>     at org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(
>     ... 6 more
> {quote}

This message was sent by Atlassian JIRA

View raw message