From dev-return-31669-archive-asf-public=cust-asf.ponee.io@geode.apache.org Wed Aug 21 01:12:48 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id BB09818063F for ; Wed, 21 Aug 2019 03:12:47 +0200 (CEST) Received: (qmail 57612 invoked by uid 500); 21 Aug 2019 01:12:47 -0000 Mailing-List: contact dev-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list dev@geode.apache.org Received: (qmail 57601 invoked by uid 99); 21 Aug 2019 01:12:46 -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, 21 Aug 2019 01:12:46 +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 7453A182AD8 for ; Wed, 21 Aug 2019 01:12:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.301 X-Spam-Level: * X-Spam-Status: No, score=1.301 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id KLxrT4Rp-9Iv for ; Wed, 21 Aug 2019 01:12:44 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=148.163.150.38; helo=mx0a-00296801.pphosted.com; envelope-from=mstolz@pivotal.io; receiver= Received: from mx0a-00296801.pphosted.com (mx0a-00296801.pphosted.com [148.163.150.38]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 3568C7DD38 for ; Wed, 21 Aug 2019 01:12:42 +0000 (UTC) Received: from pps.filterd (m0114582.ppops.net [127.0.0.1]) by mx0a-00296801.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7L161tS029035 for ; Wed, 21 Aug 2019 01:12:40 GMT Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by mx0a-00296801.pphosted.com with ESMTP id 2ugu70815y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 21 Aug 2019 01:12:40 +0000 Received: by mail-io1-f70.google.com with SMTP id v3so846705ios.4 for ; Tue, 20 Aug 2019 18:12:40 -0700 (PDT) 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=NhiVdlyKTzon4G/ZZkLCzuLL5iFx8otLOEst62AAsug=; b=JBiIoTvHsoOFUhYcPzPZOwqwOjLAwEEIdvXkF1irPCLvJTZeyLlWw/DOieBVoYEMFt iokw9wjXVTeQcsVaF38UbzKyuZYZiApt5RokwKKYSGea9xvgBshElx0W4jZ1jZg0X+2v Zqf2fwAZLN4D1H54NDtInT7kOd7lXDUMImC7RhRGC6IUDj5U5vkdrK0pPlLd0rHbGfgv HXzDl1fewSWhEy/QYevnpBfLQ+ULxhvwrK8RFxyk31nGKjd+fC8aIMnoNyt+TMV8yz8p sFZWuGb4iAtqeWYXpXuE0t5ZiYrUlCauyTSCS9Dpxoz8KL8ncs+gaHqviR3jXYNZ40Di 9EVA== X-Gm-Message-State: APjAAAWv/tbxVOTZlc+49PBWHppzwMG37ZJ9wC5REHKTH4iftpCc50B+ nIO5SMS8RM8i/qDWr1no2jjDF0CQmEv8uIi5uJh8+8XvXfnt1OgcZC0VXZt8fiqs2J7ATwZT2SQ dmDdyQ25OKnLa72eFrLYRob4F2vv1fA7FKMgWE2C+JJy2/NapQvJx0MA= X-Received: by 2002:a6b:7807:: with SMTP id j7mr36122715iom.224.1566349959543; Tue, 20 Aug 2019 18:12:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwjvGA/UAj0kDJjIhFlEDclaummDD1znq/FZjGv98W3C0vXsQLkwOp2+j6YD57vkO5995w3LOHn8iZNS8SNE+o= X-Received: by 2002:a6b:7807:: with SMTP id j7mr36122671iom.224.1566349959095; Tue, 20 Aug 2019 18:12:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Michael Stolz Date: Tue, 20 Aug 2019 21:12:26 -0400 Message-ID: Subject: Re: [DISCUSS] what region types to support in the new management rest api To: geode Content-Type: multipart/alternative; boundary="000000000000e7fe390590964471" X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-21_01:2019-08-19,2019-08-21 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 lowpriorityscore=0 clxscore=1015 suspectscore=1 priorityscore=1501 mlxscore=0 bulkscore=0 impostorscore=0 spamscore=0 mlxlogscore=999 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908210007 --000000000000e7fe390590964471 Content-Type: text/plain; charset="UTF-8" I'm not at all sure why supporting the current set is more work than a subset. Are we planning to fix issues in the current implementation in the new API rather than the underlying (still needed) existing API? How is that a good idea? -- Mike Stolz Principal Engineer, Pivotal Cloud Cache Mobile: +1-631-835-4771 On Tue, Aug 20, 2019, 9:09 PM Anilkumar Gingade wrote: > My vote is for supporting all the region type currently supported. As mike > was pointing, we have seen usecases where different regions are used for > specific application needs. > > > > On Tue, Aug 20, 2019 at 5:09 PM Darrel Schneider > wrote: > > > gfsh create region currently does not support "distributed-no-ack" nor > > "global". I did not find in jira a feature request for gfsh to support > > these. So I think it would be safe for the Geode Management REST API to > > also not support those scopes. > > > > > > On Tue, Aug 20, 2019 at 12:10 PM Kirk Lund wrote: > > > > > Here's my 2cents: The Geode Management REST API should definitely > support > > > "group" such that creation of a region may target zero, one, or more > > > groups. > > > > > > On Tue, Aug 20, 2019 at 10:45 AM Darrel Schneider < > dschneider@pivotal.io > > > > > > wrote: > > > > > > > Is "group" support on the PCC roadmap or is the plan for the members > > of a > > > > cluster to always be uniform? > > > > > > > > On Tue, Aug 20, 2019 at 9:56 AM Jinmei Liao > wrote: > > > > > > > > > So, sound like we still need to support *PROXY types. It's OK to > drop > > > > > support for LOCAL* region types in management rest API? > > > > > > > > > > Also, regarding existing region shortcuts, we are also > experimenting > > > > using > > > > > different object types to represent different types of region, for > > > > example, > > > > > redundantCopies property should only exists in partition regions. > > > Instead > > > > > of having a flat object that could have a type of any of these > values > > > and > > > > > holds all sorts of properties that may/may not make sense for that > > > type, > > > > > should just have a factory method that given these region > shortcuts, > > we > > > > > would return a specific region object that's determined by this > type? > > > > > > > > > > On Tue, Aug 20, 2019 at 8:15 AM Jens Deppe > > wrote: > > > > > > > > > > > Currently, when deployed to the cloud (aka PCC) there is no > ability > > > > for a > > > > > > user to group members thus it is also not possible to create > > regions > > > > (via > > > > > > gfsh at least) that are separated by groups. Typically one would > > > > create a > > > > > > PROXY region against one group and the PARTITION region against > > > another > > > > > > group. However, without the ability to assign groups, that is not > > > > > possible. > > > > > > > > > > > > --Jens > > > > > > > > > > > > On Tue, Aug 20, 2019 at 7:46 AM Michael Stolz > > > > > wrote: > > > > > > > > > > > > > I know that lots of folks use PROXY regions on the server side > to > > > > host > > > > > > > logic associated with the region, but I think they always do > that > > > in > > > > > > > conjunction with server groups so that the proxy is on some of > > the > > > > > server > > > > > > > and the same region containing data is on others. Given the way > > > > > cache.xml > > > > > > > works they might not even bother with the server groups, but > I'm > > > not > > > > > > sure. > > > > > > > > > > > > > > I think we should carry forward the existing shortcuts and not > go > > > > > > backward > > > > > > > to the separate attributes. > > > > > > > > > > > > > > -- > > > > > > > Mike Stolz > > > > > > > Principal Engineer, Pivotal Cloud Cache > > > > > > > Mobile: +1-631-835-4771 > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Aug 19, 2019 at 7:59 PM Darrel Schneider < > > > > > dschneider@pivotal.io> > > > > > > > wrote: > > > > > > > > > > > > > > > Keep in mind that the context of the regions in question is > the > > > > > > cluster. > > > > > > > So > > > > > > > > these regions would be created on servers. > > > > > > > > So, for example, does anyone see a need to create PROXY > regions > > > on > > > > > the > > > > > > > > server? Even if we did not support them on the server, they > > would > > > > > still > > > > > > > be > > > > > > > > supported on clients. > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Aug 19, 2019 at 4:26 PM Jinmei Liao < > jiliao@pivotal.io > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Region type (in another word Region shortcut) defines a set > > of > > > > > > > attributes > > > > > > > > > for a region. These are the list of region types we have: > > > > > > > > > > > > > > > > > > LOCAL, > > > > > > > > > LOCAL_PERSISTENT, > > > > > > > > > LOCAL_HEAP_LRU, > > > > > > > > > LOCAL_OVERFLOW, > > > > > > > > > LOCAL_PERSISTENT_OVERFLOW, > > > > > > > > > > > > > > > > > > PARTITION, > > > > > > > > > PARTITION_REDUNDANT, > > > > > > > > > PARTITION_PERSISTENT, > > > > > > > > > PARTITION_REDUNDANT_PERSISTENT, > > > > > > > > > PARTITION_OVERFLOW, > > > > > > > > > PARTITION_REDUNDANT_OVERFLOW, > > > > > > > > > PARTITION_PERSISTENT_OVERFLOW, > > > > > > > > > PARTITION_REDUNDANT_PERSISTENT_OVERFLOW, > > > > > > > > > PARTITION_HEAP_LRU, > > > > > > > > > PARTITION_REDUNDANT_HEAP_LRU, > > > > > > > > > > > > > > > > > > REPLICATE, > > > > > > > > > REPLICATE_PERSISTENT, > > > > > > > > > REPLICATE_OVERFLOW, > > > > > > > > > REPLICATE_PERSISTENT_OVERFLOW, > > > > > > > > > REPLICATE_HEAP_LRU, > > > > > > > > > > > > > > > > > > REPLICATE_PROXY, > > > > > > > > > PARTITION_PROXY, > > > > > > > > > PARTITION_PROXY_REDUNDANT, > > > > > > > > > > > > > > > > > > In region management rest api, especially in PCC world, we > > are > > > > > > > wondering > > > > > > > > > 1) should we allow users to create LOCAL* regions through > > > > > management > > > > > > > rest > > > > > > > > > api? > > > > > > > > > 2) should we allow users to create *PROXY regions through > > > > > management > > > > > > > rest > > > > > > > > > api? > > > > > > > > > 3) for the rest of the PARTITION* and REPLICATE* types, > > should > > > we > > > > > > > strive > > > > > > > > to > > > > > > > > > keep the region type list the same as before, or only keep > > the > > > > type > > > > > > as > > > > > > > > > REPLICATE/PARTITION, but use other properties like > > > > "redundantCopy" > > > > > > and > > > > > > > > > "evictionAction" to allow different permutations of region > > > > > > attributes? > > > > > > > > > > > > > > > > > > comments appreciated! > > > > > > > > > -- > > > > > > > > > Cheers > > > > > > > > > > > > > > > > > > Jinmei > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Cheers > > > > > > > > > > Jinmei > > > > > > > > > > > > > > > --000000000000e7fe390590964471--