[jira] [Closed] (GEODE-1507) gfsh variable substitution does not work

2018-08-18 Thread JIRA 


 [ 
https://issues.apache.org/jira/browse/GEODE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Juan José Ramos Cassella closed GEODE-1507.
---

Changes merged into develop.

> gfsh variable substitution does not work
> 
>
> Key: GEODE-1507
> URL: https://issues.apache.org/jira/browse/GEODE-1507
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Juan José Ramos Cassella
>Priority: Major
>
> {noformat}
> gfsh>set variable --name=foo --value=bar
> Value for variable foo is now: bar.
> gfsh>echo --string="Hello ${foo}"
> Hello ${foo}
> {noformat}
> The problem has come in with spring-shell and jline replacement. 
> {{Gfsh.executeCommand}} was replaced with {{Gfsh.executeScriptLine}} which 
> ends up never being called unless a script is executed with {{run --file}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-1507) gfsh variable substitution does not work

2018-08-18 Thread JIRA 


 [ 
https://issues.apache.org/jira/browse/GEODE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Juan José Ramos Cassella updated GEODE-1507:

Fix Version/s: 1.7.0

> gfsh variable substitution does not work
> 
>
> Key: GEODE-1507
> URL: https://issues.apache.org/jira/browse/GEODE-1507
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Fix For: 1.7.0
>
>
> {noformat}
> gfsh>set variable --name=foo --value=bar
> Value for variable foo is now: bar.
> gfsh>echo --string="Hello ${foo}"
> Hello ${foo}
> {noformat}
> The problem has come in with spring-shell and jline replacement. 
> {{Gfsh.executeCommand}} was replaced with {{Gfsh.executeScriptLine}} which 
> ends up never being called unless a script is executed with {{run --file}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5224) statistics of Type DiskRegionStatistics is not correct after recovery from eviction

2018-08-18 Thread yossi reginiano (JIRA) 


[ 
https://issues.apache.org/jira/browse/GEODE-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585032#comment-16585032
 ] 

yossi reginiano commented on GEODE-5224:


hi Darrel,

sorry for the Semantic error - u are correct our region is defined as an 
Overflow one - once LRU size is reached, the LRU value is overflow to Disk 

we observe the statistics discrepancy in the following scenario:

after some time the LRU size was reached and we moved into Eviction - in which 
some values are overflow to disk

once we have recovered from Eviction (all records were handled and removed) , 
we face the following statistics discrepancy - *entriesOnlyOnDisk is not 
reduced to 0 but rather stay high and on the other end - entriesInVM is reduced 
under 0*

*now seems like this issue is only a statistic one*

> statistics of Type DiskRegionStatistics is not correct after recovery from 
> eviction
> ---
>
> Key: GEODE-5224
> URL: https://issues.apache.org/jira/browse/GEODE-5224
> Project: Geode
>  Issue Type: Bug
>  Components: eviction
>Affects Versions: 1.4.0
>Reporter: yossi reginiano
>Priority: Major
>  Labels: pull-request-available
> Attachments: EntriesInVM.png, EntriesOnlyOnDisk.png
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> we are using geode 1.4 and facing the following issue
> after getting into eviction we can see that entriesOnlyOnDisk is shown 
> correctly, the problem is when getting out of eviction - we can see that the 
> summarize is getting messed up and that entriesOnlyOnDisk is not reduced to 0 
> but rather stay high and on the other end - entriesInVM is reduced under 0.
> the numbers sum up ok - the issue is only that we reduce too much from 
> entriesInVM while part of it should have been removed from entriesOnlyOnDisk.
> the issue can be reproduced very simply by getting into and out of eviction 
> and monitoring the statistics.
> please see following screen shots that describes the issue-
> !image-2018-05-16-15-02-35-522.png!
>  
>  
> !image-2018-05-16-15-03-18-815.png!
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)