Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 410E31089C for ; Wed, 4 Feb 2015 09:41:04 +0000 (UTC) Received: (qmail 18735 invoked by uid 500); 4 Feb 2015 09:41:05 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 18699 invoked by uid 500); 4 Feb 2015 09:41:05 -0000 Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list dev@ignite.incubator.apache.org Received: (qmail 18666 invoked by uid 99); 4 Feb 2015 09:40:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2015 09:40:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vozerov@gridgain.com designates 209.85.192.47 as permitted sender) Received: from [209.85.192.47] (HELO mail-qg0-f47.google.com) (209.85.192.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2015 09:40:50 +0000 Received: by mail-qg0-f47.google.com with SMTP id l89so338555qgf.6 for ; Wed, 04 Feb 2015 01:40:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=fa4h7JoXPX1isj2RPZjB9cwZF+IqyXLY330QPZNBYzU=; b=bfRFeBbhFW/yFxbs1m0mG4hyMSyV83Ztxi7VUNPNc+HawMguLoM4tlJ9rdcpxFJoCZ 3inxvhXQ3dJ9Ub2DQge95YGDr/x3mmXoZQzekTbu72g7orWlNpSes4wKqyNeWp3IAyhB 3atMJ4G68q9tVTsQnlfGuGJUwcKiKFEIPVlPn5QLVKu5cMwl0d4vt0/ytlHR6cDk2165 akAO9tSVf7w3OOGF1bXpTls5uPPJ3qJz9Ctgqnw5MxROOSlwJMgVCoGg3G4LVH5isGOR M65idvUHR2u5S8jmJ8NWFhvEhThTJPCPmFSJ07bn8wafjMS3D1WOl0VlcKw2YCMc4zjA rnpw== X-Gm-Message-State: ALoCoQkEtt0zOP6TsEP0ZNu87W8rcsXezuN5e1rGgXRK4gdwzTWQuQOR3n8xJUrRYWRW2FMEf25R MIME-Version: 1.0 X-Received: by 10.229.125.133 with SMTP id y5mr19197475qcr.17.1423042829405; Wed, 04 Feb 2015 01:40:29 -0800 (PST) Received: by 10.140.98.247 with HTTP; Wed, 4 Feb 2015 01:40:29 -0800 (PST) Date: Wed, 4 Feb 2015 12:40:29 +0300 Message-ID: Subject: "executorServiceShutdown" properties concept review. From: Vladimir Ozerov To: dev@ignite.incubator.apache.org Content-Type: multipart/alternative; boundary=001a1133d99659013a050e3ffa66 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133d99659013a050e3ffa66 Content-Type: text/plain; charset=UTF-8 Hi, I'd like to start the discussion about infamous "shutdown" properties in configuration classes: - IgniteConfiguration.executorServiceShutdown() - IgniteConfiguration.ggfsExecutorServiceShutdown() - IgniteConfiguration.managementExecutorServiceShutdown() - IgniteConfiguration.peerClassLoadingExecutorServiceShutdown() - IgniteConfiguration.systemExecutorServiceShutdown() - IgniteConfiguration.restExecutorServiceShutdown() - ClientConnectionConfiguration.restExecutorServiceShutdown() This yields in 12 additional methods in IgniteConfiguration and 2 in ClientConnectionConfiguration. Reason why we have these properties is clear: if you starts Ignite in embedded mode and provides his own thread pool, he may want to keep it running even after Ignite node is stopped. On the other hand, it seems to me that custom executor service is pretty unusal and rare use case. What if we create wrapper class encapsulating both executor service and shutdown flag? E.g.: IgniteExecutorServiceConfiguration { ExecutorService getExecutorService(); bool isExecutorServiceShutdown(); } This will remove 6 properties. +19 deprecated client-related properties which are also will be removed. In summary, we will be able to remove 25 properties (of 103 currently) from IgniteConfiguration. Any thoughts on this? Vladimir. --001a1133d99659013a050e3ffa66--