Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4C2C4200D1E for ; Wed, 18 Oct 2017 11:14:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4AAD7160BEF; Wed, 18 Oct 2017 09:14:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8E302160BEA for ; Wed, 18 Oct 2017 11:14:06 +0200 (CEST) Received: (qmail 51642 invoked by uid 500); 18 Oct 2017 09:14:05 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 51633 invoked by uid 99); 18 Oct 2017 09:14:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Oct 2017 09:14:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D5D6F1806CD for ; Wed, 18 Oct 2017 09:14:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Q3JnDWVX8DpD for ; Wed, 18 Oct 2017 09:14:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E3E495FD38 for ; Wed, 18 Oct 2017 09:14:03 +0000 (UTC) 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 77B6EE06BB for ; Wed, 18 Oct 2017 09:14:03 +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 232392438C for ; Wed, 18 Oct 2017 09:14:02 +0000 (UTC) Date: Wed, 18 Oct 2017 09:14:02 +0000 (UTC) From: "Till Rohrmann (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-7866) Weigh list of preferred locations for scheduling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 18 Oct 2017 09:14:07 -0000 [ https://issues.apache.org/jira/browse/FLINK-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann updated FLINK-7866: --------------------------------- Description: [~sihuazhou] proposed to not only use the list of preferred locations to decide where to schedule a task, but to also weigh the list according to how often a location appeared and then select the location based on the weight. That way, we would obtain better locality in some cases. Example: Preferred locations list: {{ [location1, location2, location2] }} Weighted preferred locations list {{ [(location2 , 2), (location1, 1)] }} was: [~sihuazhou] proposed to not only use the list of preferred locations to decide where to schedule a task, but to also weigh the list according to how often a location appeared and then select the location based on the weight. That way, we would obtain better locality in some cases. Example: Preferred locations list: {{ {location1, location2, location2} }} Weighted preferred locations list {{ {(location2 , 2), (location1, 1)} }} > Weigh list of preferred locations for scheduling > ------------------------------------------------ > > Key: FLINK-7866 > URL: https://issues.apache.org/jira/browse/FLINK-7866 > Project: Flink > Issue Type: Improvement > Components: Scheduler > Affects Versions: 1.4.0, 1.3.2 > Reporter: Till Rohrmann > Fix For: 1.5.0 > > > [~sihuazhou] proposed to not only use the list of preferred locations to decide where to schedule a task, but to also weigh the list according to how often a location appeared and then select the location based on the weight. That way, we would obtain better locality in some cases. > Example: > Preferred locations list: {{ [location1, location2, location2] }} > Weighted preferred locations list {{ [(location2 , 2), (location1, 1)] }} -- This message was sent by Atlassian JIRA (v6.4.14#64029)