From dev-return-46129-apmail-ignite-dev-archive=ignite.apache.org@ignite.apache.org Tue Jun 4 11:17:49 2019 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 [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id 83F4C19486 for ; Tue, 4 Jun 2019 11:17:49 +0000 (UTC) Received: (qmail 17732 invoked by uid 500); 4 Jun 2019 11:17:45 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 17691 invoked by uid 500); 4 Jun 2019 11:17:45 -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 17670 invoked by uid 99); 4 Jun 2019 11:17:45 -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, 04 Jun 2019 11:17:45 +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 805101A4444 for ; Tue, 4 Jun 2019 11:17:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.053 X-Spam-Level: ** X-Spam-Status: No, score=2.053 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 hobDoZLqgW3B for ; Tue, 4 Jun 2019 11:17:40 +0000 (UTC) Received: from mail-qt1-f193.google.com (mail-qt1-f193.google.com [209.85.160.193]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 556FD5F3AE for ; Tue, 4 Jun 2019 11:17:40 +0000 (UTC) Received: by mail-qt1-f193.google.com with SMTP id d23so13226994qto.2 for ; Tue, 04 Jun 2019 04:17:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XpoeKAGVO9JXJ9Uj2y7bpYeQMvcoESQbbJ++bU0PaWU=; b=UHoEz31DosXflCL07W9cuQ9z/Nt+cJRyawwfp/8tgTJh2HfwanoiNAwTrTOP9OXAoI 1r8k9M+v7BehhJtJEYrgm96SMJNtgdCgie2vDPif3ALgxIzxqd9HQ6b96i7KOcHGmhI+ /0JsxiAJE09o14fLBltNW3cZ8AVuh0tfBXICzd32m+194ViakN2XIuXrG5/dzMuHWIHS 8tanOd9QhNWmvJ15z15m5P/TLXld9b5STtNiAgLRhvuQ2kGgYfFNsRuTiMDEkLhXXGKe oK2HkI8mFrjO3WjQkO/TCxfxTvsdmK7jnKmv2akbPu/Znxl9o4xfXc9QNYj58b50HD5o KmLw== 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=XpoeKAGVO9JXJ9Uj2y7bpYeQMvcoESQbbJ++bU0PaWU=; b=ZPkhjH1BHkXeaLK7+gvlC4XLXTqGGiIdwt81UWmFxGaZeZALDXAQK+9Cr+/H5/ITKZ 5F6Fg4xmnCOLaoVPqX/RYR7+tRQ5bNoIxYu0gBRAfpWJ3U3erPIOYtInmVdd8EbRQh1z wxMpxb8IYFIZbQpC1vBG10jwq9DOwwhXtPE9/Hkusl95Nx6oGj8ww2ST7frNB7oTw4Y4 GrZpluhPPgYzNMI+Jh9raU2FyE+y2uwd0MJySpUIdPV5bS1uTmb1yp4ve9qqx8Za1jiL 1dM59r5vqRQsmGYkXXNGnXWgTlFXoz2GdTl3t88A8I84MjROhjdo6H1ZsbOTdKaaWgQj RwdA== X-Gm-Message-State: APjAAAU/cm0e8iWlxpopxF052O6JOFwdTIiNsL0rd2PQN6K4zk5I4rjg Fa6PEBIEKKrVI32pjCze1hB/FjYSp8R+ga5IsDEQ0iKI1Pw= X-Google-Smtp-Source: APXvYqz7rYM76X3BLRSNrQY/M+FcrgGC4p+OfsGcaia3p5EPJA3EINSkdsqCxaSZv70AM9msGXT9wE5zDSJHb/aivqc= X-Received: by 2002:ac8:2418:: with SMTP id c24mr27536823qtc.37.1559647053510; Tue, 04 Jun 2019 04:17:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sergey Antonov Date: Tue, 4 Jun 2019 14:17:20 +0300 Message-ID: Subject: Re: {DISCUSSION] Cluster read-only mode. To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="000000000000997d8d058a7da083" --000000000000997d8d058a7da083 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, Ivan. >>What is a fundamental difference between them? On inactive cluster caches aren't started. So you can't get data from cache. =D0=B2=D1=82, 4 =D0=B8=D1=8E=D0=BD. 2019 =D0=B3. =D0=B2 12:16, =D0=9F=D0=B0= =D0=B2=D0=BB=D1=83=D1=85=D0=B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD : > Sergey, Igniters, > > Sorry if my question is not very smart. > > I am trying to think about it from a perspective of a (newbie) user. > And from the first glance it is not clear how a read-only cluster is > different from a not active cluster? What is a fundamental difference > between them? Can we combine two modes into one? If not we will need a > clear explanation for a user. > > =D0=BF=D0=BD, 3 =D0=B8=D1=8E=D0=BD. 2019 =D0=B3. =D0=B2 20:15, Maxim Muza= farov : > > > > Sergey, > > > > Do we have an IEP for this feature? > > > > What should happen when on an active cluster with put operations if we > > receive a read-only state change request? How we guarantee that all > > cache operations delivered (or not yet) to backups are not rejected by > > applied read-only request? I haven't found such tests in your PR. > > > > I've downloaded your branch and run some tests locally. I've tried > > DataStreamer cache loads (allowOverwrite mode false) with a concurrent > > cluster change state request to read-only mode and I've got strange > > behaviour. My test scenario was: > > 1) Start DataStremer cache load; > > 2) change cluster to read-only state; > > 3) change state back to normal; > > > > When the state has been changed to `read-only` I've flooded with a lot > > of `Failed to perform cache operation (cluster is in read-only mode)` > > errors, but when I've reverted the state back the DataStreamer > > continue its load without any error. I think we should not allow such > > behaviour. We should cancel the DataStreamer task or allow it to be > > finished. > > > > On Fri, 31 May 2019 at 13:00, Sergey Antonov > wrote: > > > > > > Hello, Zhenya, Maxim! > > > > > > Thank you for your replies! > > > > > > >> Should we also allow writes to the DistributedMetaStorage and if > not why? > > > Yes. DistributedMetastorage available for updates with enabled > read-only > > > mode. I added test about it to ClusterReadOnlyModeSelfTest > > > > > > >> What's the purpose for ignite-sys-cache updates still be available= ? > > > ignite-sys-cache is using in the different subcomponents, for example= , > > > security. > > > > > > =D1=87=D1=82, 30 =D0=BC=D0=B0=D1=8F 2019 =D0=B3. =D0=B2 20:30, Zhenya= Stanilovsky > : > > > > > > > hi, Sergey. > > > > What's the purpose for ignite-sys-cache updates still be available = ? > > > > > > > > thanks ! > > > > > > > > > Hello Igniters! > > > > > > > > > > I'm working on cluster read-only mode [1] feature. In this mode > cluster > > > > > will be available only for read operations, all data modification > > > > > operations in user caches will be rejected > > > > > with ClusterReadOnlyModeCheckedException. This feature could be > helpfull > > > > > for maintenance works (control.sh idle_verify/validate_indexes). > > > > > > > > > > A few points about cluster read-only mode: > > > > > 1) Read-only mode could be enabled on active cluster only. > > > > > 2) Read-only mode doens't store on PDS (i.e. after cluster restar= t > > > > > enabled > > > > > read-only mode will be forgotten) > > > > > 3) Updates to ignite-sys-cache will be available with enabled > read-only > > > > > mode. > > > > > > > > > > More informartion about implementation you could find in PR [2]. > > > > > > > > > > What do you think about this feature? > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11256 > > > > > [2] https://github.com/apache/ignite/pull/6423 > > > > > > > > > > > > > -- > > > BR, Sergey Antonov > > > > -- > Best regards, > Ivan Pavlukhin > --=20 BR, Sergey Antonov --000000000000997d8d058a7da083--