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

Settings Virtual Table should display the values assigned to a property in the DatabaseDescriptor on startup and not null (as per the yaml)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • 4.0.x, 4.1.x, 4.x
    • Local/Config
    • None
    • Correctness
    • Low
    • Low Hanging Fruit
    • User Report
    • All
    • None

    Description

      There are a few properties that after startup do not show their assigned values as per the DatabaseDescriptor assignment but the cassandra.yaml value.

      They will not be also updated in the virtual table down the road in case they are updated through JMX, nodetool etc.

      EDIT: This ticket should serve to check the properties that are not type Duration, Data Storage and Data Rate; also that are not new to 4.1. I will post a list of who are those later today for convenience. We target all those in Config class (some advanced properties are not broadly advertised in cassandra.yaml intentionally).

      There is Settings Virtual Table  which is supposed to show the values for our config parameters at any time. Especially useful if any property was changed after startup through JMX/nodetool and it doesn't match anymore the value in cassandra.yaml. For this to be possible, we need to ensure that the parameters are always updated in the Config class. It was observed that some are not always updating in Config class, but after startup delegating to other internal variables. This is a bug and this task should review and address any new findings. 

      Classes of interest - SettingsTable where you can see how config parameters are listed; Config class where our configuration parameters are defined.

      We need patches 4.0 and above. I suggest you start looking into 4.0 branch and then merge into higher branches. As you won't be checking the data storage, data rate and duration type parameters, there shouldn't be many conflicts on merge. 

      We have a lot of parameters and I suggest you split the list into batches to check and produce patches where/if needed to make the work more incremental and easier to work on and review it.

       

      Attachments

        Issue Links

          Activity

            People

              atri Atri Sharma
              e.dimitrova Ekaterina Dimitrova
              Atri Sharma
              Caleb Rackliffe, Ekaterina Dimitrova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: