Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-12464

reduce Overseer.close() logging (for non-Overseer leaders)

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5, master (8.0)
    • Component/s: logging
    • Labels:
      None

      Description

      ZkController.init creates an Overseer object:

      • If that object becomes overseer leader then its start method is called.
      • If the object does not become overseer leader then its close method is called and that currently emits mildly confusing Overseer (id=null) closing info logging – confusing especially since this happens at node startup.

      ZkController.init creates an Overseer object:

      • If that object becomes overseer leader then its start method is called and (if assertions are enabled) ObjectReleaseTracker.track is called.
      • If the object does not become overseer leader then its close method is called and (if assertions are enabled) ObjectReleaseTracker.release is called despite ObjectReleaseTracker.track not having been called previously.

        Attachments

        1. SOLR-12464.patch
          1 kB
          Christine Poerschke
        2. SOLR-12464-ea.patch
          0.5 kB
          Christine Poerschke

          Issue Links

            Activity

              People

              • Assignee:
                cpoerschke Christine Poerschke
                Reporter:
                cpoerschke Christine Poerschke
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: