From dev-return-104658-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Sun Jun 2 12:41:03 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 9355718064E for ; Sun, 2 Jun 2019 14:41:03 +0200 (CEST) Received: (qmail 87809 invoked by uid 500); 2 Jun 2019 12:41:01 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 87779 invoked by uid 99); 2 Jun 2019 12:41:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2019 12:41:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 63077E1025 for ; Sun, 2 Jun 2019 12:41:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1AD702459B for ; Sun, 2 Jun 2019 12:41:00 +0000 (UTC) Date: Sun, 2 Jun 2019 12:41:00 +0000 (UTC) From: "ChenLin (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-8465) Copying strategy for the topic dimension MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 ChenLin created KAFKA-8465: ------------------------------ Summary: Copying strategy for the topic dimension Key: KAFKA-8465 URL: https://issues.apache.org/jira/browse/KAFKA-8465 Project: Kafka Issue Type: Improvement Components: core Affects Versions: 2.2.1, 2.2.0, 2.0.1 Reporter: ChenLin When some partiton's replication is assigned to a broker, which disks should these copies be placed on the broker? The original strategy is to allocate according to the number of partiitons, but this will cause a partiton with too many topics to be stored on a disk, which may cause disk hotspot problems. In order to solve this problem, we propose an improved strategy: first ensure that the number of partitions of each disk in the topic dimension is even. If the number of partitions of a topic on two disks is equal, then sort according to the total number of partitions on the disk. Select a disk with the least number of partitions to store the current replication. -- This message was sent by Atlassian JIRA (v7.6.3#76005)