From dev-return-42214-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Nov 21 14:56:25 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E91F3180668 for ; Wed, 21 Nov 2018 14:56:24 +0100 (CET) Received: (qmail 53287 invoked by uid 500); 21 Nov 2018 13:56:24 -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 53216 invoked by uid 99); 21 Nov 2018 13:56:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2018 13:56:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id EA475C0629 for ; Wed, 21 Nov 2018 13:56:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.54 X-Spam-Level: X-Spam-Status: No, score=0.54 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id CTqOnRGTm9Dj for ; Wed, 21 Nov 2018 13:56:20 +0000 (UTC) Received: from mail-vs1-f45.google.com (mail-vs1-f45.google.com [209.85.217.45]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E405A5FB80 for ; Wed, 21 Nov 2018 13:56:19 +0000 (UTC) Received: by mail-vs1-f45.google.com with SMTP id x64so3284372vsa.5 for ; Wed, 21 Nov 2018 05:56:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=eFz1a6obRrA/PIE3hsSHNQ9uMxPxyTVPy2wnMTuoeOk=; b=EKso/vnRAFNTblrEj5rHigA3Dw39MVlLGQdzvqh1kZ8k7ZSkNNKRY2W4/sPuOEUBcU w42OEQ1QExmmbEjNfByrYsrhu4ICWyu2Wph8sIt6kzNWpkN27OWIQ0+/WwMmIR8/ApQR A+6rQ9g/2teVyB/RjbsolhNf956KH52GBSdGSS/tdtsRbQWRMfU4xRR05aTys8T45q4L 9KyvuKGRzXUFKmNrdLzQQIsyv0TqNoFP/jQWZGrywhodFvS7DmS1Hz2Qh5OYyFNCQiSj wVTN41/eg+fZ+QyCgawqCQXyQoZ7RB7DRIRdK/ALoDrTg1WKD4KBuu7lByELaaJ453Qk OmKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=eFz1a6obRrA/PIE3hsSHNQ9uMxPxyTVPy2wnMTuoeOk=; b=j0DtUQylpKZUFtu1sgAc41KEBKY+WT9xsvOWvEEb9ntnedu9ed+eeFVBXhnbpGtMjE /DoYUKtN0PK4hOWlEQDKrzYReN0731jFSisOZwPWHzVnBfA5JgIHS8guwpjyJKbNc+g2 zbBLSLdYfQt2fFxHJMr3AWBbv9tpys+VIBX9UP74xeG1ODUkEZP/iOhp/EdncW3Z+bjE CwWnDbvPe7qLphESPJpj7UImESpgnH5s9beBmuM0vs3hh9peZ/aVyydCtDSmF9tlTRcd TziSyZZTNNzJIQTXp6Jq/8EYEA/nZr+ND+NN79f32i1v4OZhxDDaUUxy8tiyWmTVQfyF HIPQ== X-Gm-Message-State: AA+aEWaZUroZHjIBsbJJtXrAGF7EDtYQ+6jLWLYFkatIKpPJp6RGqBxh qW9v0gpiHb0Y/uSTfLy73C3UBNkftbyVOlFv3hmSLFig X-Google-Smtp-Source: AJdET5f2VgYzscC/yzyfbaDVOHl66UVjoElvuusUqpk/z3TUoYa6+Ne1WY31Dwfpvugd3qp0A4L3XAw9PcwopAl8cy4= X-Received: by 2002:a67:3a1c:: with SMTP id h28mr2818785vsa.218.1542808573159; Wed, 21 Nov 2018 05:56:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vladimir Ozerov Date: Wed, 21 Nov 2018 16:56:01 +0300 Message-ID: Subject: Re: New API for changing configuration of persistent caches To: dev Content-Type: multipart/alternative; boundary="000000000000f5c3d8057b2d1c4c" --000000000000f5c3d8057b2d1c4c Content-Type: text/plain; charset="UTF-8" Hi Ed, Several questions from my side: 1) If we do not allow to change the most demanded by users things like affinity or persistence/in-memory, then what kind of configuration properties do we expect to be changed? Can we have several examples? 2) How will it interact with PME? 3) How will it interact with CREATE INDEX and ALTER TABLE commands? On Wed, Nov 21, 2018 at 4:48 PM Eduard Shangareev < eduard.shangareev@gmail.com> wrote: > Igniters, > > I propose new public API to change the cache configuration of persistent > caches with keeping data. > > It would look like: > > Ignite ignite = ...; > ignite.restartCaches(cfg1, ... cfgN); > > where cfgX is a new cache configuration, which contains the name of an > existing persistent cache. > > The obvious limitation: > - affinity key mapping couldn't be changed; > - count of partitions couldn't be changed; > - MVCC couldn't be turned off/on; > - persistent couldn't be turned off; > - group settings couldn't be changed (group name); > - if cache belongs to group it's needed to restart all of them. > > Failure scenario is the crucial thing (and most difficult): > - initiator fail; > - cluster restart at any stage; > - joining/starting offline nodes. > > Some thoughts about implementation: > - stop cache with destroy=false; > - start cache dynamically with new configuration; > - if indexes settings changed - remove index.bin to start indexation; > - change blt-history when start cache initiated to not allow join nodes > with old configuration; > - use restartId (IGNITE-8911) to not allow to start cache in between. > > Your thoughts? Would it be a useful feature? > --000000000000f5c3d8057b2d1c4c--