Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Won't Fix
    • Affects Version/s: 0.8.0
    • Fix Version/s: None
    • Component/s: controller
    • Labels:

      Description

      We created the state change log in KAFKA-513 which creates a well formatted log of the lifetime of all state change requests in a Kafka cluster. While troubleshooting KAFKA-790, I looked into server.log, controller.log and state-change.log and realized we can improve the controller logging -

      1. StopReplica state change is missing from the state-change.log
      2. Some state change log messages are repeated. These are likely mistakenly inside a for loop rather than outside
      3. Some controller logging that should be in the controller.log is still in server.log. For example, everything from ReplicaManager. This is useful for troubleshooting but confusing to be inside server.log.

        Activity

        Neha Narkhede created issue -
        Hide
        Swapnil Ghike added a comment -

        This should wait till KAFKA-793 is checked in.

        Show
        Swapnil Ghike added a comment - This should wait till KAFKA-793 is checked in.
        Hide
        Neha Narkhede added a comment -

        Sure, that works

        Show
        Neha Narkhede added a comment - Sure, that works
        Neha Narkhede made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Tony Stevenson made changes -
        Workflow no-reopen-closed, patch-avail [ 12770254 ] Apache Kafka Workflow [ 13052978 ]
        Tony Stevenson made changes -
        Workflow Apache Kafka Workflow [ 13052978 ] no-reopen-closed, patch-avail [ 13055002 ]
        Hide
        Gwen Shapira added a comment -

        Kinda old now Lets celebrate 3rd birthday by closing.

        We can create a new JIRA if we decide to tackle the cleanup again.

        Show
        Gwen Shapira added a comment - Kinda old now Lets celebrate 3rd birthday by closing. We can create a new JIRA if we decide to tackle the cleanup again.
        Gwen Shapira made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        23m 59s 1 Neha Narkhede 07/Mar/13 18:36
        In Progress In Progress Resolved Resolved
        1015d 5h 29m 1 Gwen Shapira 18/Dec/15 00:05

          People

          • Assignee:
            Neha Narkhede
            Reporter:
            Neha Narkhede
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development