cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Deng (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-12596) cosmetic issue with compaction-stress write
Date Thu, 01 Sep 2016 23:56:20 GMT
Wei Deng created CASSANDRA-12596:

             Summary: cosmetic issue with compaction-stress write
                 Key: CASSANDRA-12596
             Project: Cassandra
          Issue Type: Bug
            Reporter: Wei Deng
            Priority: Minor

I got the following when I was trying to run `compaction-stress write` with a 10GB data set.
Looks like a race condition with the lifecycle transaction log but it only affects the reporting
of the progress temporarily.

Written 50.27GB of 100GB
ERROR 23:49:55,843 Error while getting /mnt/compaction/stresscql/blogposts-606839b5bd683964ad7f57f519eb6dae
folder size. {}
java.nio.file.NoSuchFileException: /mnt/compaction/stresscql/blogposts-606839b5bd683964ad7f57f519eb6dae/mc_txn_write_c6877a90-709e-11e6-91a5-a1533b002bc1.log
        at sun.nio.fs.UnixException.translateToIOException( ~[na:1.8.0_66]
        at sun.nio.fs.UnixException.rethrowAsIOException( ~[na:1.8.0_66]
        at sun.nio.fs.UnixException.rethrowAsIOException( ~[na:1.8.0_66]
        at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(
        at sun.nio.fs.UnixFileSystemProvider.readAttributes(
        at sun.nio.fs.LinuxFileSystemProvider.readAttributes(
        at java.nio.file.Files.readAttributes( ~[na:1.8.0_66]
        at java.nio.file.FileTreeWalker.getAttributes( ~[na:1.8.0_66]
        at java.nio.file.FileTreeWalker.visit( ~[na:1.8.0_66]
        at ~[na:1.8.0_66]
        at java.nio.file.Files.walkFileTree( ~[na:1.8.0_66]
        at java.nio.file.Files.walkFileTree( ~[na:1.8.0_66]
        at ~[main/:na]
        at org.apache.cassandra.db.Directories.getRawDiretoriesSize(
        at org.apache.cassandra.stress.CompactionStress$
        at org.apache.cassandra.stress.CompactionStress.main( [stress/:na]
Written 37.49GB of 100GB

You will see the next "Written xxxGB" number being inaccurate because it interrupted the directory
accounting of the data files, but the subsequent "Written xxxGB" number will get back to normal.

Since it generates a ERROR log entry it's probably still worthwhile to fix.

This message was sent by Atlassian JIRA

View raw message