You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jim Witschey (JIRA)" <ji...@apache.org> on 2015/05/08 00:19:00 UTC
[jira] [Commented] (CASSANDRA-8593) Test for leap second related
bugs
[ https://issues.apache.org/jira/browse/CASSANDRA-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533480#comment-14533480 ]
Jim Witschey commented on CASSANDRA-8593:
-----------------------------------------
[Here|http://www.datastax.com/dev/blog/preparing-for-the-leap-second] is the blog post that came out of this work.
Are there any objections to closing this?
> Test for leap second related bugs
> ---------------------------------
>
> Key: CASSANDRA-8593
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8593
> Project: Cassandra
> Issue Type: Test
> Reporter: Ryan McGuire
> Assignee: Jim Witschey
>
> http://www.datastax.com/dev/blog/linux-cassandra-and-saturdays-leap-second-problem
> Another leap second is being added in June, we need to find an old system/platform that does still have this issue, create a test that exercises it. Then we can use the test to create a list of any still affected platforms. Ideally, we can include a list of the affected platforms/configs inside C* and it will issue a warning in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)