• Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:


      Chukwa has many configuration options, and it's easy to mis-set them. I'd like to contribute a module for doing stronger static checks of configuration at startup.

      In particular, this will flag and log cases where:
      An option is set in the Chukwa config files that is never read by Chukwa.
      A non-numeric value is used for a numeric parameter, non-boolean value for boolean parameter, etc.

      The table of options and types is automatically generated and then human-checked. It should be easy to keep it up to date.
      The changes to the Chukwa codebase should be quite modest: one new Jar, and a handful of lines to invoke that Jar on startup.

      Does this sound like a thing people would like to see?

      1. confspellcheck.jar
        24 kB
        Ari Rabkin
      2. CHUKWA-527.patch
        7 kB
        Ari Rabkin
      3. options.dict
        2 kB
        Ari Rabkin


        Ari Rabkin made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ari Rabkin made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Ari Rabkin made changes -
        Attachment CHUKWA-527.patch [ 12456814 ]
        Attachment confspellcheck.jar [ 12456815 ]
        Ari Rabkin made changes -
        Attachment options.dict [ 12456299 ]
        Ari Rabkin made changes -
        Attachment options.dict [ 12456299 ]
        Ari Rabkin made changes -
        Field Original Value New Value
        Attachment options.dict [ 12456298 ]
        Ari Rabkin created issue -


          • Assignee:
            Ari Rabkin
            Ari Rabkin
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: