You're probably running into
https://issues.apache.org/jira/browse/CASSANDRA-6784. This will be fixed in
2.0.6.
On Mon, Mar 3, 2014 at 3:43 PM, Phil Luckhurst <
phil.luckhu...@powerassure.com> wrote:
> Running 'nodetool compactionHistory' seems to be showing strange timestamp
> values for the 'compacted_at' column. e.g.
> id keyspace_name
> columnfamily_name compacted_at bytes_in
> bytes_out rows_merged
> cb035320-9f11-11e3-82e3-e37a59d03017 system
> sstable_activity
> 1212036306964769 74352 19197 {1:19, 4:427}
>
> And running a CQL query on the system.compaction_history table shows dates
> well in the future.
>
> id | bytes_in |
> bytes_out | columnfamily_name | compacted_at |
> keyspace_name | rows_merged
>
> --------------------------------------+----------+-----------+-------------------------+---------------------------+--------------------+--------------------------
> bda494f0-9db8-11e3-bb85-ed7074988754 | 647 | 320 |
> compactions_in_progress | 17391-03-07 12:26:35+0000 | system |
> {1: 3, 2: 1}
> dc87cd00-a269-11e3-a1a8-ed7074988754 | 410 | 159 |
> compactions_in_progress | 33738-09-07 17:03:21+0100 | system |
> {1: 2, 2: 1}
>
> Is this a known issue or something wrong on our system?
>
> Thanks
> Phil
>
>
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Invalid-compacted-at-timestamp-entries-in-Cassandra-2-0-5-tp7593190.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
>
