What does this error mean?

This error means a commit log segment that should have been archived did not archive properly. Instead of attempting to archive segment, Cassandra is choosing to ignore the segment assuming that it may have already been archived and the resulting segment is left behind due to other possible errors.

Why does this error occur?

This error occurs when the attempted archival of a commit log segment throws an IOException.

How do you fix this error?

Since the exception thrown is an IOException, you should check the typical causes of IOExceptions for this scenario:

• Is the file still available for reading/writing?
• Do you have proper permissions in place to access the file/directories?
• Is there enough disk space in the archival directory?

The cause information that follows the specific error statement will provide further details to help you narrow down why the IOException occurred. If you need further assistance determining the cause, DataStax Support can assist.