[
https://issues.apache.org/jira/browse/CASSANDRA-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010408#comment-13010408
]
Joaquin Casares commented on CASSANDRA-2339:
--------------------------------------------
I spun up a 3 node cluster, ran stress.py on a node, changed the replication
factor to 3, ran a repair followed by a cleanup and did not see these errors on
any of the machines.
> Repair results in benign "Unable to delete" error on streaming neighbors
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-2339
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2339
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7.4
> Reporter: Jason Harvey
> Priority: Minor
> Labels: repair
>
> When running a repair on a node, all of the surrounding nodes threw
> multitudes of the following errors immediately after they started streaming
> for the repair:
> {code}
> ERROR 23:24:00,494 Unable to delete
> /var/lib/cassandra/data/system/LocationInfo-f-21-Data.db (it will be removed
> on server restart)
> ERROR 23:24:00,495 Unable to delete
> /var/lib/cassandra/data/reddit/Hide-f-15-Data.db (it will be removed on
> server restart)
> ERROR 23:24:00,496 Unable to delete
> /var/lib/cassandra/data/reddit/CommentSortsCache-f-21-Data.db (it will be
> removed on server restart)
> ERROR 23:24:00,496 Unable to delete
> /var/lib/cassandra/data/reddit/permacache-f-58-Data.db (it will be removed on
> server restart)
> ERROR 23:24:00,496 Unable to delete
> /var/lib/cassandra/data/reddit/VotesByDay-f-5-Data.db (it will be removed on
> server restart)
> ...
> {code}
> Interestingly, I checked every file and verified that it *was* actually
> removed right around the time these errors were thrown. Double-delete going
> on somewhere?
> The error didn't appear to cause any problems with the repair.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
