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 73BD0200D52 for ; Sat, 18 Nov 2017 01:06:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 72394160C0A; Sat, 18 Nov 2017 00:06:12 +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 B8EF2160BFB for ; Sat, 18 Nov 2017 01:06:11 +0100 (CET) Received: (qmail 66088 invoked by uid 500); 18 Nov 2017 00:06:10 -0000 Mailing-List: contact issues-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 issues@geode.apache.org Received: (qmail 66078 invoked by uid 99); 18 Nov 2017 00:06:10 -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; Sat, 18 Nov 2017 00:06:10 +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 096471A145C for ; Sat, 18 Nov 2017 00:06:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 1SZwSBZIxPqd for ; Sat, 18 Nov 2017 00:06:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 247745FC55 for ; Sat, 18 Nov 2017 00:06:02 +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 EE173E0EFA for ; Sat, 18 Nov 2017 00:06:00 +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 5522C240EA for ; Sat, 18 Nov 2017 00:06:00 +0000 (UTC) Date: Sat, 18 Nov 2017 00:06:00 +0000 (UTC) From: "Swapnil Bawaskar (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (GEODE-1897) Users should be able to configure eviction through gfsh MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 18 Nov 2017 00:06:12 -0000 [ https://issues.apache.org/jira/browse/GEODE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar updated GEODE-1897: ------------------------------------ Description: While creating a region in gfsh, users should be able to configure eviction for that region. All three modes of eviction should be supported: 1. Eviction driven by the resource manager: {noformat} gfsh>create region --name=myRegion --type=REPLICATE --eviction-enabled {noformat} 2. eviction driven by entry count in the region: {noformat} gfsh>create region --name=myRegion --type=REPLICATE --eviction-entry-count=1000 {noformat} 3. eviction driven by bytes used: {noformat} gfsh>create region --name=myRegion --type=REPLICATE --eviction-max-memory=100 (value in megabytes) {noformat} And also specify the eviction action as {noformat} --eviction-action=overflow-to-disk or --eviction-action=local-destroy {noformat} and an object sizer, so that users can plug-in custom object sizes as {noformat} --eviction-object-sizer=my.company.geode.MySizer {noformat} the sizer should only apply to heap and memory based eviction. was: While creating a region in gfsh, users should be able to configure eviction for that region. All three modes of eviction should be supported: 1. Eviction driven by the resource manager: {noformat} gfsh>create region --name=myRegion --type=REPLICATE --eviction-enabled {noformat} 2. eviction driven by entry count in the region: {noformat} gfsh>create region --name=myRegion --type=REPLICATE --eviction-entry-count=1000 {noformat} 3. eviction driven by bytes used: {noformat} gfsh>create region --name=myRegion --type=REPLICATE --eviction-max-memory=100 (value in megabytes) {noformat} And also specify the eviction action as {noformat} --eviction-action=overflow-to-disk or --eviction-action=local-destroy {noformat} > Users should be able to configure eviction through gfsh > ------------------------------------------------------- > > Key: GEODE-1897 > URL: https://issues.apache.org/jira/browse/GEODE-1897 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh > Reporter: Swapnil Bawaskar > Assignee: Jens Deppe > Fix For: 1.4.0 > > > While creating a region in gfsh, users should be able to configure eviction for that region. > All three modes of eviction should be supported: > 1. Eviction driven by the resource manager: > {noformat} > gfsh>create region --name=myRegion --type=REPLICATE --eviction-enabled > {noformat} > 2. eviction driven by entry count in the region: > {noformat} > gfsh>create region --name=myRegion --type=REPLICATE --eviction-entry-count=1000 > {noformat} > 3. eviction driven by bytes used: > {noformat} > gfsh>create region --name=myRegion --type=REPLICATE --eviction-max-memory=100 > (value in megabytes) > {noformat} > And also specify the eviction action as > {noformat} > --eviction-action=overflow-to-disk or > --eviction-action=local-destroy > {noformat} > and an object sizer, so that users can plug-in custom object sizes as > {noformat} > --eviction-object-sizer=my.company.geode.MySizer > {noformat} > the sizer should only apply to heap and memory based eviction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)