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 69C2F200C1B for ; Tue, 14 Feb 2017 15:23:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 68548160B5F; Tue, 14 Feb 2017 14:23:45 +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 B3CD3160B52 for ; Tue, 14 Feb 2017 15:23:44 +0100 (CET) Received: (qmail 6894 invoked by uid 500); 14 Feb 2017 14:23:43 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 6883 invoked by uid 99); 14 Feb 2017 14:23:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2017 14:23:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 789DC1A03C8 for ; Tue, 14 Feb 2017 14:23:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JXP9nvd0FQb8 for ; Tue, 14 Feb 2017 14:23:43 +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 A7A015F570 for ; Tue, 14 Feb 2017 14:23:42 +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 E94F6E00C7 for ; Tue, 14 Feb 2017 14:23:41 +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 9E6FD2411B for ; Tue, 14 Feb 2017 14:23:41 +0000 (UTC) Date: Tue, 14 Feb 2017 14:23:41 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-4699) Introduce custom configurable executors. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 14 Feb 2017 14:23:45 -0000 Vladimir Ozerov created IGNITE-4699: --------------------------------------- Summary: Introduce custom configurable executors. Key: IGNITE-4699 URL: https://issues.apache.org/jira/browse/IGNITE-4699 Project: Ignite Issue Type: Task Components: compute Reporter: Vladimir Ozerov Fix For: 2.0 We need to provide a way to configure custom thread pools for user compute tasks. Proposed API: 1) Config {code} class ExecutorConfiguration { String name; int size; } {code} 2) Choosing executor for compute task: {code} IgniteCompute compute = Ignite.compute().withExecutor("my_exec"); {code} 3) Accessing raw executor (could be required for proper execution of future listeners): {code} ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec"); {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)