[CASSANDRA-8176] Intermittent NPE from RecoveryManagerTest RecoverPIT unit test

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.2
• Component/s: Legacy/Testing
• Labels: qa-resolved
• Severity: Normal
• Assignee: Sam Tunnicliffe
• Reporter: Michael Shuler

Authors

Sam Tunnicliffe

Reviewers

Jonathan Ellis

• Created: 23/Oct/14 16:59
• Updated: 16/Apr/19 09:31
• Resolved: 29/Oct/14 15:24

Description

    [junit] Testsuite: org.apache.cassandra.db.RecoveryManagerTest
    [junit] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.654 sec
    [junit] 
    [junit] ------------- Standard Output ---------------
    [junit] WARN  16:40:38 No host ID found, created 2cbd54a8-79a5-40e0-a8e6-c8bf2c575877 (Note: This should happen exactly once per node).
    [junit] WARN  16:40:38 No host ID found, created 2cbd54a8-79a5-40e0-a8e6-c8bf2c575877 (Note: This should happen exactly once per node).
    [junit] WARN  16:40:38 Encountered bad header at position 16 of commit log /home/mshuler/git/cassandra/build/test/cassandra/commitlog:0/CommitLog-4-1414082433807.log, with invalid CRC. The end of segment marker should be zero.
    [junit] WARN  16:40:38 Encountered bad header at position 16 of commit log /home/mshuler/git/cassandra/build/test/cassandra/commitlog:0/CommitLog-4-1414082433807.log, with invalid CRC. The end of segment marker should be zero.
    [junit] ------------- ---------------- ---------------
    [junit] Testcase: testRecoverPIT(org.apache.cassandra.db.RecoveryManagerTest):      Caused an ERROR
    [junit] null
    [junit] java.lang.NullPointerException
    [junit]     at org.apache.cassandra.db.RecoveryManagerTest.testRecoverPIT(RecoveryManagerTest.java:129)
    [junit] 
    [junit] 
    [junit] Test org.apache.cassandra.db.RecoveryManagerTest FAILED

Test fails roughly 20-25% of CI runs. Several 10x and 25x bisections for 2.1 git bisect start cassandra-2.1 f03e505 resulted in

first bad commit: [1394b128c65ef1ad59f765e9c9c5058cac04ca69]

which is CASSANDRA-6904.

That patch went to 2.0 and I still need to dig there to see if we're getting the same error, but I've attached the unit test failure system.log from 2.1.