Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8660

Cassandra makes Java 1.7+ SEGFAULT

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Urgent
    • Resolution: Cannot Reproduce
    • None
    • None
    • None

    • Linux Redhat 6.5

    • Critical

    Description

      We upgraded a 3 nodes cluster from Cassandra 2.0.11-5f54285e9e to 2.1-7e6d9eb842.

      With Cassandra 2.1 , within ~10 min. cassandra manages to makes Java 1.7.0_72-b14 segfault. This is also tested and same behavior w/ Java 1.7.0_60-b19 and 1.8.0_25-b17.

      We were able to use same data, downgrade back to 2.0 and things ran for ~3-4 days w/ no hick up. Upgrading back to Cassandra-2.1, Java does a segfault again.

      See attached hs_err file.

      Pierre

      Attachments

        1. hs_err_pid-patch1.log
          746 kB
          Pierre Belanger
        2. 8660
          1 kB
          Benedict Elliott Smith
        3. hs_err_pid12004.log
          646 kB
          Pierre Belanger

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-8661 We don't detect OOM when allocating a Memory object

          • Normal -
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-8552 Large compactions run out of off-heap RAM

          • Urgent - This issue should block release until it is resolved, and trigger immediate release once resolved.
          • Resolved

          Activity

            People

              benedict Benedict Elliott Smith
              belanger Pierre Belanger
              Benedict Elliott Smith
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: