[jira] [Created] (GEODE-2119) gfsh user and password visible in clear text
Karen Smoler Miller created GEODE-2119: -- Summary: gfsh user and password visible in clear text Key: GEODE-2119 URL: https://issues.apache.org/jira/browse/GEODE-2119 Project: Geode Issue Type: Bug Components: gfsh Reporter: Karen Smoler Miller Both gfsh connect and gfsh start server allow the specification on the command line of a user name and a password for use as credentials in authentication. Clear text versions of the user name and password are then visible 1. if the user runs gfsh history 2. in historyfile, if the user runs gfsh history --file=historyfile 3. in the output of ps It would be worth a check to see if clear text versions of the user or password end up in any locator or server logs. I don't believe it does for gfsh connect, but it might for the start server case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2114) Add user and password to gfsh connect docs
[ https://issues.apache.org/jira/browse/GEODE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2114. Resolution: Fixed > Add user and password to gfsh connect docs > -- > > Key: GEODE-2114 > URL: https://issues.apache.org/jira/browse/GEODE-2114 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The gfsh connect command has --user and --password options that are not > completely documented. The task here is to complete that documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2114) Add user and password to gfsh connect docs
[ https://issues.apache.org/jira/browse/GEODE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2114: --- Fix Version/s: 1.1.0-incubating > Add user and password to gfsh connect docs > -- > > Key: GEODE-2114 > URL: https://issues.apache.org/jira/browse/GEODE-2114 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The gfsh connect command has --user and --password options that are not > completely documented. The task here is to complete that documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller reopened GEODE-2098:
Assignee: Karen Smoler Miller (was: Avinash Dongre)
Reopening this ticket, as there's a small documentation task associated with
the change. I'll take care of the documentation change. The gfsh history
command reference page ought to say the history file goes into the .geode
directory, and it currently says that the file goes into the home directory.
> 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: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> 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] [Commented] (GEODE-2114) Add user and password to gfsh connect docs
[ https://issues.apache.org/jira/browse/GEODE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668973#comment-15668973 ] Karen Smoler Miller commented on GEODE-2114: Note that a gfsh history --file=historyfilename after using doing a gfsh connect that specifies user and password will write the command with user name and password in clear text to the history file. So, I added prose that notes that the password is clear text and may be visible to others. > Add user and password to gfsh connect docs > -- > > Key: GEODE-2114 > URL: https://issues.apache.org/jira/browse/GEODE-2114 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Karen Smoler Miller > > The gfsh connect command has --user and --password options that are not > completely documented. The task here is to complete that documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2114) Add user and password to gfsh connect docs
Karen Smoler Miller created GEODE-2114: -- Summary: Add user and password to gfsh connect docs Key: GEODE-2114 URL: https://issues.apache.org/jira/browse/GEODE-2114 Project: Geode Issue Type: Task Components: docs Reporter: Karen Smoler Miller The gfsh connect command has --user and --password options that are not completely documented. The task here is to complete that documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2110. Resolution: Fixed > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reopened GEODE-2110: Reopening this story to add a note that a user that specifies the password on the command line is specifying their password in the clear. > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2110. Resolution: Fixed Fix Version/s: 1.1.0-incubating > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1896) unable to specify a PartitionResolver in gfsh
[
https://issues.apache.org/jira/browse/GEODE-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-1896:
---
Component/s: docs
> unable to specify a PartitionResolver in gfsh
> -
>
> Key: GEODE-1896
> URL: https://issues.apache.org/jira/browse/GEODE-1896
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Avinash Dongre
> Fix For: 1.1.0-incubating
>
>
> While creating a region in gfsh, users should be able to provide a
> PartitionResolver, something like:
> {noformat}
> gfsh>create region --name=myRegion --type=PARTITION
> --partition-resolver=com.mycompany.MyCustomPartitionResolver
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2110: -- Assignee: Karen Smoler Miller > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2110) Add user and password to gfsh start server docs
Karen Smoler Miller created GEODE-2110: -- Summary: Add user and password to gfsh start server docs Key: GEODE-2110 URL: https://issues.apache.org/jira/browse/GEODE-2110 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller Options to the gfsh start server command specify the user and password to use as credentials in authentication. These options are nicely printed in the gfsh help option, but they did not make it into the command reference page for the gfsh start server command. Thus, they need to be added. >From the help output: user User name to securely connect to the cluster. If the --password parameter is not specified then it will be prompted for. Required: false password Password to securely connect to the cluster. Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (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 resolved GEODE-2101. Resolution: Fixed Fix Version/s: 1.1.0-incubating > 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 > Fix For: 1.1.0-incubating > > > 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] [Assigned] (GEODE-2105) Remove documentation of Log Collection Utility
[ https://issues.apache.org/jira/browse/GEODE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2105: -- Assignee: Karen Smoler Miller > Remove documentation of Log Collection Utility > -- > > Key: GEODE-2105 > URL: https://issues.apache.org/jira/browse/GEODE-2105 > Project: Geode > Issue Type: Task >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The log collection utility is not part of Geode releases, so remove it from > the documentation. > https://issues.apache.org/jira/browse/GEODE-79 and the feature/GEODE-79 > branch has the code for the Log Collection Utility, but exists from a time > when the Geode docs were not yet donated to the ASF. The existing > documentation in file log_collection_utility.html.md.erb will be placed onto > that branch so it is not lost. No testing or checks will be done on the > feature/GEODE-79 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2105) Remove documentation of Log Collection Utility
[ https://issues.apache.org/jira/browse/GEODE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2105. Resolution: Fixed Fix Version/s: 1.1.0-incubating > Remove documentation of Log Collection Utility > -- > > Key: GEODE-2105 > URL: https://issues.apache.org/jira/browse/GEODE-2105 > Project: Geode > Issue Type: Task >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The log collection utility is not part of Geode releases, so remove it from > the documentation. > https://issues.apache.org/jira/browse/GEODE-79 and the feature/GEODE-79 > branch has the code for the Log Collection Utility, but exists from a time > when the Geode docs were not yet donated to the ASF. The existing > documentation in file log_collection_utility.html.md.erb will be placed onto > that branch so it is not lost. No testing or checks will be done on the > feature/GEODE-79 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2105) Remove documentation of Log Collection Utility
Karen Smoler Miller created GEODE-2105: -- Summary: Remove documentation of Log Collection Utility Key: GEODE-2105 URL: https://issues.apache.org/jira/browse/GEODE-2105 Project: Geode Issue Type: Task Reporter: Karen Smoler Miller The log collection utility is not part of Geode releases, so remove it from the documentation. https://issues.apache.org/jira/browse/GEODE-79 and the feature/GEODE-79 branch has the code for the Log Collection Utility, but exists from a time when the Geode docs were not yet donated to the ASF. The existing documentation in file log_collection_utility.html.md.erb will be placed onto that branch so it is not lost. No testing or checks will be done on the feature/GEODE-79 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2098:
---
Component/s: docs
> 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: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Avinash Dongre
>
> 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] [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)
[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] [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] [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] [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] [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: --- Description: 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 was: 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 > 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 > > 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] [Assigned] (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 reassigned GEODE-2094: -- Assignee: Karen Smoler Miller > 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] [Created] (GEODE-2094) Update admin/dev REST API documentation
Karen Smoler Miller created GEODE-2094: -- Summary: 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 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 --J=-Dgemfire.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-2090) Update off-heap statistics documentation
[
https://issues.apache.org/jira/browse/GEODE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-2090.
Resolution: Fixed
> Update off-heap statistics documentation
>
>
> Key: GEODE-2090
> URL: https://issues.apache.org/jira/browse/GEODE-2090
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The {{gfsh show metrics}} command reference page is missing the optional
> {{--category=offheap}} option.
> Also, verify if the statistic {{compactions}} ought to be called
> {{defragmentations}}. If so, fix the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2090) Update off-heap statistics documentation
[
https://issues.apache.org/jira/browse/GEODE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2090:
---
Fix Version/s: 1.1.0-incubating
> Update off-heap statistics documentation
>
>
> Key: GEODE-2090
> URL: https://issues.apache.org/jira/browse/GEODE-2090
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The {{gfsh show metrics}} command reference page is missing the optional
> {{--category=offheap}} option.
> Also, verify if the statistic {{compactions}} ought to be called
> {{defragmentations}}. If so, fix the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1530) geode-examples setEnv.sh script needs to export path
[
https://issues.apache.org/jira/browse/GEODE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-1530.
Resolution: Fixed
> geode-examples setEnv.sh script needs to export path
>
>
> Key: GEODE-1530
> URL: https://issues.apache.org/jira/browse/GEODE-1530
> Project: Geode
> Issue Type: Bug
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Labels: bug-hunt
>
> Work currently on the feature/GEODE-33 branch.
> In the replicated example, the {{scripts/setEnv.sh}} script should to prepend
> the {{GEODE_HOME}} environment variable it finds to the PATH, so that the
> {{startAll.sh}} uses that path.
> Append this line to the {{scripts/setEnv.sh}} script:
> {{export PATH=$GEODE_HOME/bin:$PATH}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1531) geode-examples: add final step to run stop script
[
https://issues.apache.org/jira/browse/GEODE-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-1531.
Resolution: Fixed
> geode-examples: add final step to run stop script
> --
>
> Key: GEODE-1531
> URL: https://issues.apache.org/jira/browse/GEODE-1531
> Project: Geode
> Issue Type: Bug
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Labels: bug-hunt
>
> {{replicated/README.md}} steps 1-5 of the replicated example in
> geode-examples on the feature/GEODE-33 branch are fine. (Well, step 4 to
> kill a *server* needs to be specified.)
> A Step 6 needs to be added to the {{replicated/README.md}} file to run
> {{$ scripts/stopAll.sh}}
> Without this, novice users will not realize that they still have servers and
> a locator running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1523) geode-examples README.md markdown improvement
[
https://issues.apache.org/jira/browse/GEODE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-1523.
Resolution: Fixed
> geode-examples README.md markdown improvement
> -
>
> Key: GEODE-1523
> URL: https://issues.apache.org/jira/browse/GEODE-1523
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Labels: bug-hunt
>
> The markdown in the feature/GEODE-33 branch file {{geode-examples/README.md}}
> is not yet right.
> There are problems with the references and with the bulleted list.
> (A separate ticket will address the content of the file. This ticket is only
> to fix the markdown, so it displays correctly.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2090) Update off-heap statistics documentation
[
https://issues.apache.org/jira/browse/GEODE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2090:
---
Description:
The {{gfsh show metrics}} command reference page is missing the optional
{{--category=offheap}} option.
Also, verify if the statistic {{compactions}} ought to be called
{{defragmentations}}. If so, fix the error.
was:
The {{gfsh show metrics}} command reference page is missing the optional
{{--category=offheap}} option.
Also, verify if the statistic {{compactionTime}} is incorrectly called
{{defragmentationTime}}. If so, fix the error.
> Update off-heap statistics documentation
>
>
> Key: GEODE-2090
> URL: https://issues.apache.org/jira/browse/GEODE-2090
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>
> The {{gfsh show metrics}} command reference page is missing the optional
> {{--category=offheap}} option.
> Also, verify if the statistic {{compactions}} ought to be called
> {{defragmentations}}. If so, fix the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2090) Update off-heap statistics documentation
[
https://issues.apache.org/jira/browse/GEODE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller reassigned GEODE-2090:
--
Assignee: Karen Smoler Miller
> Update off-heap statistics documentation
>
>
> Key: GEODE-2090
> URL: https://issues.apache.org/jira/browse/GEODE-2090
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>
> The {{gfsh show metrics}} command reference page is missing the optional
> {{--category=offheap}} option.
> Also, verify if the statistic {{compactionTime}} is incorrectly called
> {{defragmentationTime}}. If so, fix the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2090) Update off-heap statistics documentation
Karen Smoler Miller created GEODE-2090:
--
Summary: Update off-heap statistics documentation
Key: GEODE-2090
URL: https://issues.apache.org/jira/browse/GEODE-2090
Project: Geode
Issue Type: Bug
Components: docs
Reporter: Karen Smoler Miller
The {{gfsh show metrics}} command reference page is missing the optional
{{--category=offheap}} option.
Also, verify if the statistic {{compactionTime}} is incorrectly called
{{defragmentationTime}}. If so, fix the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2070) Improve documentation of region management
[ https://issues.apache.org/jira/browse/GEODE-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2070. Resolution: Fixed > Improve documentation of region management > -- > > Key: GEODE-2070 > URL: https://issues.apache.org/jira/browse/GEODE-2070 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The outline and navigation of the material on regions is > Basic Configuration and Programming > Data Regions > Data Region Management > Creating a Region with gfsh > Creating a Region Through the cache.xml File > Creating a Region Through the API > ... > The information in the 3 'Creating' sections is partially covered in the > Data Region Management section. Reorganize and collapse into a single > section on management that covers region management the 3 ways: > 1. APIs > 2. cache.xml declaration > 3. gfsh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2070) Improve documentation of region management
[ https://issues.apache.org/jira/browse/GEODE-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2070: --- Fix Version/s: 1.1.0-incubating > Improve documentation of region management > -- > > Key: GEODE-2070 > URL: https://issues.apache.org/jira/browse/GEODE-2070 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The outline and navigation of the material on regions is > Basic Configuration and Programming > Data Regions > Data Region Management > Creating a Region with gfsh > Creating a Region Through the cache.xml File > Creating a Region Through the API > ... > The information in the 3 'Creating' sections is partially covered in the > Data Region Management section. Reorganize and collapse into a single > section on management that covers region management the 3 ways: > 1. APIs > 2. cache.xml declaration > 3. gfsh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2068) Improve documentation on serial/parallel gateway senders
[ https://issues.apache.org/jira/browse/GEODE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2068. Resolution: Fixed > Improve documentation on serial/parallel gateway senders > > > Key: GEODE-2068 > URL: https://issues.apache.org/jira/browse/GEODE-2068 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The documentation on Serial Gateway Senders implies that the events queued > are generated from a single server. Not true. The events generated from a > cluster are funneled through a single server. > For the material on Parallel Gateway Senders, the terminology "simultaneous" > implies timing, and we don't coordinate the timing of when events are sent. > What we're doing is to identify that an event is sent from the server that > hosts the primary bucket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2068) Improve documentation on serial/parallel gateway senders
[ https://issues.apache.org/jira/browse/GEODE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2068: --- Fix Version/s: 1.1.0-incubating > Improve documentation on serial/parallel gateway senders > > > Key: GEODE-2068 > URL: https://issues.apache.org/jira/browse/GEODE-2068 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The documentation on Serial Gateway Senders implies that the events queued > are generated from a single server. Not true. The events generated from a > cluster are funneled through a single server. > For the material on Parallel Gateway Senders, the terminology "simultaneous" > implies timing, and we don't coordinate the timing of when events are sent. > What we're doing is to identify that an event is sent from the server that > hosts the primary bucket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2070) Improve documentation of region management
[ https://issues.apache.org/jira/browse/GEODE-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2070: -- Assignee: Karen Smoler Miller > Improve documentation of region management > -- > > Key: GEODE-2070 > URL: https://issues.apache.org/jira/browse/GEODE-2070 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > The outline and navigation of the material on regions is > Basic Configuration and Programming > Data Regions > Data Region Management > Creating a Region with gfsh > Creating a Region Through the cache.xml File > Creating a Region Through the API > ... > The information in the 3 'Creating' sections is partially covered in the > Data Region Management section. Reorganize and collapse into a single > section on management that covers region management the 3 ways: > 1. APIs > 2. cache.xml declaration > 3. gfsh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2070) Improve documentation of region management
Karen Smoler Miller created GEODE-2070: -- Summary: Improve documentation of region management Key: GEODE-2070 URL: https://issues.apache.org/jira/browse/GEODE-2070 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller The outline and navigation of the material on regions is Basic Configuration and Programming Data Regions Data Region Management Creating a Region with gfsh Creating a Region Through the cache.xml File Creating a Region Through the API ... The information in the 3 'Creating' sections is partially covered in the Data Region Management section. Reorganize and collapse into a single section on management that covers region management the 3 ways: 1. APIs 2. cache.xml declaration 3. gfsh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2017) Removal of nonSingleHopsCount stat in client
[ https://issues.apache.org/jira/browse/GEODE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2017: --- Component/s: docs > Removal of nonSingleHopsCount stat in client > > > Key: GEODE-2017 > URL: https://issues.apache.org/jira/browse/GEODE-2017 > Project: Geode > Issue Type: Bug > Components: client/server, docs, native client >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer > > Currently, the nonSingleHopsCount stat in the client is defined as "Total > number of times client request observed more than one hop during operation." > From this definition, this stat should track every time a client operation > requires more than one hop. Currently, this stat is only incremented when > "singleHop" is enabled on the pool. If this is correct then > metaDataRefreshCount will track the same metric, as the client will > automatically refresh when more than one hop is required for a prSingleHop > enabled pool. > If the nonSingleHopsCount metric where to track every non-one hop operation, > regardless of the "singleHop" flag on the pool, then the implementation of > this stat would need to change. > Otherwise we remove this stat and only track all nonSingleHop operation with > the metaDataRefresh count. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (GEODE-2068) Improve documentation on serial/parallel gateway senders
[ https://issues.apache.org/jira/browse/GEODE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2068: --- Comment: was deleted (was: While making changes, I intend to fix the subnav as well. There appear to be problems with the use of html anchors.) > Improve documentation on serial/parallel gateway senders > > > Key: GEODE-2068 > URL: https://issues.apache.org/jira/browse/GEODE-2068 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > The documentation on Serial Gateway Senders implies that the events queued > are generated from a single server. Not true. The events generated from a > cluster are funneled through a single server. > For the material on Parallel Gateway Senders, the terminology "simultaneous" > implies timing, and we don't coordinate the timing of when events are sent. > What we're doing is to identify that an event is sent from the server that > hosts the primary bucket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2068) Improve documentation on serial/parallel gateway senders
[ https://issues.apache.org/jira/browse/GEODE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634484#comment-15634484 ] Karen Smoler Miller commented on GEODE-2068: While making changes, I intend to fix the subnav as well. There appear to be problems with the use of html anchors. > Improve documentation on serial/parallel gateway senders > > > Key: GEODE-2068 > URL: https://issues.apache.org/jira/browse/GEODE-2068 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > The documentation on Serial Gateway Senders implies that the events queued > are generated from a single server. Not true. The events generated from a > cluster are funneled through a single server. > For the material on Parallel Gateway Senders, the terminology "simultaneous" > implies timing, and we don't coordinate the timing of when events are sent. > What we're doing is to identify that an event is sent from the server that > hosts the primary bucket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2068) Improve documentation on serial/parallel gateway senders
[ https://issues.apache.org/jira/browse/GEODE-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2068: -- Assignee: Karen Smoler Miller > Improve documentation on serial/parallel gateway senders > > > Key: GEODE-2068 > URL: https://issues.apache.org/jira/browse/GEODE-2068 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > The documentation on Serial Gateway Senders implies that the events queued > are generated from a single server. Not true. The events generated from a > cluster are funneled through a single server. > For the material on Parallel Gateway Senders, the terminology "simultaneous" > implies timing, and we don't coordinate the timing of when events are sent. > What we're doing is to identify that an event is sent from the server that > hosts the primary bucket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2068) Improve documentation on serial/parallel gateway senders
Karen Smoler Miller created GEODE-2068: -- Summary: Improve documentation on serial/parallel gateway senders Key: GEODE-2068 URL: https://issues.apache.org/jira/browse/GEODE-2068 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller The documentation on Serial Gateway Senders implies that the events queued are generated from a single server. Not true. The events generated from a cluster are funneled through a single server. For the material on Parallel Gateway Senders, the terminology "simultaneous" implies timing, and we don't coordinate the timing of when events are sent. What we're doing is to identify that an event is sent from the server that hosts the primary bucket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2047) Document change to enable-network-partition-detection
[ https://issues.apache.org/jira/browse/GEODE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2047. Resolution: Fixed Fix Version/s: (was: 1.0.0-incubating) > Document change to enable-network-partition-detection > - > > Key: GEODE-2047 > URL: https://issues.apache.org/jira/browse/GEODE-2047 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > This subtask is to change the documentation to reflect the code change that > went into GEODE-762. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2047) Document change to enable-network-partition-detection
[ https://issues.apache.org/jira/browse/GEODE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2047: --- Fix Version/s: 1.1.0-incubating > Document change to enable-network-partition-detection > - > > Key: GEODE-2047 > URL: https://issues.apache.org/jira/browse/GEODE-2047 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating, 1.1.0-incubating > > > This subtask is to change the documentation to reflect the code change that > went into GEODE-762. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2065) Document defragmentationsInProgress statistic
[ https://issues.apache.org/jira/browse/GEODE-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2065. Resolution: Fixed > Document defragmentationsInProgress statistic > - > > Key: GEODE-2065 > URL: https://issues.apache.org/jira/browse/GEODE-2065 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating > > > This is a sub-task of GEODE-1590. > Add the offheap memory statistic defragmentationsInProgress to the > documentation. It is the integer number of defragmentations currently in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2060) Update docs for security-related properties
[
https://issues.apache.org/jira/browse/GEODE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2060:
---
Fix Version/s: 1.1.0-incubating
> Update docs for security-related properties
> ---
>
> Key: GEODE-2060
> URL: https://issues.apache.org/jira/browse/GEODE-2060
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> Place {{security-manager}} and {{security-post-processor}} properties into
> the list of properties within the reference section of the documentation.
> Also review other security-related properties listed and identify those that
> are deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2060) Update docs for security-related properties
[
https://issues.apache.org/jira/browse/GEODE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-2060.
Resolution: Fixed
> Update docs for security-related properties
> ---
>
> Key: GEODE-2060
> URL: https://issues.apache.org/jira/browse/GEODE-2060
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> Place {{security-manager}} and {{security-post-processor}} properties into
> the list of properties within the reference section of the documentation.
> Also review other security-related properties listed and identify those that
> are deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2065) Document defragmentationsInProgress statistic
[ https://issues.apache.org/jira/browse/GEODE-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2065: -- Assignee: Karen Smoler Miller > Document defragmentationsInProgress statistic > - > > Key: GEODE-2065 > URL: https://issues.apache.org/jira/browse/GEODE-2065 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating > > > This is a sub-task of GEODE-1590. > Add the offheap memory statistic defragmentationsInProgress to the > documentation. It is the integer number of defragmentations currently in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2065) Document defragmentationsInProgress statistic
Karen Smoler Miller created GEODE-2065: -- Summary: Document defragmentationsInProgress statistic Key: GEODE-2065 URL: https://issues.apache.org/jira/browse/GEODE-2065 Project: Geode Issue Type: Sub-task Components: docs Reporter: Karen Smoler Miller This is a sub-task of GEODE-1590. Add the offheap memory statistic defragmentationsInProgress to the documentation. It is the integer number of defragmentations currently in progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2060) Update docs for security-related properties
[
https://issues.apache.org/jira/browse/GEODE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller reassigned GEODE-2060:
--
Assignee: Karen Smoler Miller
> Update docs for security-related properties
> ---
>
> Key: GEODE-2060
> URL: https://issues.apache.org/jira/browse/GEODE-2060
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>
> Place {{security-manager}} and {{security-post-processor}} properties into
> the list of properties within the reference section of the documentation.
> Also review other security-related properties listed and identify those that
> are deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2060) Update docs for security-related properties
[
https://issues.apache.org/jira/browse/GEODE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-2060:
---
Issue Type: Improvement (was: Bug)
> Update docs for security-related properties
> ---
>
> Key: GEODE-2060
> URL: https://issues.apache.org/jira/browse/GEODE-2060
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>
> Place {{security-manager}} and {{security-post-processor}} properties into
> the list of properties within the reference section of the documentation.
> Also review other security-related properties listed and identify those that
> are deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2060) Update docs for security-related properties
Karen Smoler Miller created GEODE-2060:
--
Summary: Update docs for security-related properties
Key: GEODE-2060
URL: https://issues.apache.org/jira/browse/GEODE-2060
Project: Geode
Issue Type: Bug
Components: docs
Reporter: Karen Smoler Miller
Place {{security-manager}} and {{security-post-processor}} properties into the
list of properties within the reference section of the documentation.
Also review other security-related properties listed and identify those that
are deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2050) Update documentation of statistics
[ https://issues.apache.org/jira/browse/GEODE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2050. Resolution: Fixed > Update documentation of statistics > -- > > Key: GEODE-2050 > URL: https://issues.apache.org/jira/browse/GEODE-2050 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > With JGroups 3.6.10, a set of statistics have been removed. They need to be > removed from the documentation: > - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying > messages for batched transmission", "nanoseconds"), > - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing > batched messages to the network", "nanoseconds"), > - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, > prior to sending a multicast message", "flushes"), > - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for > acknowledgements for outstanding unicast datagram messages", "nanoseconds"), > - "flowControlRequests", "Total number of flow control credit requests sent > to other processes", "messages"), > - "flowControlResponses", "Total number of flow control credit responses sent > to a requestor", "messages"), > "flowControlWaitsInProgress", "Number of threads blocked waiting for > flow-control recharges from other processes", "threads"), > - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting > for other processes to recharge the flow of control meter", "nanoseconds"), > - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting > due to flow-control throttle requests from other members", "threads"), > - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability > in NAKACK", "messages"), > - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in > NAKACK", "messages"), > - "jgQueuedMessages", "Number of messages queued by transport and awaiting > processing", "messages"), *is not in the documentation* > - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt > of prior messages", "messages"), > - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", > "messages"), > - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority > messages", "messages"), > - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST > send", "nanoseconds"), > - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", > "nanoseconds"), > - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", > "messages"), > - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", > "messages"), > - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", > "messages"), > - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), > - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), > - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", > "nanoseconds"), > - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to > backpressure", "events"), > - "jgFCautoRequests", "Number of times JGroups FC automatically sent > replenishment requests", "events"), > - "jgFCreplenish", "Number of times JGroups FC received replenishments from > receivers", "messages"), > - "jgFCresumes", "Number of times JGroups FC resumed sends due to > backpressure", "events"), > - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", > "events"), > - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle > requests to a sender", "events"), > - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", > "events"), *is not in the documentation* > With the new membership service, these statistics have been added. Each has > a name, a description, and a unit of measure: > - "heartbeatRequestsSent", "Heartbeat request messages that this member has > sent.", "messages"), > - "heartbeatRequestsReceived", "Heartbeat request messages that this member > has received.", "messages"), > - "heartbeatsSent", "Heartbeat messages that this member has sent.", > "messages"), > - "heartbeatsReceived", "Heartbeat messages that this member has received.", > "messages"), > - "suspectsSent", "Suspect member messages that this member has sent.", > "messages"), > - "suspectsReceived", "Suspect member messages that this member has > received.", "messages"), > - "finalCheckRequestsSent", "Heartbeat request messages that this member has > sent.", "messages"), > - "finalCheckRequestsReceived", "Final check requests that this member has > received.","messages"), > - "finalCheckResponsesSe
[jira] [Updated] (GEODE-2050) Update documentation of statistics
[ https://issues.apache.org/jira/browse/GEODE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2050: --- Fix Version/s: 1.1.0-incubating > Update documentation of statistics > -- > > Key: GEODE-2050 > URL: https://issues.apache.org/jira/browse/GEODE-2050 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > With JGroups 3.6.10, a set of statistics have been removed. They need to be > removed from the documentation: > - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying > messages for batched transmission", "nanoseconds"), > - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing > batched messages to the network", "nanoseconds"), > - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, > prior to sending a multicast message", "flushes"), > - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for > acknowledgements for outstanding unicast datagram messages", "nanoseconds"), > - "flowControlRequests", "Total number of flow control credit requests sent > to other processes", "messages"), > - "flowControlResponses", "Total number of flow control credit responses sent > to a requestor", "messages"), > "flowControlWaitsInProgress", "Number of threads blocked waiting for > flow-control recharges from other processes", "threads"), > - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting > for other processes to recharge the flow of control meter", "nanoseconds"), > - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting > due to flow-control throttle requests from other members", "threads"), > - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability > in NAKACK", "messages"), > - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in > NAKACK", "messages"), > - "jgQueuedMessages", "Number of messages queued by transport and awaiting > processing", "messages"), *is not in the documentation* > - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt > of prior messages", "messages"), > - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", > "messages"), > - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority > messages", "messages"), > - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST > send", "nanoseconds"), > - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", > "nanoseconds"), > - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", > "messages"), > - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", > "messages"), > - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", > "messages"), > - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), > - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), > - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", > "nanoseconds"), > - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to > backpressure", "events"), > - "jgFCautoRequests", "Number of times JGroups FC automatically sent > replenishment requests", "events"), > - "jgFCreplenish", "Number of times JGroups FC received replenishments from > receivers", "messages"), > - "jgFCresumes", "Number of times JGroups FC resumed sends due to > backpressure", "events"), > - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", > "events"), > - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle > requests to a sender", "events"), > - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", > "events"), *is not in the documentation* > With the new membership service, these statistics have been added. Each has > a name, a description, and a unit of measure: > - "heartbeatRequestsSent", "Heartbeat request messages that this member has > sent.", "messages"), > - "heartbeatRequestsReceived", "Heartbeat request messages that this member > has received.", "messages"), > - "heartbeatsSent", "Heartbeat messages that this member has sent.", > "messages"), > - "heartbeatsReceived", "Heartbeat messages that this member has received.", > "messages"), > - "suspectsSent", "Suspect member messages that this member has sent.", > "messages"), > - "suspectsReceived", "Suspect member messages that this member has > received.", "messages"), > - "finalCheckRequestsSent", "Heartbeat request messages that this member has > sent.", "messages"), > - "finalCheckRequestsReceived", "Final check requests that this member has > received.","messages"), > - "finalChec
[jira] [Updated] (GEODE-2050) Update documentation of statistics
[ https://issues.apache.org/jira/browse/GEODE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2050: --- Description: With JGroups 3.6.10, a set of statistics have been removed. They need to be removed from the documentation: - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying messages for batched transmission", "nanoseconds"), - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing batched messages to the network", "nanoseconds"), - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, prior to sending a multicast message", "flushes"), - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for acknowledgements for outstanding unicast datagram messages", "nanoseconds"), - "flowControlRequests", "Total number of flow control credit requests sent to other processes", "messages"), - "flowControlResponses", "Total number of flow control credit responses sent to a requestor", "messages"), "flowControlWaitsInProgress", "Number of threads blocked waiting for flow-control recharges from other processes", "threads"), - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting for other processes to recharge the flow of control meter", "nanoseconds"), - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting due to flow-control throttle requests from other members", "threads"), - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability in NAKACK", "messages"), - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in NAKACK", "messages"), - "jgQueuedMessages", "Number of messages queued by transport and awaiting processing", "messages"), *is not in the documentation* - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt of prior messages", "messages"), - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", "messages"), - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority messages", "messages"), - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST send", "nanoseconds"), - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", "nanoseconds"), - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", "messages"), - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", "messages"), - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", "messages"), - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", "nanoseconds"), - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to backpressure", "events"), - "jgFCautoRequests", "Number of times JGroups FC automatically sent replenishment requests", "events"), - "jgFCreplenish", "Number of times JGroups FC received replenishments from receivers", "messages"), - "jgFCresumes", "Number of times JGroups FC resumed sends due to backpressure", "events"), - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", "events"), - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle requests to a sender", "events"), - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", "events"), *is not in the documentation* With the new membership service, these statistics have been added. Each has a name, a description, and a unit of measure: - "heartbeatRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "heartbeatRequestsReceived", "Heartbeat request messages that this member has received.", "messages"), - "heartbeatsSent", "Heartbeat messages that this member has sent.", "messages"), - "heartbeatsReceived", "Heartbeat messages that this member has received.", "messages"), - "suspectsSent", "Suspect member messages that this member has sent.", "messages"), - "suspectsReceived", "Suspect member messages that this member has received.", "messages"), - "finalCheckRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "finalCheckRequestsReceived", "Final check requests that this member has received.","messages"), - "finalCheckResponsesSent", "Final check responses that this member has sent.", "messages"), - "finalCheckResponsesReceived", "Final check responses that this member has received.","messages"), The above four stats are broken down into two other sets for TCP/IP vs UDP checks: - "tcpFinalCheckRequestsSent", "TCP final check requests that this member has sent.", "messages", false), - "tcpFinalCheckRequestsReceived", "TCP final check requests that this member has received.","messages", false), - "tcpFinalCheckResponsesSent", "TCP final check responses that this member has sen
[jira] [Updated] (GEODE-2050) Update documentation of statistics
[ https://issues.apache.org/jira/browse/GEODE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2050: --- Description: With JGroups 3.6.10, a set of statistics have been removed. They need to be removed from the documentation: - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying messages for batched transmission", "nanoseconds"), - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing batched messages to the network", "nanoseconds"), - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, prior to sending a multicast message", "flushes"), - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for acknowledgements for outstanding unicast datagram messages", "nanoseconds"), - "flowControlRequests", "Total number of flow control credit requests sent to other processes", "messages"), - "flowControlResponses", "Total number of flow control credit responses sent to a requestor", "messages"), "flowControlWaitsInProgress", "Number of threads blocked waiting for flow-control recharges from other processes", "threads"), - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting for other processes to recharge the flow of control meter", "nanoseconds"), - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting due to flow-control throttle requests from other members", "threads"), - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability in NAKACK", "messages"), - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in NAKACK", "messages"), - "jgQueuedMessages", "Number of messages queued by transport and awaiting processing", "messages"), *is not in the documentation* - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt of prior messages", "messages"), - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", "messages"), - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority messages", "messages"), - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST send", "nanoseconds"), - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", "nanoseconds"), - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", "messages"), - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", "messages"), - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", "messages"), - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", "nanoseconds"), - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to backpressure", "events"), - "jgFCautoRequests", "Number of times JGroups FC automatically sent replenishment requests", "events"), - "jgFCreplenish", "Number of times JGroups FC received replenishments from receivers", "messages"), - "jgFCresumes", "Number of times JGroups FC resumed sends due to backpressure", "events"), - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", "events"), - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle requests to a sender", "events"), - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", "events"), With the new membership service, these statistics have been added. Each has a name, a description, and a unit of measure: - "heartbeatRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "heartbeatRequestsReceived", "Heartbeat request messages that this member has received.", "messages"), - "heartbeatsSent", "Heartbeat messages that this member has sent.", "messages"), - "heartbeatsReceived", "Heartbeat messages that this member has received.", "messages"), - "suspectsSent", "Suspect member messages that this member has sent.", "messages"), - "suspectsReceived", "Suspect member messages that this member has received.", "messages"), - "finalCheckRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "finalCheckRequestsReceived", "Final check requests that this member has received.","messages"), - "finalCheckResponsesSent", "Final check responses that this member has sent.", "messages"), - "finalCheckResponsesReceived", "Final check responses that this member has received.","messages"), The above four stats are broken down into two other sets for TCP/IP vs UDP checks: - "tcpFinalCheckRequestsSent", "TCP final check requests that this member has sent.", "messages", false), - "tcpFinalCheckRequestsReceived", "TCP final check requests that this member has received.","messages", false), - "tcpFinalCheckResponsesSent", "TCP final check responses that this member has sent.","messages", false), - "tcp
[jira] [Updated] (GEODE-2050) Update documentation of statistics
[ https://issues.apache.org/jira/browse/GEODE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2050: --- Description: With JGroups 3.6.10, a set of statistics have been removed. They need to be removed from the documentation: - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying messages for batched transmission", "nanoseconds"), - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing batched messages to the network", "nanoseconds"), - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, prior to sending a multicast message", "flushes"), - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for acknowledgements for outstanding unicast datagram messages", "nanoseconds"), - "flowControlRequests", "Total number of flow control credit requests sent to other processes", "messages"), - "flowControlResponses", "Total number of flow control credit responses sent to a requestor", "messages"), "flowControlWaitsInProgress", "Number of threads blocked waiting for flow-control recharges from other processes", "threads"), - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting for other processes to recharge the flow of control meter", "nanoseconds"), - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting due to flow-control throttle requests from other members", "threads"), - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability in NAKACK", "messages"), - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in NAKACK", "messages"), - "jgQueuedMessages", "Number of messages queued by transport and awaiting processing", "messages"), * is not in the documentation * - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt of prior messages", "messages"), - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", "messages"), - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority messages", "messages"), - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST send", "nanoseconds"), - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", "nanoseconds"), - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", "messages"), - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", "messages"), - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", "messages"), - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", "nanoseconds"), - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to backpressure", "events"), - "jgFCautoRequests", "Number of times JGroups FC automatically sent replenishment requests", "events"), - "jgFCreplenish", "Number of times JGroups FC received replenishments from receivers", "messages"), - "jgFCresumes", "Number of times JGroups FC resumed sends due to backpressure", "events"), - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", "events"), - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle requests to a sender", "events"), - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", "events"), With the new membership service, these statistics have been added. Each has a name, a description, and a unit of measure: - "heartbeatRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "heartbeatRequestsReceived", "Heartbeat request messages that this member has received.", "messages"), - "heartbeatsSent", "Heartbeat messages that this member has sent.", "messages"), - "heartbeatsReceived", "Heartbeat messages that this member has received.", "messages"), - "suspectsSent", "Suspect member messages that this member has sent.", "messages"), - "suspectsReceived", "Suspect member messages that this member has received.", "messages"), - "finalCheckRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "finalCheckRequestsReceived", "Final check requests that this member has received.","messages"), - "finalCheckResponsesSent", "Final check responses that this member has sent.", "messages"), - "finalCheckResponsesReceived", "Final check responses that this member has received.","messages"), The above four stats are broken down into two other sets for TCP/IP vs UDP checks: - "tcpFinalCheckRequestsSent", "TCP final check requests that this member has sent.", "messages", false), - "tcpFinalCheckRequestsReceived", "TCP final check requests that this member has received.","messages", false), - "tcpFinalCheckResponsesSent", "TCP final check responses that this member has sent.","messages", false), - "t
[jira] [Assigned] (GEODE-2050) Update documentation of statistics
[ https://issues.apache.org/jira/browse/GEODE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2050: -- Assignee: Karen Smoler Miller > Update documentation of statistics > -- > > Key: GEODE-2050 > URL: https://issues.apache.org/jira/browse/GEODE-2050 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > With JGroups 3.6.10, a set of statistics have been removed. They need to be > removed from the documentation: > - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying > messages for batched transmission", "nanoseconds"), > - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing > batched messages to the network", "nanoseconds"), > - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, > prior to sending a multicast message", "flushes"), > - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for > acknowledgements for outstanding unicast datagram messages", "nanoseconds"), > - "flowControlRequests", "Total number of flow control credit requests sent > to other processes", "messages"), > - "flowControlResponses", "Total number of flow control credit responses sent > to a requestor", "messages"), > "flowControlWaitsInProgress", "Number of threads blocked waiting for > flow-control recharges from other processes", "threads"), > - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting > for other processes to recharge the flow of control meter", "nanoseconds"), > - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting > due to flow-control throttle requests from other members", "threads"), > - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability > in NAKACK", "messages"), > - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in > NAKACK", "messages"), > - "jgQueuedMessages", "Number of messages queued by transport and awaiting > processing", "messages"), > - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt > of prior messages", "messages"), > - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", > "messages"), > - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority > messages", "messages"), > - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST > send", "nanoseconds"), > - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", > "nanoseconds"), > - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", > "messages"), > - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", > "messages"), > - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", > "messages"), > - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), > - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), > - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", > "nanoseconds"), > - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to > backpressure", "events"), > - "jgFCautoRequests", "Number of times JGroups FC automatically sent > replenishment requests", "events"), > - "jgFCreplenish", "Number of times JGroups FC received replenishments from > receivers", "messages"), > - "jgFCresumes", "Number of times JGroups FC resumed sends due to > backpressure", "events"), > - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", > "events"), > - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle > requests to a sender", "events"), > - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", > "events"), > With the new membership service, these statistics have been added. Each has > a name, a description, and a unit of measure: > - "heartbeatRequestsSent", "Heartbeat request messages that this member has > sent.", "messages"), > - "heartbeatRequestsReceived", "Heartbeat request messages that this member > has received.", "messages"), > - "heartbeatsSent", "Heartbeat messages that this member has sent.", > "messages"), > - "heartbeatsReceived", "Heartbeat messages that this member has received.", > "messages"), > - "suspectsSent", "Suspect member messages that this member has sent.", > "messages"), > - "suspectsReceived", "Suspect member messages that this member has > received.", "messages"), > - "finalCheckRequestsSent", "Heartbeat request messages that this member has > sent.", "messages"), > - "finalCheckRequestsReceived", "Final check requests that this member has > received.","messages"), > - "finalCheckResponsesSent", "Final check responses that this member has > sent.", "messages"), > - "finalCh
[jira] [Created] (GEODE-2050) Update documentation of statistics
Karen Smoler Miller created GEODE-2050: -- Summary: Update documentation of statistics Key: GEODE-2050 URL: https://issues.apache.org/jira/browse/GEODE-2050 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller With JGroups 3.6.10, a set of statistics have been removed. They need to be removed from the documentation: - "batchCopyTime", "Total amount of time, in nanoseconds, spent copying messages for batched transmission", "nanoseconds"), - "batchFlushTime", "Total amount of time, in nanoseconds, spent flushing batched messages to the network", "nanoseconds"), - "ucastFlushes", "Total number of flushes of the unicast datagram protocol, prior to sending a multicast message", "flushes"), - "ucastFlushTime", "Total amount of time, in nanoseconds, spent waiting for acknowledgements for outstanding unicast datagram messages", "nanoseconds"), - "flowControlRequests", "Total number of flow control credit requests sent to other processes", "messages"), - "flowControlResponses", "Total number of flow control credit responses sent to a requestor", "messages"), "flowControlWaitsInProgress", "Number of threads blocked waiting for flow-control recharges from other processes", "threads"), - "flowControlWaitTime", "Total amount of time, in nanoseconds, spent waiting for other processes to recharge the flow of control meter", "nanoseconds"), - "flowControlThrottleWaitsInProgress", "Number of threads blocked waiting due to flow-control throttle requests from other members", "threads"), - "jgNAKACKreceivedMessages", "Number of received messages awaiting stability in NAKACK", "messages"), - "jgNAKACKsentMessages", "Number of sent messages awaiting stability in NAKACK", "messages"), - "jgQueuedMessages", "Number of messages queued by transport and awaiting processing", "messages"), - "jgUNICASTreceivedMessages", "Number of received messages awaiting receipt of prior messages", "messages"), - "jgUNICASTsentMessages", "Number of un-acked normal priority messages", "messages"), - "jgUNICASTsentHighPriorityMessages", "Number of un-acked high priority messages", "messages"), - "jgUNICASTdataReceivedTime", "Amount of time spent in JGroups UNICAST send", "nanoseconds"), - "jgSTABLEsuspendTime", "Amount of time JGroups STABLE is suspended", "nanoseconds"), - "jgSTABLEmessages", "Number of STABLE messages received by JGroups", "messages"), - "jgSTABLEmessagesSent", "Number of STABLE messages sent by JGroups", "messages"), - "jgSTABILITYmessages", "Number of STABILITY messages received by JGroups", "messages"), - "jgDownTime", "Down Time spent in JGroups stacks", "nanoseconds"), - "jgUpTime", "Up Time spent in JGroups stacks", "nanoseconds"), - "jChannelUpTime", "Up Time spent in JChannel including jgroup stack", "nanoseconds"), - "jgFCsendBlocks", "Number of times JGroups FC halted sends due to backpressure", "events"), - "jgFCautoRequests", "Number of times JGroups FC automatically sent replenishment requests", "events"), - "jgFCreplenish", "Number of times JGroups FC received replenishments from receivers", "messages"), - "jgFCresumes", "Number of times JGroups FC resumed sends due to backpressure", "events"), - "jgFCsentCredits", "Number of times JGroups FC sent credits to a sender", "events"), - "jgFCsentThrottleRequests","Number of times JGroups FC sent throttle requests to a sender", "events"), - "jgNAKACKwaits", "Number of delays created by NAKACK sent_msgs overflow", "events"), With the new membership service, these statistics have been added. Each has a name, a description, and a unit of measure: - "heartbeatRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "heartbeatRequestsReceived", "Heartbeat request messages that this member has received.", "messages"), - "heartbeatsSent", "Heartbeat messages that this member has sent.", "messages"), - "heartbeatsReceived", "Heartbeat messages that this member has received.", "messages"), - "suspectsSent", "Suspect member messages that this member has sent.", "messages"), - "suspectsReceived", "Suspect member messages that this member has received.", "messages"), - "finalCheckRequestsSent", "Heartbeat request messages that this member has sent.", "messages"), - "finalCheckRequestsReceived", "Final check requests that this member has received.","messages"), - "finalCheckResponsesSent", "Final check responses that this member has sent.", "messages"), - "finalCheckResponsesReceived", "Final check responses that this member has received.","messages"), The above four stats are broken down into two other sets for TCP/IP vs UDP checks: - "tcpFinalCheckRequestsSent", "TCP final check requests that this member has sent.", "messages", false), - "tcpFinalCheckRequestsReceived", "TCP final check requests that this member has received.","messages",
[jira] [Updated] (GEODE-2045) Improve documentation of region shortcuts
[ https://issues.apache.org/jira/browse/GEODE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2045: --- Component/s: docs > Improve documentation of region shortcuts > - > > Key: GEODE-2045 > URL: https://issues.apache.org/jira/browse/GEODE-2045 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The description of a bunch of region shortcuts for partitioned regions says > that they have local scope, and they don't. While fixing this, also fix the > links to those descriptions (since they do not error out, but they also do > not work correctly), and remove many of the links that clutter each > description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2045) Improve documentation of region shortcuts
[ https://issues.apache.org/jira/browse/GEODE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2045: --- Fix Version/s: 1.1.0-incubating > Improve documentation of region shortcuts > - > > Key: GEODE-2045 > URL: https://issues.apache.org/jira/browse/GEODE-2045 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The description of a bunch of region shortcuts for partitioned regions says > that they have local scope, and they don't. While fixing this, also fix the > links to those descriptions (since they do not error out, but they also do > not work correctly), and remove many of the links that clutter each > description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2045) Improve documentation of region shortcuts
[ https://issues.apache.org/jira/browse/GEODE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2045. Resolution: Fixed > Improve documentation of region shortcuts > - > > Key: GEODE-2045 > URL: https://issues.apache.org/jira/browse/GEODE-2045 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The description of a bunch of region shortcuts for partitioned regions says > that they have local scope, and they don't. While fixing this, also fix the > links to those descriptions (since they do not error out, but they also do > not work correctly), and remove many of the links that clutter each > description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2045) Improve documentation of region shortcuts
[ https://issues.apache.org/jira/browse/GEODE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2045: -- Assignee: Karen Smoler Miller > Improve documentation of region shortcuts > - > > Key: GEODE-2045 > URL: https://issues.apache.org/jira/browse/GEODE-2045 > Project: Geode > Issue Type: Bug >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > The description of a bunch of region shortcuts for partitioned regions says > that they have local scope, and they don't. While fixing this, also fix the > links to those descriptions (since they do not error out, but they also do > not work correctly), and remove many of the links that clutter each > description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2047) Document change to enable-network-partition-detection
[ https://issues.apache.org/jira/browse/GEODE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2047: -- Assignee: Karen Smoler Miller > Document change to enable-network-partition-detection > - > > Key: GEODE-2047 > URL: https://issues.apache.org/jira/browse/GEODE-2047 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating > > > This subtask is to change the documentation to reflect the code change that > went into GEODE-762. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2047) Document change to enable-network-partition-detection
[ https://issues.apache.org/jira/browse/GEODE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623556#comment-15623556 ] Karen Smoler Miller commented on GEODE-2047: The doc task here is to change the default setting of enable-network-partition-detection from false to true. > Document change to enable-network-partition-detection > - > > Key: GEODE-2047 > URL: https://issues.apache.org/jira/browse/GEODE-2047 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Karen Smoler Miller > Fix For: 1.0.0-incubating > > > This subtask is to change the documentation to reflect the code change that > went into GEODE-762. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2047) Document change to enable-network-partition-detection
Karen Smoler Miller created GEODE-2047: -- Summary: Document change to enable-network-partition-detection Key: GEODE-2047 URL: https://issues.apache.org/jira/browse/GEODE-2047 Project: Geode Issue Type: Sub-task Reporter: Karen Smoler Miller This subtask is to change the documentation to reflect the code change that went into GEODE-762. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2044) Add tc Server 3.2 for HTTP Sess Mgmt module
[ https://issues.apache.org/jira/browse/GEODE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2044: --- Fix Version/s: 1.1.0-incubating > Add tc Server 3.2 for HTTP Sess Mgmt module > --- > > Key: GEODE-2044 > URL: https://issues.apache.org/jira/browse/GEODE-2044 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Documentation needs to include tc Server 3.2 as available. No changes to > installation or use instructions needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2044) Add tc Server 3.2 for HTTP Sess Mgmt module
[ https://issues.apache.org/jira/browse/GEODE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2044. Resolution: Fixed > Add tc Server 3.2 for HTTP Sess Mgmt module > --- > > Key: GEODE-2044 > URL: https://issues.apache.org/jira/browse/GEODE-2044 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Documentation needs to include tc Server 3.2 as available. No changes to > installation or use instructions needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2045) Improve documentation of region shortcuts
Karen Smoler Miller created GEODE-2045: -- Summary: Improve documentation of region shortcuts Key: GEODE-2045 URL: https://issues.apache.org/jira/browse/GEODE-2045 Project: Geode Issue Type: Bug Reporter: Karen Smoler Miller The description of a bunch of region shortcuts for partitioned regions says that they have local scope, and they don't. While fixing this, also fix the links to those descriptions (since they do not error out, but they also do not work correctly), and remove many of the links that clutter each description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2044) Add tc Server 3.2 for HTTP Sess Mgmt module
[ https://issues.apache.org/jira/browse/GEODE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2044: -- Assignee: Karen Smoler Miller > Add tc Server 3.2 for HTTP Sess Mgmt module > --- > > Key: GEODE-2044 > URL: https://issues.apache.org/jira/browse/GEODE-2044 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > Documentation needs to include tc Server 3.2 as available. No changes to > installation or use instructions needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2044) Add tc Server 3.2 for HTTP Sess Mgmt module
Karen Smoler Miller created GEODE-2044: -- Summary: Add tc Server 3.2 for HTTP Sess Mgmt module Key: GEODE-2044 URL: https://issues.apache.org/jira/browse/GEODE-2044 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller Documentation needs to include tc Server 3.2 as available. No changes to installation or use instructions needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2040) Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module
[ https://issues.apache.org/jira/browse/GEODE-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2040: --- Fix Version/s: 1.1.0-incubating > Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module > > > Key: GEODE-2040 > URL: https://issues.apache.org/jira/browse/GEODE-2040 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Documentation needs to include Tomcat 8.0 and 8.5 as available. Alter set up > instructions to also include them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2040) Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module
[ https://issues.apache.org/jira/browse/GEODE-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2040. Resolution: Fixed > Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module > > > Key: GEODE-2040 > URL: https://issues.apache.org/jira/browse/GEODE-2040 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Documentation needs to include Tomcat 8.0 and 8.5 as available. Alter set up > instructions to also include them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2040) Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module
[ https://issues.apache.org/jira/browse/GEODE-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2040: -- Assignee: Karen Smoler Miller > Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module > > > Key: GEODE-2040 > URL: https://issues.apache.org/jira/browse/GEODE-2040 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > Documentation needs to include Tomcat 8.0 and 8.5 as available. Alter set up > instructions to also include them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2040) Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module
Karen Smoler Miller created GEODE-2040: -- Summary: Add Tomcat 8.0 and 8.5 for HTTP Sess Mgmt module Key: GEODE-2040 URL: https://issues.apache.org/jira/browse/GEODE-2040 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller Documentation needs to include Tomcat 8.0 and 8.5 as available. Alter set up instructions to also include them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2036) Fix documentation typos
[ https://issues.apache.org/jira/browse/GEODE-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2036: -- Assignee: Karen Smoler Miller > Fix documentation typos > --- > > Key: GEODE-2036 > URL: https://issues.apache.org/jira/browse/GEODE-2036 > Project: Geode > Issue Type: Bug >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > This ticket will be used for all documentation commits that fix small errors, > omissions and oversights. Changes committed against this ticket will be of a > small enough scope that there is no need for community input, discussion, or > review. This ticket should remain open only until the release of Geode 1.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (GEODE-2036) Fix documentation typos
[ https://issues.apache.org/jira/browse/GEODE-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller closed GEODE-2036. -- > Fix documentation typos > --- > > Key: GEODE-2036 > URL: https://issues.apache.org/jira/browse/GEODE-2036 > Project: Geode > Issue Type: Bug >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > This ticket will be used for all documentation commits that fix small errors, > omissions and oversights. Changes committed against this ticket will be of a > small enough scope that there is no need for community input, discussion, or > review. This ticket should remain open only until the release of Geode 1.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2036) Fix documentation typos
[ https://issues.apache.org/jira/browse/GEODE-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2036. Resolution: Fixed > Fix documentation typos > --- > > Key: GEODE-2036 > URL: https://issues.apache.org/jira/browse/GEODE-2036 > Project: Geode > Issue Type: Bug >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > This ticket will be used for all documentation commits that fix small errors, > omissions and oversights. Changes committed against this ticket will be of a > small enough scope that there is no need for community input, discussion, or > review. This ticket should remain open only until the release of Geode 1.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2036) Fix documentation typos
[ https://issues.apache.org/jira/browse/GEODE-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609075#comment-15609075 ] Karen Smoler Miller commented on GEODE-2036: Community consensus is to not use a JIRA (like this one) for small documentation fixes. One commit was made under this ticket, with SHA1 f6b534d024fa692eb6b68d215db9d7d33af86ac3, before the consensus was reached. > Fix documentation typos > --- > > Key: GEODE-2036 > URL: https://issues.apache.org/jira/browse/GEODE-2036 > Project: Geode > Issue Type: Bug >Reporter: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > This ticket will be used for all documentation commits that fix small errors, > omissions and oversights. Changes committed against this ticket will be of a > small enough scope that there is no need for community input, discussion, or > review. This ticket should remain open only until the release of Geode 1.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2036) Fix documentation typos
Karen Smoler Miller created GEODE-2036: -- Summary: Fix documentation typos Key: GEODE-2036 URL: https://issues.apache.org/jira/browse/GEODE-2036 Project: Geode Issue Type: Bug Reporter: Karen Smoler Miller Fix For: 1.1.0-incubating This ticket will be used for all documentation commits that fix small errors, omissions and oversights. Changes committed against this ticket will be of a small enough scope that there is no need for community input, discussion, or review. This ticket should remain open only until the release of Geode 1.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2015) Host Geode docs on Geode website
[ https://issues.apache.org/jira/browse/GEODE-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595645#comment-15595645 ] Karen Smoler Miller commented on GEODE-2015: New PR #267 did not get automatically added to this ticket. Here's a link to the PR: https://github.com/apache/incubator-geode/pull/267 > Host Geode docs on Geode website > > > Key: GEODE-2015 > URL: https://issues.apache.org/jira/browse/GEODE-2015 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Joey McAllister >Assignee: Joey McAllister >Priority: Minor > Fix For: 1.1.0-incubating > > > Now that the Geode docs have been donated to the project, let's host them on > the Geode website. > Also document process for posting new docs builds to the website. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2019. Resolution: Fixed > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.0.0-incubating >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > Fix For: 1.1.0-incubating > > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2019: --- Fix Version/s: 1.1.0-incubating > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.0.0-incubating >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > Fix For: 1.1.0-incubating > > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2015) Host Geode docs on Geode website
[ https://issues.apache.org/jira/browse/GEODE-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15593189#comment-15593189 ] Karen Smoler Miller commented on GEODE-2015: PR #266 will get the docs hosted on the website. I'm going to pull it in, and then verify that all the links work. This GEODE-2015 ticket is then to remain open, as the process for doing this is not yet correctly documented, given that the docs are now hosted within the asf-site branch. There will need to be changes to the geode-site/website/README.md file (which is no longer correct in its instructions of how to view the site locally) and to the geode-book/README.md file (which is not complete). > Host Geode docs on Geode website > > > Key: GEODE-2015 > URL: https://issues.apache.org/jira/browse/GEODE-2015 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Joey McAllister >Assignee: Joey McAllister >Priority: Minor > Fix For: 1.1.0-incubating > > > Now that the Geode docs have been donated to the project, let's host them on > the Geode website. > Also document process for posting new docs builds to the website. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592537#comment-15592537 ] Karen Smoler Miller commented on GEODE-2019: Review request for the addition: https://reviews.apache.org/r/53072/ > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.0.0-incubating >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2019: --- Priority: Minor (was: Major) > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.0.0-incubating >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-2019: -- Assignee: Karen Smoler Miller > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2019) Add automated rebalance documentation
Karen Smoler Miller created GEODE-2019: -- Summary: Add automated rebalance documentation Key: GEODE-2019 URL: https://issues.apache.org/jira/browse/GEODE-2019 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller Add documentation for the automated rebalance feature. The feature invokes a rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2019: --- Affects Version/s: 1.1.0-incubating > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.0.0-incubating >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2019) Add automated rebalance documentation
[ https://issues.apache.org/jira/browse/GEODE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2019: --- Affects Version/s: (was: 1.1.0-incubating) 1.0.0-incubating > Add automated rebalance documentation > - > > Key: GEODE-2019 > URL: https://issues.apache.org/jira/browse/GEODE-2019 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.0.0-incubating >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > > Add documentation for the automated rebalance feature. The feature invokes a > rebalance on a time schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1883) AuthInitializer should be made optional
[
https://issues.apache.org/jira/browse/GEODE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-1883:
---
Component/s: docs
> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
> Issue Type: New Feature
> Components: docs, management
>Reporter: Swapnil Bawaskar
>
> {{AuthInitializer}} is the interface that a client must implement that
> provides credentials that are verified by the server. The same interface is
> also used for peer authentication.
> In order to configure {{AuthInitialize}} any Geode property starting with
> {{security-}} is passed through to the {{AuthInitialize.getCredentials}}
> method.
> For simple authentication where only a username and a password are required,
> users should not really be required to implement the AuthInitialize interface
> in the presence of property passthrough.
> Geode should detect {{security-username}} and {{security-password}}
> properties in gemfire.security OR gfsecurity.properties file and use those
> for authentication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GEODE-1883) AuthInitializer should be made optional
[
https://issues.apache.org/jira/browse/GEODE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582756#comment-15582756
]
Karen Smoler Miller edited comment on GEODE-1883 at 10/17/16 7:37 PM:
--
There should be an update in the newly-added documentation about the client
setting of the properties. I will do this in the {{develop}} branch, and if
there must be a third Geode release candidate for 1.0.0-incubating, this change
should be cherry picked into the new release candidate.
Also, the documentation should be updated again if/when this bug is fixed.
was (Author: karensmolermiller):
There should be an update in the newly-added documentation about the client
setting of the properties. I will do this in the {{release/1.0.0-incubating}}
branch, so it goes into the next Geode release candidate.
> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
> Issue Type: New Feature
> Components: management
>Reporter: Swapnil Bawaskar
>
> {{AuthInitializer}} is the interface that a client must implement that
> provides credentials that are verified by the server. The same interface is
> also used for peer authentication.
> In order to configure {{AuthInitialize}} any Geode property starting with
> {{security-}} is passed through to the {{AuthInitialize.getCredentials}}
> method.
> For simple authentication where only a username and a password are required,
> users should not really be required to implement the AuthInitialize interface
> in the presence of property passthrough.
> Geode should detect {{security-username}} and {{security-password}}
> properties in gemfire.security OR gfsecurity.properties file and use those
> for authentication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1883) AuthInitializer should be made optional
[
https://issues.apache.org/jira/browse/GEODE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582756#comment-15582756
]
Karen Smoler Miller commented on GEODE-1883:
There should be an update in the newly-added documentation about the client
setting of the properties. I will do this in the {{release/1.0.0-incubating}}
branch, so it goes into the next Geode release candidate.
> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
> Issue Type: New Feature
> Components: management
>Reporter: Swapnil Bawaskar
>
> {{AuthInitializer}} is the interface that a client must implement that
> provides credentials that are verified by the server. The same interface is
> also used for peer authentication.
> In order to configure {{AuthInitialize}} any Geode property starting with
> {{security-}} is passed through to the {{AuthInitialize.getCredentials}}
> method.
> For simple authentication where only a username and a password are required,
> users should not really be required to implement the AuthInitialize interface
> in the presence of property passthrough.
> Geode should detect {{security-username}} and {{security-password}}
> properties in gemfire.security OR gfsecurity.properties file and use those
> for authentication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1952) Merge documentation to develop branch
[ https://issues.apache.org/jira/browse/GEODE-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-1952: -- Assignee: Karen Smoler Miller > Merge documentation to develop branch > - > > Key: GEODE-1952 > URL: https://issues.apache.org/jira/browse/GEODE-1952 > Project: Geode > Issue Type: New Feature > Components: docs >Reporter: Anthony Baker >Assignee: Karen Smoler Miller > > The staging/docs-grant1 branch [1] contains the source current used to build > the documentation site [2] for geode. In order to merge this source init the > develop branch, we need to: > 1) Review the files and determine if there are any licensing or dependency > considerations. Update the LICENSE and NOTICE files as necessary. > 2) Update the source headers and replace with the Apache source header as > needed. Since these are documentation files, determine if a source header is > required. > 3) Improve the build process to make it simpler for contributors and users. > This includes writing up build instructions. We will need to create a > top-level directory (geode-docs?) to hold the files. > 4) Include the documentation in the source distributions created by the build. > 5) Incorporate other suggestions from the community. > Once the branch has been merged, we should host the documentation site on > geode.apache.org. > [1] > https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tree;h=refs/heads/staging/docs-grant1;hb=refs/heads/staging/docs-grant1 > [2] http://geode.docs.pivotal.io -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) Open geode.properties if gemfire.properties is not found
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-1948: --- Labels: branding configuration docs (was: branding configuration) > Open geode.properties if gemfire.properties is not found > > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration, docs > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1947) Rename SSL_HTTP_REQUIRE_AUTHENTICATION to SSL_WEB_REQUIRE_AUTHENTICATION
[ https://issues.apache.org/jira/browse/GEODE-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-1947: --- Labels: docs (was: ) > Rename SSL_HTTP_REQUIRE_AUTHENTICATION to SSL_WEB_REQUIRE_AUTHENTICATION > > > Key: GEODE-1947 > URL: https://issues.apache.org/jira/browse/GEODE-1947 > Project: Geode > Issue Type: Improvement > Components: docs, security >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer > Labels: docs > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1759) Improve geode-site/website/README.md
[ https://issues.apache.org/jira/browse/GEODE-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-1759. Resolution: Fixed > Improve geode-site/website/README.md > > > Key: GEODE-1759 > URL: https://issues.apache.org/jira/browse/GEODE-1759 > Project: Geode > Issue Type: Improvement > Components: docs, web-content >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating > > > The README.md file with instructions for updating the Geode website need a > bit of improvement. > 1. work to introduce changes to the website should *not* be done in the > master branch > 2. to update the website, the proper set of directories must be placed into a > non-obvious location within the *asf-site* branch. That means that changes > cannot be merged in, but instead must be lifted from the working branch and > placed into the right spot on the *asf-site* branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1759) Improve geode-site/website/README.md
[ https://issues.apache.org/jira/browse/GEODE-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-1759: --- Fix Version/s: 1.0.0-incubating > Improve geode-site/website/README.md > > > Key: GEODE-1759 > URL: https://issues.apache.org/jira/browse/GEODE-1759 > Project: Geode > Issue Type: Improvement > Components: docs, web-content >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating > > > The README.md file with instructions for updating the Geode website need a > bit of improvement. > 1. work to introduce changes to the website should *not* be done in the > master branch > 2. to update the website, the proper set of directories must be placed into a > non-obvious location within the *asf-site* branch. That means that changes > cannot be merged in, but instead must be lifted from the working branch and > placed into the right spot on the *asf-site* branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
