Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-4415

Reduce time to create and send MetadataUpdateRequest

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.10.1.0
    • 0.10.2.0
    • None
    • None

    Description

      As of current implementation, when controller receives ControlledShutdownRequest, it will 1) for every broker in the cluster, for every partition on the broker which wants to shutdown, create an instance of PartitionStateInfo and add it to ControllerBrokerRequestBatch.,updateMetadataRequestMap; and 2) for every broker, for every follower partitions on the broker which wants to shutdown, send one MetadataUpdateRequst to that broker.

      In order to shutdown a broker, the controller will need to instantiate O(partitionNum * brokerNum) PartitionStateInfo. This is not efficient. The broker should only need to instantiate O(partitionNum) PartitionStateInfo.

      Micro-benchmark results show that this optimization can reduce the time of processing ControlledShutdownRequest by 30%.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            lindong Dong Lin
            lindong Dong Lin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment