geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Bawaskar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-1897) Users should be able to configure eviction through gfsh
Date Sat, 18 Nov 2017 00:06:00 GMT

     [ 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)

Mime
View raw message