[jira] [Created] (GEODE-2097) Offheap persistent heapLRU regions can run out of offheap memory during recovery
Darrel Schneider created GEODE-2097:
---
Summary: Offheap persistent heapLRU regions can run out of offheap
memory during recovery
Key: GEODE-2097
URL: https://issues.apache.org/jira/browse/GEODE-2097
Project: Geode
Issue Type: Bug
Components: offheap
Reporter: Darrel Schneider
When the data for a persistent region is being recovered from the disk store
the lru limit is constantly checked. If the lru limit is exceeded then value
recovery will cease. But for off-heap regions this lru limit should be checking
how much off-heap memory has been allocated.
During recovery the amount of heap memory is being checked for an offheap
regions. So we can end up recovering too many values to off-heap and running
out of off-heap memory during recovery.
The code that causes this problem is:
org.apache.geode.internal.cache.lru.HeapLRUCapacityController.createLRUHelper().new
AbstractEnableLRU() {...}.mustEvict(LRUStatistics, Region, int)
During off-heap disk store recovery the Region parameter passed to this method
is "null". This causes the following heap check to be done:
if (region == null) {
return resourceManager.getHeapMonitor().getState().isEviction();
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2098) gfsh history should be stored in ~/.geode
Anthony Baker created GEODE-2098:
Summary: gfsh history should be stored in ~/.geode
Key: GEODE-2098
URL: https://issues.apache.org/jira/browse/GEODE-2098
Project: Geode
Issue Type: Improvement
Components: gfsh
Reporter: Anthony Baker
Currently gfsh stores history in the ~/.gemfire directory. We should change
that to be ~/.geode.
{code}
private static String getHomeGemFireDirectory() {
String userHome = System.getProperty("user.home");
String homeDirPath = userHome + "/.gemfire";
File alternateDir = new File(homeDirPath);
if (!alternateDir.exists()) {
if (!alternateDir.mkdirs()) {
homeDirPath = ".";
}
}
return homeDirPath;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2099) Race condition in ConnectToLocatorSSLDUnitTest
Jinmei Liao created GEODE-2099: -- Summary: Race condition in ConnectToLocatorSSLDUnitTest Key: GEODE-2099 URL: https://issues.apache.org/jira/browse/GEODE-2099 Project: Geode Issue Type: Bug Components: management, tests Reporter: Jinmei Liao Fix For: 1.1.0-incubating This test contains 3 tests, if put a long enough wait or a break point in between the tests, the tests would pass, otherwise the last two tests would fail. Need to get to the bottom of this. For the last tests are ignored. This is happening after we have to put "disconnect" after each connect to properly close the jmx thread so that it wouldn't pollute other tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2094) Update admin/dev REST API documentation
[ https://issues.apache.org/jira/browse/GEODE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658438#comment-15658438 ] ASF subversion and git services commented on GEODE-2094: Commit 3db9b309740ff10a7bc0bc6c4ad9bcea3124f29a in incubator-geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3db9b30 ] GEODE-2094 Update admin/dev REST API documentation - Add 3 missing gfsh start server options: --http-service-port --http-service-bind-address --start-rest-api - Update examples to use these options, instead of using the older --J=-gemfire. property specification. > Update admin/dev REST API documentation > --- > > Key: GEODE-2094 > URL: https://issues.apache.org/jira/browse/GEODE-2094 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > These 3 options for the gfsh start server command are not documented, so also > add them to the command reference page: > --http-service-port > --http-service-bind-address > --start-rest-api > The commands to start a server can be simplified in the prose on using gfsh > with REST commands. > 1. In the docs file > geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb, about using > the admin REST interface, the sample gfsh start server command can be > simplified. > --J=-Dgemfire.http-service-port=8080 > becomes > --http-service-port=8080 > --J=-Dgemfire.http-service-bind-address=myremotecluster.example.com > becomes > --http-service-bind-address=myremotecluster.example.com > 2. In the docs file geode-docs/rest_apps/setup_config.html.md.erb, about > using the dev REST API, the gfsh start server commands given in steps 2 and 3 > can be simplified (corrected). > --J=-Dgemfire.start-dev-rest-api=true > becomes > --start-rest-api=true > --J=-Dgemfire.http-service-port=8080 > becomes > --http-service-port=8080 > --J=-Dgemfire.http-service-bind-address=localhost > becomes > --http-service-bind-address=localhost -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2094) Update admin/dev REST API documentation
[ https://issues.apache.org/jira/browse/GEODE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2094: --- Fix Version/s: 1.1.0-incubating > Update admin/dev REST API documentation > --- > > Key: GEODE-2094 > URL: https://issues.apache.org/jira/browse/GEODE-2094 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > These 3 options for the gfsh start server command are not documented, so also > add them to the command reference page: > --http-service-port > --http-service-bind-address > --start-rest-api > The commands to start a server can be simplified in the prose on using gfsh > with REST commands. > 1. In the docs file > geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb, about using > the admin REST interface, the sample gfsh start server command can be > simplified. > --J=-Dgemfire.http-service-port=8080 > becomes > --http-service-port=8080 > --J=-Dgemfire.http-service-bind-address=myremotecluster.example.com > becomes > --http-service-bind-address=myremotecluster.example.com > 2. In the docs file geode-docs/rest_apps/setup_config.html.md.erb, about > using the dev REST API, the gfsh start server commands given in steps 2 and 3 > can be simplified (corrected). > --J=-Dgemfire.start-dev-rest-api=true > becomes > --start-rest-api=true > --J=-Dgemfire.http-service-port=8080 > becomes > --http-service-port=8080 > --J=-Dgemfire.http-service-bind-address=localhost > becomes > --http-service-bind-address=localhost -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2094) Update admin/dev REST API documentation
[ https://issues.apache.org/jira/browse/GEODE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2094. Resolution: Fixed > Update admin/dev REST API documentation > --- > > Key: GEODE-2094 > URL: https://issues.apache.org/jira/browse/GEODE-2094 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > These 3 options for the gfsh start server command are not documented, so also > add them to the command reference page: > --http-service-port > --http-service-bind-address > --start-rest-api > The commands to start a server can be simplified in the prose on using gfsh > with REST commands. > 1. In the docs file > geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb, about using > the admin REST interface, the sample gfsh start server command can be > simplified. > --J=-Dgemfire.http-service-port=8080 > becomes > --http-service-port=8080 > --J=-Dgemfire.http-service-bind-address=myremotecluster.example.com > becomes > --http-service-bind-address=myremotecluster.example.com > 2. In the docs file geode-docs/rest_apps/setup_config.html.md.erb, about > using the dev REST API, the gfsh start server commands given in steps 2 and 3 > can be simplified (corrected). > --J=-Dgemfire.start-dev-rest-api=true > becomes > --start-rest-api=true > --J=-Dgemfire.http-service-port=8080 > becomes > --http-service-port=8080 > --J=-Dgemfire.http-service-bind-address=localhost > becomes > --http-service-bind-address=localhost -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2100) Add new version of query client server messages
Jason Huynh created GEODE-2100: -- Summary: Add new version of query client server messages Key: GEODE-2100 URL: https://issues.apache.org/jira/browse/GEODE-2100 Project: Geode Issue Type: Bug Components: querying Reporter: Jason Huynh Fix For: 1.1.0-incubating Create new message types that properly handle legacy clients compared to newer clients -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2100) Add new version of query client server messages
[ https://issues.apache.org/jira/browse/GEODE-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh reassigned GEODE-2100: -- Assignee: Jason Huynh > Add new version of query client server messages > --- > > Key: GEODE-2100 > URL: https://issues.apache.org/jira/browse/GEODE-2100 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > Fix For: 1.1.0-incubating > > > Create new message types that properly handle legacy clients compared to > newer clients -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2101) Improve WAN topology terminology in docs
Karen Smoler Miller created GEODE-2101: -- Summary: Improve WAN topology terminology in docs Key: GEODE-2101 URL: https://issues.apache.org/jira/browse/GEODE-2101 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller In our documentation description of WAN topologies, the term "parallel multi-site topology" is a fully connected mesh. The "serial multi-site topology" is a ring. It will improve the docs to change our descriptions to use the common and accepted terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1740) Potential region inconsistency with concurrent region operation during transaction commit processing
[ https://issues.apache.org/jira/browse/GEODE-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658605#comment-15658605 ] ASF GitHub Bot commented on GEODE-1740: --- GitHub user gemzdude opened a pull request: https://github.com/apache/incubator-geode/pull/282 GEODE-1740: Inconsistencies with concurrent clear and commit There is a possible region inconsistency if region operations such as CLEAR are performed during transaction commit processing. Commit processing has been modified to acquire and hold a read on each region involved in a transaction for the duration of commit processing. This prevents clear from being able to acquire a write lock until commit processing is complete. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gemzdude/incubator-geode feature/GEODE-1740 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-geode/pull/282.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #282 commit deab93b8e72f6bb1248a19bdb4a993d0ef980718 Author: Scott Jewell Date: 2016-11-02T22:59:35Z GEODE-1740: Correct potential region inconsistencies with concurrent clear and transaction commit > Potential region inconsistency with concurrent region operation during > transaction commit processing > > > Key: GEODE-1740 > URL: https://issues.apache.org/jira/browse/GEODE-1740 > Project: Geode > Issue Type: Bug > Components: regions, transactions >Reporter: Scott Jewell > > There is a possible region inconsistency if region operations such as CLEAR > are performed during transaction commit processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1740) Potential region inconsistency with concurrent region operation during transaction commit processing
[ https://issues.apache.org/jira/browse/GEODE-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658628#comment-15658628 ] ASF GitHub Bot commented on GEODE-1740: --- Github user gemzdude commented on the issue: https://github.com/apache/incubator-geode/pull/282 Spotless check has been applied > Potential region inconsistency with concurrent region operation during > transaction commit processing > > > Key: GEODE-1740 > URL: https://issues.apache.org/jira/browse/GEODE-1740 > Project: Geode > Issue Type: Bug > Components: regions, transactions >Reporter: Scott Jewell > > There is a possible region inconsistency if region operations such as CLEAR > are performed during transaction commit processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2101) Improve WAN topology terminology in docs
[ https://issues.apache.org/jira/browse/GEODE-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2101: -- Assignee: Karen Smoler Miller > Improve WAN topology terminology in docs > > > Key: GEODE-2101 > URL: https://issues.apache.org/jira/browse/GEODE-2101 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > > In our documentation description of WAN topologies, the term "parallel > multi-site topology" is a fully connected mesh. The "serial multi-site > topology" is a ring. It will improve the docs to change our descriptions to > use the common and accepted terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2101) Improve WAN topology terminology in docs
[ https://issues.apache.org/jira/browse/GEODE-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2101: --- Priority: Minor (was: Major) > Improve WAN topology terminology in docs > > > Key: GEODE-2101 > URL: https://issues.apache.org/jira/browse/GEODE-2101 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Priority: Minor > > In our documentation description of WAN topologies, the term "parallel > multi-site topology" is a fully connected mesh. The "serial multi-site > topology" is a ring. It will improve the docs to change our descriptions to > use the common and accepted terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
