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

By default, Cassandra should refuse to start if JNA can't be initialized properly

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 2.1 beta1
    • None

    Description

      Failure to have JNA working properly is such a common undetected problem that it would be far preferable to have Cassandra refuse to startup unless JNA is initialized. In theory, this should be much less of a problem with Cassandra 2.1 due to CASSANDRA-5872, but even there, it might fail due to native lib problems, or might otherwise be misconfigured. A yaml override, such as boot_without_jna would allow the deliberate overriding of this policy.

      Attachments

        1. trunk-6575-v4.patch
          8 kB
          Joshua McKenzie
        2. trunk-6575-v3.patch
          8 kB
          Clément Lardeur
        3. trunk-6575-v2.patch
          2 kB
          Clément Lardeur
        4. trunk-6575.patch
          2 kB
          Clément Lardeur
        5. 6575.txt
          2 kB
          Benedict Elliott Smith

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-7201 Regression: ColumnFamilyStoreTest, NativeCellTest, SSTableMetadataTest unit tests on 2.1

          • Normal -
          • Resolved
          relates to

          Task - A task that needs to be done. CASSANDRA-5872 Bundle JNA

          • Low -
          • Resolved

          Activity

            People

              clardeur Clément Lardeur
              tupshin Tupshin Harper
              Clément Lardeur
              Joshua McKenzie
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: