[jira] [Created] (GEODE-6305) Switch off parallel mode for WindowsGfshDistributedTest CI jobs
Jens Deppe created GEODE-6305: - Summary: Switch off parallel mode for WindowsGfshDistributedTest CI jobs Key: GEODE-6305 URL: https://issues.apache.org/jira/browse/GEODE-6305 Project: Geode Issue Type: Task Components: ci Reporter: Jens Deppe The WindowsGfshDistributedTest jobs often fail with bind exceptions. As these jobs are not parallelized, this is probably due to them running in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6305) Switch off parallel mode for WindowsGfshDistributedTest CI jobs
[ https://issues.apache.org/jira/browse/GEODE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-6305: - Assignee: Jens Deppe > Switch off parallel mode for WindowsGfshDistributedTest CI jobs > --- > > Key: GEODE-6305 > URL: https://issues.apache.org/jira/browse/GEODE-6305 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > > The WindowsGfshDistributedTest jobs often fail with bind exceptions. As these > jobs are not parallelized, this is probably due to them running in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6305) Switch off parallel mode for WindowsGfshDistributedTest CI jobs
[ https://issues.apache.org/jira/browse/GEODE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-6305: -- Labels: pull-request-available (was: ) > Switch off parallel mode for WindowsGfshDistributedTest CI jobs > --- > > Key: GEODE-6305 > URL: https://issues.apache.org/jira/browse/GEODE-6305 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > > The WindowsGfshDistributedTest jobs often fail with bind exceptions. As these > jobs are not parallelized, this is probably due to them running in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6306) Have the CreateRegionCommand call the internal Cluster Management service API to create the region with all the options
Jinmei Liao created GEODE-6306: -- Summary: Have the CreateRegionCommand call the internal Cluster Management service API to create the region with all the options Key: GEODE-6306 URL: https://issues.apache.org/jira/browse/GEODE-6306 Project: Geode Issue Type: Improvement Components: configuration, gfsh Reporter: Jinmei Liao Currently the CreateRegionCommand handles all options supported by gfsh, but cluster management api createRegion call only supports name and type. We should add more option support to the internal api and then have the createRegionCommand directly call the api to do all the work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6307) WindowsIntegrationTestOpenJDK11 fails in CI for AnalyzeSerializablesJUnitTest
Jens Deppe created GEODE-6307:
-
Summary: WindowsIntegrationTestOpenJDK11 fails in CI for
AnalyzeSerializablesJUnitTest
Key: GEODE-6307
URL: https://issues.apache.org/jira/browse/GEODE-6307
Project: Geode
Issue Type: Bug
Components: serialization
Reporter: Jens Deppe
This CI job fails consistently with errors such as:
{{java.lang.AssertionError: Expecting actual not to be null at
org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.loadClasses(AnalyzeSerializablesJUnitTestBase.java:445)
at
org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.findClasses(AnalyzeSerializablesJUnitTestBase.java:123)
at
org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.testSerializables(AnalyzeSerializablesJUnitTestBase.java:186)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}}
It is strange that this only happens on JDK11 though. I have a theory that it
has to do with path comparisons so I'm attempting a change that normalizes
paths before checking them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6307) WindowsIntegrationTestOpenJDK11 fails in CI for AnalyzeSerializablesJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-6307:
--
Labels: pull-request-available (was: )
> WindowsIntegrationTestOpenJDK11 fails in CI for AnalyzeSerializablesJUnitTest
> -
>
> Key: GEODE-6307
> URL: https://issues.apache.org/jira/browse/GEODE-6307
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> This CI job fails consistently with errors such as:
> {{java.lang.AssertionError: Expecting actual not to be null at
> org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.loadClasses(AnalyzeSerializablesJUnitTestBase.java:445)
> at
> org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.findClasses(AnalyzeSerializablesJUnitTestBase.java:123)
> at
> org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.testSerializables(AnalyzeSerializablesJUnitTestBase.java:186)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}}
>
> It is strange that this only happens on JDK11 though. I have a theory that it
> has to do with path comparisons so I'm attempting a change that normalizes
> paths before checking them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6307) WindowsIntegrationTestOpenJDK11 fails in CI for AnalyzeSerializablesJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-6307:
-
Assignee: Jens Deppe
> WindowsIntegrationTestOpenJDK11 fails in CI for AnalyzeSerializablesJUnitTest
> -
>
> Key: GEODE-6307
> URL: https://issues.apache.org/jira/browse/GEODE-6307
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> This CI job fails consistently with errors such as:
> {{java.lang.AssertionError: Expecting actual not to be null at
> org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.loadClasses(AnalyzeSerializablesJUnitTestBase.java:445)
> at
> org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.findClasses(AnalyzeSerializablesJUnitTestBase.java:123)
> at
> org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTestBase.testSerializables(AnalyzeSerializablesJUnitTestBase.java:186)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}}
>
> It is strange that this only happens on JDK11 though. I have a theory that it
> has to do with path comparisons so I'm attempting a change that normalizes
> paths before checking them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6308) start and status gfsh command output is missing line separators
[
https://issues.apache.org/jira/browse/GEODE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-6308:
Assignee: Kirk Lund
> start and status gfsh command output is missing line separators
> ---
>
> Key: GEODE-6308
> URL: https://issues.apache.org/jira/browse/GEODE-6308
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> The output used to look like this:
> {noformat}
> % gfsh status server --dir=server4
> Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
> online.
> Process ID: 49008
> Uptime: 2 minutes 4 seconds
> Geode Version: 1.7.0
> Java Version: 1.8.0_144
> Log File: /home/username/server4/server4.log
> JVM Arguments:
> {noformat}
> But it now looks like this:
> {noformat}
> gfsh>start locator
> Starting a Geode Locator in /Users/klund/dev/gemfire4/give-odd-jar...
> ...
> Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
> give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode
> Version: 0.0.0Java Version: 1.8.0_181Log File:
> /Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
> -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
> /Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The line separators should be restored for readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6308) start and status gfsh command output is missing line separators
Kirk Lund created GEODE-6308:
Summary: start and status gfsh command output is missing line
separators
Key: GEODE-6308
URL: https://issues.apache.org/jira/browse/GEODE-6308
Project: Geode
Issue Type: Bug
Reporter: Kirk Lund
The output used to look like this:
{noformat}
% gfsh status server --dir=server4
Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
online.
Process ID: 49008
Uptime: 2 minutes 4 seconds
Geode Version: 1.7.0
Java Version: 1.8.0_144
Log File: /home/username/server4/server4.log
JVM Arguments:
{noformat}
But it now looks like this:
{noformat}
gfsh>start locator
Starting a Geode Locator in /Users/klund/dev/gemfire4/give-odd-jar...
...
Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode Version:
0.0.0Java Version: 1.8.0_181Log File:
/Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
-Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
{noformat}
The line separators should be restored for readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6308) start and status gfsh command output is missing line separators
[
https://issues.apache.org/jira/browse/GEODE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-6308:
-
Component/s: gfsh
> start and status gfsh command output is missing line separators
> ---
>
> Key: GEODE-6308
> URL: https://issues.apache.org/jira/browse/GEODE-6308
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> The output used to look like this:
> {noformat}
> % gfsh status server --dir=server4
> Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
> online.
> Process ID: 49008
> Uptime: 2 minutes 4 seconds
> Geode Version: 1.7.0
> Java Version: 1.8.0_144
> Log File: /home/username/server4/server4.log
> JVM Arguments:
> {noformat}
> But it now looks like this:
> {noformat}
> gfsh>start locator
> Starting a Geode Locator in /Users/klund/dev/gemfire4/give-odd-jar...
> ...
> Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
> give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode
> Version: 0.0.0Java Version: 1.8.0_181Log File:
> /Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
> -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
> /Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The line separators should be restored for readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6306) Have the CreateRegionCommand call the internal Cluster Management service API to create the region with all the options
[ https://issues.apache.org/jira/browse/GEODE-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-6306: -- Labels: pull-request-available (was: ) > Have the CreateRegionCommand call the internal Cluster Management service API > to create the region with all the options > --- > > Key: GEODE-6306 > URL: https://issues.apache.org/jira/browse/GEODE-6306 > Project: Geode > Issue Type: Improvement > Components: configuration, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > > Currently the CreateRegionCommand handles all options supported by gfsh, but > cluster management api createRegion call only supports name and type. We > should add more option support to the internal api and then have the > createRegionCommand directly call the api to do all the work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6300) Assertion in CLI tests re: bad AppDomain
[
https://issues.apache.org/jira/browse/GEODE-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749017#comment-16749017
]
ASF subversion and git services commented on GEODE-6300:
Commit c5c46751ad6198438ca95e9023d2970edf765e5c in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c5c4675 ]
GEODE-6300: Fix AddDomain gripe in CLI tests (#436)
* Make sure *everything* run in thread pool gets the right
AppDomain context
Co-authored-by: Matthew Reddington
> Assertion in CLI tests re: bad AppDomain
>
>
> Key: GEODE-6300
> URL: https://issues.apache.org/jira/browse/GEODE-6300
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> From the ci logs
> (http://concourse-nativeclient.gemfire.pivotal.io/teams/main/pipelines/build-develop/jobs/cli-test-windows-debug/builds/64):
>
> System.ArgumentException: Cannot pass a GCHandle across AppDomains.
> Parameter name: handle
> at System.Runtime.InteropServices.GCHandle.InternalCheckDomain(IntPtr handle)
> at System.Runtime.InteropServices.GCHandle.FromIntPtr(IntPtr value)
> at gcroot ^>.\{dtor}(gcroot* )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.\{dtor}(ManagedDataSerializablePrimitive*
> )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.__vbaseDtor(ManagedDataSerializablePrimitive*
> )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.__vecDelDtor(ManagedDataSerializablePrimitive*
> , UInt32 A_0)
> at
> std._Ref_count._Destroy(_Ref_count*
> )
> errorlevel 0
> + exitcode=1
> + echo exitcode=1
> exitcode=1
> + exit 1
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6305) Switch off parallel mode for WindowsGfshDistributedTest CI jobs
[ https://issues.apache.org/jira/browse/GEODE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749055#comment-16749055 ] ASF subversion and git services commented on GEODE-6305: Commit 5b59595b3585e16d6f117bdd847befd2c3bdf1c7 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5b59595 ] GEODE-6305: Disable Gradle parallel mode for WindowsGfshDistributedTest jobs (#3103) - This option is most likely causing bind exceptions in CI. > Switch off parallel mode for WindowsGfshDistributedTest CI jobs > --- > > Key: GEODE-6305 > URL: https://issues.apache.org/jira/browse/GEODE-6305 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The WindowsGfshDistributedTest jobs often fail with bind exceptions. As these > jobs are not parallelized, this is probably due to them running in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6308) start and status gfsh command output is missing line separators
[
https://issues.apache.org/jira/browse/GEODE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-6308:
--
Labels: pull-request-available (was: )
> start and status gfsh command output is missing line separators
> ---
>
> Key: GEODE-6308
> URL: https://issues.apache.org/jira/browse/GEODE-6308
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
>
> The output used to look like this:
> {noformat}
> % gfsh status server --dir=server4
> Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
> online.
> Process ID: 49008
> Uptime: 2 minutes 4 seconds
> Geode Version: 1.7.0
> Java Version: 1.8.0_144
> Log File: /home/username/server4/server4.log
> JVM Arguments:
> {noformat}
> But it now looks like this:
> {noformat}
> gfsh>start locator
> Starting a Geode Locator in /Users/klund/dev/gemfire4/give-odd-jar...
> ...
> Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
> give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode
> Version: 0.0.0Java Version: 1.8.0_181Log File:
> /Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
> -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
> /Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The line separators should be restored for readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6308) start and status gfsh command output is missing line separators
[
https://issues.apache.org/jira/browse/GEODE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-6308:
-
Description:
The output used to look like this:
{noformat}
Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
online.
Process ID: 49008
Uptime: 2 minutes 4 seconds
Geode Version: 1.7.0
Java Version: 1.8.0_144
Log File: /home/username/server4/server4.log
JVM Arguments:
{noformat}
But it now looks like this:
{noformat}
Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode Version:
0.0.0Java Version: 1.8.0_181Log File:
/Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
-Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
{noformat}
The line separators should be restored for readability.
was:
The output used to look like this:
{noformat}
% gfsh status server --dir=server4
Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
online.
Process ID: 49008
Uptime: 2 minutes 4 seconds
Geode Version: 1.7.0
Java Version: 1.8.0_144
Log File: /home/username/server4/server4.log
JVM Arguments:
{noformat}
But it now looks like this:
{noformat}
gfsh>start locator
Starting a Geode Locator in /Users/klund/dev/gemfire4/give-odd-jar...
...
Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode Version:
0.0.0Java Version: 1.8.0_181Log File:
/Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
-Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
{noformat}
The line separators should be restored for readability.
> start and status gfsh command output is missing line separators
> ---
>
> Key: GEODE-6308
> URL: https://issues.apache.org/jira/browse/GEODE-6308
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The output used to look like this:
> {noformat}
> Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
> online.
> Process ID: 49008
> Uptime: 2 minutes 4 seconds
> Geode Version: 1.7.0
> Java Version: 1.8.0_144
> Log File: /home/username/server4/server4.log
> JVM Arguments:
> {noformat}
> But it now looks like this:
> {noformat}
> Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
> give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode
> Version: 0.0.0Java Version: 1.8.0_181Log File:
> /Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
> -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
> /Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The line separators should be restored for readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6297) CI failure: LocatorLauncherRemoteFileIntegrationTest.statusWithPidReturnsOnlineWithDetails
[
https://issues.apache.org/jira/browse/GEODE-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749065#comment-16749065
]
ASF subversion and git services commented on GEODE-6297:
Commit 654dc3bac3e50e66f33385bdbc38c88750061aa9 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=654dc3b ]
GEODE-6297: Add Process info to Launcher status failure msg
This will provide some details about if the process is actually
alive or not when FileProcessController.status throws
IllegalStateException.
When the test fails again, if Process is not alive then the
underlying cause is probably something like a BindException
preventing the startup of the Locator process.
This info will also apply to GEODE-6183 which is nearly
identical.
I'm including the change in ServerLauncherRemoteIntegrationTestCase
as well in case there's ever a similar failure starting up a
server.
> CI failure:
> LocatorLauncherRemoteFileIntegrationTest.statusWithPidReturnsOnlineWithDetails
> --
>
> Key: GEODE-6297
> URL: https://issues.apache.org/jira/browse/GEODE-6297
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Bruce Schuchardt
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Failed in Windows CI run
> [232|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK8/builds/232]
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
> statusWithPidReturnsOnlineWithDetails FAILED
> java.lang.IllegalStateException: Status file
> 'C:\Users\geode\AppData\Local\Temp\junit7623641902150852427\vf.gf.locator.status'
> is blank
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6308) start and status gfsh command output is missing line separators
[
https://issues.apache.org/jira/browse/GEODE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-6308:
-
Description:
Server and Locator start/status/stop gfsh command output is missing line
separators.
The output used to look like this:
{noformat}
Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
online.
Process ID: 49008
Uptime: 2 minutes 4 seconds
Geode Version: 1.7.0
Java Version: 1.8.0_144
Log File: /home/username/server4/server4.log
JVM Arguments:
{noformat}
But it now looks like this:
{noformat}
Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode Version:
0.0.0Java Version: 1.8.0_181Log File:
/Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
-Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
{noformat}
The line separators should be restored for readability.
was:
The output used to look like this:
{noformat}
Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
online.
Process ID: 49008
Uptime: 2 minutes 4 seconds
Geode Version: 1.7.0
Java Version: 1.8.0_144
Log File: /home/username/server4/server4.log
JVM Arguments:
{noformat}
But it now looks like this:
{noformat}
Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode Version:
0.0.0Java Version: 1.8.0_181Log File:
/Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
-Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
{noformat}
The line separators should be restored for readability.
> start and status gfsh command output is missing line separators
> ---
>
> Key: GEODE-6308
> URL: https://issues.apache.org/jira/browse/GEODE-6308
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Server and Locator start/status/stop gfsh command output is missing line
> separators.
> The output used to look like this:
> {noformat}
> Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
> online.
> Process ID: 49008
> Uptime: 2 minutes 4 seconds
> Geode Version: 1.7.0
> Java Version: 1.8.0_144
> Log File: /home/username/server4/server4.log
> JVM Arguments:
> {noformat}
> But it now looks like this:
> {noformat}
> Locator in /Users/klund/dev/gemfire4/give-odd-jar on 10.118.20.84[10334] as
> give-odd-jar is currently online.Process ID: 799Uptime: 6 secondsGeode
> Version: 0.0.0Java Version: 1.8.0_181Log File:
> /Users/klund/dev/gemfire4/give-odd-jar/give-odd-jar.logJVM Arguments:
> -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806Class-Path:
> /Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-core-0.0.0.jar:/Users/klund/dev/gemfire4/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The line separators should be restored for readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6292) Hot loop when joining if locator-wait-time is set and there are no locators
[ https://issues.apache.org/jira/browse/GEODE-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749073#comment-16749073 ] ASF subversion and git services commented on GEODE-6292: Commit e52f6f66fb64ec40553b14e6f312fff2fcc7bbe8 in geode's branch refs/heads/feature/GEODE-6290 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e52f6f6 ] GEODE-6292 hot loop in GMSJoinLeave.findCoordinator Added a 1 second pause before retrying if no locators could be contacted and locator-wait-time has been set. > Hot loop when joining if locator-wait-time is set and there are no locators > --- > > Key: GEODE-6292 > URL: https://issues.apache.org/jira/browse/GEODE-6292 > Project: Geode > Issue Type: New Feature > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > If you start up a locator and three servers and then kill two of the servers > the locator and remaining server will go into auto-reconnect mode. When they > attempt to start up they will run a hot thread if locator-wait-time is set > because there is no stall in the loop that contacts locators for the duration > of this wait time in GMSJoinLeave.findCoordinator(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6294) Add disable-jmx configuration property to disable JMX
[ https://issues.apache.org/jira/browse/GEODE-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749074#comment-16749074 ] ASF subversion and git services commented on GEODE-6294: Commit 86099f921ef08696016a886d8abe9d3b5ee97eb5 in geode's branch refs/heads/feature/GEODE-6290 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=86099f9 ] GEODE-6294: Add disable-jmx config property > Add disable-jmx configuration property to disable JMX > - > > Key: GEODE-6294 > URL: https://issues.apache.org/jira/browse/GEODE-6294 > Project: Geode > Issue Type: Improvement > Components: configuration, jmx >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add disable-jmx configuration property to disable JMX. This option is boolean > and will have a false value by default. Setting it to true will prevent Geode > from creating and using MBeans. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6305) Switch off parallel mode for WindowsGfshDistributedTest CI jobs
[ https://issues.apache.org/jira/browse/GEODE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749077#comment-16749077 ] ASF subversion and git services commented on GEODE-6305: Commit 5b59595b3585e16d6f117bdd847befd2c3bdf1c7 in geode's branch refs/heads/feature/GEODE-6290 from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5b59595 ] GEODE-6305: Disable Gradle parallel mode for WindowsGfshDistributedTest jobs (#3103) - This option is most likely causing bind exceptions in CI. > Switch off parallel mode for WindowsGfshDistributedTest CI jobs > --- > > Key: GEODE-6305 > URL: https://issues.apache.org/jira/browse/GEODE-6305 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The WindowsGfshDistributedTest jobs often fail with bind exceptions. As these > jobs are not parallelized, this is probably due to them running in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6212) Need to add unit test on checkEquals method in ValueComparisonHelper class
[ https://issues.apache.org/jira/browse/GEODE-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749071#comment-16749071 ] ASF subversion and git services commented on GEODE-6212: Commit 3cf75b6e057320ae5b9338dc6433afb168151b6c in geode's branch refs/heads/feature/GEODE-6290 from pivotal-eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3cf75b6 ] GEODE-6212: Add unit test coverage for ValueComparisonHelper (#3082) * fixed an error in the helper class when adding test coverage. > Need to add unit test on checkEquals method in ValueComparisonHelper class > -- > > Key: GEODE-6212 > URL: https://issues.apache.org/jira/browse/GEODE-6212 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The method was moved from AbstractRegionEntry. Need to add unit test coverage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6290) PdxInstance with an empty string as class name should not support class versioning
[ https://issues.apache.org/jira/browse/GEODE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749078#comment-16749078 ] ASF subversion and git services commented on GEODE-6290: Commit 464b0fc87cbe5d84d0ac000c7a651f30b5165250 in geode's branch refs/heads/feature/GEODE-6290 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=464b0fc ] Merge branch 'develop' into feature/GEODE-6290 > PdxInstance with an empty string as class name should not support class > versioning > -- > > Key: GEODE-6290 > URL: https://issues.apache.org/jira/browse/GEODE-6290 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Currently if you create a PdxInstanceFactory with the empty string as the > class name then the PdxInstances it creates support class versioning. Since > the empty string is not a class, these PdxInstances should not support class > versioning. The only place this shows up is in PdxInstance.equal which allows > two instances with different identity fields to still be equal. It does this > if the one that has the identity field has the default value for it. > What should happen if you have two PdxInstances with the class name "", is > that they are only equal if the have all the same identity fields. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6292) Hot loop when joining if locator-wait-time is set and there are no locators
[ https://issues.apache.org/jira/browse/GEODE-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749080#comment-16749080 ] ASF subversion and git services commented on GEODE-6292: Commit e52f6f66fb64ec40553b14e6f312fff2fcc7bbe8 in geode's branch refs/heads/feature/GEODE-6273 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e52f6f6 ] GEODE-6292 hot loop in GMSJoinLeave.findCoordinator Added a 1 second pause before retrying if no locators could be contacted and locator-wait-time has been set. > Hot loop when joining if locator-wait-time is set and there are no locators > --- > > Key: GEODE-6292 > URL: https://issues.apache.org/jira/browse/GEODE-6292 > Project: Geode > Issue Type: New Feature > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > If you start up a locator and three servers and then kill two of the servers > the locator and remaining server will go into auto-reconnect mode. When they > attempt to start up they will run a hot thread if locator-wait-time is set > because there is no stall in the loop that contacts locators for the duration > of this wait time in GMSJoinLeave.findCoordinator(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6297) CI failure: LocatorLauncherRemoteFileIntegrationTest.statusWithPidReturnsOnlineWithDetails
[
https://issues.apache.org/jira/browse/GEODE-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749085#comment-16749085
]
ASF subversion and git services commented on GEODE-6297:
Commit 654dc3bac3e50e66f33385bdbc38c88750061aa9 in geode's branch
refs/heads/feature/GEODE-6273 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=654dc3b ]
GEODE-6297: Add Process info to Launcher status failure msg
This will provide some details about if the process is actually
alive or not when FileProcessController.status throws
IllegalStateException.
When the test fails again, if Process is not alive then the
underlying cause is probably something like a BindException
preventing the startup of the Locator process.
This info will also apply to GEODE-6183 which is nearly
identical.
I'm including the change in ServerLauncherRemoteIntegrationTestCase
as well in case there's ever a similar failure starting up a
server.
> CI failure:
> LocatorLauncherRemoteFileIntegrationTest.statusWithPidReturnsOnlineWithDetails
> --
>
> Key: GEODE-6297
> URL: https://issues.apache.org/jira/browse/GEODE-6297
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Bruce Schuchardt
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Failed in Windows CI run
> [232|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK8/builds/232]
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
> statusWithPidReturnsOnlineWithDetails FAILED
> java.lang.IllegalStateException: Status file
> 'C:\Users\geode\AppData\Local\Temp\junit7623641902150852427\vf.gf.locator.status'
> is blank
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6232) CI failure: PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer hangs
[ https://issues.apache.org/jira/browse/GEODE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749082#comment-16749082 ] ASF subversion and git services commented on GEODE-6232: Commit 14359cca827f94968bc0997240110343a56f395e in geode's branch refs/heads/feature/GEODE-6273 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=14359cc ] GEODE-6232: Disable JMX in PersistentPartitionedRegionRegressionTest > CI failure: > PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer > hangs > > > Key: GEODE-6232 > URL: https://issues.apache.org/jira/browse/GEODE-6232 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > I did not find any call stacks. > The distributedTest-progress.txt file shows this test starts but does not > complete: > 2018-12-20 19:52:27.157 + Starting test > org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionRegressionTest > doesNotWaitForPreviousInstanceOfOnlineServer > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.302/test-results/distributedTest/1545341717/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.302/test-artifacts/1545341717/distributedtestfiles-OpenJDK8-1.9.0-build.302.tgz > This occurred in DistributedTestOpenJDK8 tab #262, but a similar failure is > showing on tab #242 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6268) initializeUniquePortRange_willReturnUniquePortsForUniqueRanges seems flaky on Windows
[ https://issues.apache.org/jira/browse/GEODE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749083#comment-16749083 ] ASF subversion and git services commented on GEODE-6268: Commit bd45232c82e9651a85074fe939540ca115918f4b in geode's branch refs/heads/feature/GEODE-6273 from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bd45232 ] GEODE-6268: Reduce the number of iterations for unique port ranges in AvailablePortHelperIntegrationTest (#3092) - This test was failing fairly consistently on Windows. An initial assumption was that the given port range would be completely free. This is typically true in a Linux/Docker environment but is not the case on Windows. - The logic of these modified tests is somewhat extreme as in actual use, there would never be a need for 1000 ranges. Signed-off-by: Aditya Anchuri > initializeUniquePortRange_willReturnUniquePortsForUniqueRanges seems flaky on > Windows > - > > Key: GEODE-6268 > URL: https://issues.apache.org/jira/browse/GEODE-6268 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Kenneth Howe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.internal.AvailablePortHelperIntegrationTest.initializeUniquePortRange_willReturnUniquePortsForUniqueRanges > periodically fails on windows. It seems like there's some flakiness being > introduced that may be platform specfic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6244) Healthy member kicked out by Sick member when final-check fails
[ https://issues.apache.org/jira/browse/GEODE-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749079#comment-16749079 ] ASF subversion and git services commented on GEODE-6244: Commit ffd6b38e78ccb7f4a1b451cbcf59c16e7696393e in geode's branch refs/heads/feature/GEODE-6273 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ffd6b38 ] GEODE-6244 Healthy member kicked out by sick member - do not allow membership manager suspect initiation to kick out a member on the first failed check - perform a self-health check before sending SuspectRequest messages - consider members who have sent shutdown messages as gone when performing "should I become coordinator" checks in GMSHealthMonitor > Healthy member kicked out by Sick member when final-check fails > --- > > Key: GEODE-6244 > URL: https://issues.apache.org/jira/browse/GEODE-6244 > Project: Geode > Issue Type: New Feature > Components: membership >Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0, > 1.7.0, 1.8.0 >Reporter: Bruce Schuchardt >Priority: Major > Fix For: 1.9.0 > > > I observed this in a user's logs & can't include artifacts: Clients were > herding to one server when another server was being slow to return results. > The clients caused the server to run out of file descriptors because the > descriptor limit was set pretty low. When that happened the server had > trouble forming an outgoing tcp/ip connection to another server. It tried > using MembershipManager.verifyMember() which also failed to connect to the > other server. When that happened it sent a RemoveMessage to the locators and > several of the other servers, including the one it couldn't connect to. That > server immediately shut itself down. > MembershipManager.verifyMember() is documented to only initiate suspect > processing on the target, not initiate immediate removal. This is supposed > to be done so that some other process (i.e., the membership coordinator) will > do additional checking on the suspect in case the initiator is itself sick. > That was the case in this situation. > serverA unable to connect to serverB > serverA performs tcp/ip check in verifyMember > serverA's tcp/ip check fails (it's out of file descriptors, duh) > serverA sends RemoveMember message to locators and serverB > serverB shuts itself down (ForcedDisconnect) > The behavior should instead be > serverA unable to connect to serverB > serverA performs tcp/ip check in verifyMember > serverA's tcp/ip check fails (it's out of file descriptors, duh) > serverA sends SuspectMember message to locators & other servers > coordinator performs tcp/ip and heartbeat check on the suspect > coordinator determines suspect is available > This is all due to the checkMember call in GMSMembershipManager passing > _true_ for the _initiateRemoval_ parameter. It should be passing _false_. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749086#comment-16749086 ] ASF subversion and git services commented on GEODE-6183: Commit 654dc3bac3e50e66f33385bdbc38c88750061aa9 in geode's branch refs/heads/feature/GEODE-6273 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=654dc3b ] GEODE-6297: Add Process info to Launcher status failure msg This will provide some details about if the process is actually alive or not when FileProcessController.status throws IllegalStateException. When the test fails again, if Process is not alive then the underlying cause is probably something like a BindException preventing the startup of the Locator process. This info will also apply to GEODE-6183 which is nearly identical. I'm including the change in ServerLauncherRemoteIntegrationTestCase as well in case there's ever a similar failure starting up a server. > CI Failure: > LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed > with ConditionTimeoutException > > > Key: GEODE-6183 > URL: https://issues.apache.org/jira/browse/GEODE-6183 > Project: Geode > Issue Type: Bug > Components: ci, gfsh >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Major > > Test failed in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/223 > org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > > startDeletesStaleControlFiles FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase that > uses org.apache.geode.distributed.LocatorLauncher expected:<[online]> but > was:<[not responding]> within 300 seconds. > Caused by: > org.junit.ComparisonFailure: expected:<[online]> but was:<[not > responding]> -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6294) Add disable-jmx configuration property to disable JMX
[ https://issues.apache.org/jira/browse/GEODE-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749081#comment-16749081 ] ASF subversion and git services commented on GEODE-6294: Commit 86099f921ef08696016a886d8abe9d3b5ee97eb5 in geode's branch refs/heads/feature/GEODE-6273 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=86099f9 ] GEODE-6294: Add disable-jmx config property > Add disable-jmx configuration property to disable JMX > - > > Key: GEODE-6294 > URL: https://issues.apache.org/jira/browse/GEODE-6294 > Project: Geode > Issue Type: Improvement > Components: configuration, jmx >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add disable-jmx configuration property to disable JMX. This option is boolean > and will have a false value by default. Setting it to true will prevent Geode > from creating and using MBeans. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6305) Switch off parallel mode for WindowsGfshDistributedTest CI jobs
[ https://issues.apache.org/jira/browse/GEODE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749084#comment-16749084 ] ASF subversion and git services commented on GEODE-6305: Commit 5b59595b3585e16d6f117bdd847befd2c3bdf1c7 in geode's branch refs/heads/feature/GEODE-6273 from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5b59595 ] GEODE-6305: Disable Gradle parallel mode for WindowsGfshDistributedTest jobs (#3103) - This option is most likely causing bind exceptions in CI. > Switch off parallel mode for WindowsGfshDistributedTest CI jobs > --- > > Key: GEODE-6305 > URL: https://issues.apache.org/jira/browse/GEODE-6305 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The WindowsGfshDistributedTest jobs often fail with bind exceptions. As these > jobs are not parallelized, this is probably due to them running in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6268) initializeUniquePortRange_willReturnUniquePortsForUniqueRanges seems flaky on Windows
[ https://issues.apache.org/jira/browse/GEODE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749076#comment-16749076 ] ASF subversion and git services commented on GEODE-6268: Commit bd45232c82e9651a85074fe939540ca115918f4b in geode's branch refs/heads/feature/GEODE-6290 from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bd45232 ] GEODE-6268: Reduce the number of iterations for unique port ranges in AvailablePortHelperIntegrationTest (#3092) - This test was failing fairly consistently on Windows. An initial assumption was that the given port range would be completely free. This is typically true in a Linux/Docker environment but is not the case on Windows. - The logic of these modified tests is somewhat extreme as in actual use, there would never be a need for 1000 ranges. Signed-off-by: Aditya Anchuri > initializeUniquePortRange_willReturnUniquePortsForUniqueRanges seems flaky on > Windows > - > > Key: GEODE-6268 > URL: https://issues.apache.org/jira/browse/GEODE-6268 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Kenneth Howe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.internal.AvailablePortHelperIntegrationTest.initializeUniquePortRange_willReturnUniquePortsForUniqueRanges > periodically fails on windows. It seems like there's some flakiness being > introduced that may be platform specfic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6244) Healthy member kicked out by Sick member when final-check fails
[ https://issues.apache.org/jira/browse/GEODE-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749072#comment-16749072 ] ASF subversion and git services commented on GEODE-6244: Commit ffd6b38e78ccb7f4a1b451cbcf59c16e7696393e in geode's branch refs/heads/feature/GEODE-6290 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ffd6b38 ] GEODE-6244 Healthy member kicked out by sick member - do not allow membership manager suspect initiation to kick out a member on the first failed check - perform a self-health check before sending SuspectRequest messages - consider members who have sent shutdown messages as gone when performing "should I become coordinator" checks in GMSHealthMonitor > Healthy member kicked out by Sick member when final-check fails > --- > > Key: GEODE-6244 > URL: https://issues.apache.org/jira/browse/GEODE-6244 > Project: Geode > Issue Type: New Feature > Components: membership >Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0, > 1.7.0, 1.8.0 >Reporter: Bruce Schuchardt >Priority: Major > Fix For: 1.9.0 > > > I observed this in a user's logs & can't include artifacts: Clients were > herding to one server when another server was being slow to return results. > The clients caused the server to run out of file descriptors because the > descriptor limit was set pretty low. When that happened the server had > trouble forming an outgoing tcp/ip connection to another server. It tried > using MembershipManager.verifyMember() which also failed to connect to the > other server. When that happened it sent a RemoveMessage to the locators and > several of the other servers, including the one it couldn't connect to. That > server immediately shut itself down. > MembershipManager.verifyMember() is documented to only initiate suspect > processing on the target, not initiate immediate removal. This is supposed > to be done so that some other process (i.e., the membership coordinator) will > do additional checking on the suspect in case the initiator is itself sick. > That was the case in this situation. > serverA unable to connect to serverB > serverA performs tcp/ip check in verifyMember > serverA's tcp/ip check fails (it's out of file descriptors, duh) > serverA sends RemoveMember message to locators and serverB > serverB shuts itself down (ForcedDisconnect) > The behavior should instead be > serverA unable to connect to serverB > serverA performs tcp/ip check in verifyMember > serverA's tcp/ip check fails (it's out of file descriptors, duh) > serverA sends SuspectMember message to locators & other servers > coordinator performs tcp/ip and heartbeat check on the suspect > coordinator determines suspect is available > This is all due to the checkMember call in GMSMembershipManager passing > _true_ for the _initiateRemoval_ parameter. It should be passing _false_. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6273) Add server group support for JDBC mapping
[
https://issues.apache.org/jira/browse/GEODE-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749087#comment-16749087
]
ASF subversion and git services commented on GEODE-6273:
Commit a0bb2415804c04b43265ae99dac458b235db50dd in geode's branch
refs/heads/feature/GEODE-6273 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a0bb241 ]
GEODE-6273: add server group parameter for creating mapping command
> Add server group support for JDBC mapping
> -
>
> Key: GEODE-6273
> URL: https://issues.apache.org/jira/browse/GEODE-6273
> Project: Geode
> Issue Type: Improvement
> Components: extensions, gfsh
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As a Geode user, I want to specify which server group holds the region, so
> that I can add the JDBC mapping to that region.
> Given a Geode region exists on a server group, when I run {{create
> jdbc-mapping}} for that region
> Then I can specify the server group with an option on the command line, so
> that the jdbc-mapping is successfully recognized and completed.
> Given {{create jdbc-mapping}} has a server group option defined, when I run
> {{describe jdbc-mapping}}, then I can see the server group option definition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6232) CI failure: PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer hangs
[ https://issues.apache.org/jira/browse/GEODE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749075#comment-16749075 ] ASF subversion and git services commented on GEODE-6232: Commit 14359cca827f94968bc0997240110343a56f395e in geode's branch refs/heads/feature/GEODE-6290 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=14359cc ] GEODE-6232: Disable JMX in PersistentPartitionedRegionRegressionTest > CI failure: > PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer > hangs > > > Key: GEODE-6232 > URL: https://issues.apache.org/jira/browse/GEODE-6232 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > I did not find any call stacks. > The distributedTest-progress.txt file shows this test starts but does not > complete: > 2018-12-20 19:52:27.157 + Starting test > org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionRegressionTest > doesNotWaitForPreviousInstanceOfOnlineServer > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.302/test-results/distributedTest/1545341717/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.302/test-artifacts/1545341717/distributedtestfiles-OpenJDK8-1.9.0-build.302.tgz > This occurred in DistributedTestOpenJDK8 tab #262, but a similar failure is > showing on tab #242 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6302) checkPom only checks dependencies, but not other Pom sections
[
https://issues.apache.org/jira/browse/GEODE-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-6302:
---
Assignee: Patrick Rhomberg
> checkPom only checks dependencies, but not other Pom sections
> -
>
> Key: GEODE-6302
> URL: https://issues.apache.org/jira/browse/GEODE-6302
> Project: Geode
> Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> Most notable, the {{dependencyManagement}} section can now change without the
> {{checkPom}} task failing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749066#comment-16749066 ] ASF subversion and git services commented on GEODE-6183: Commit 654dc3bac3e50e66f33385bdbc38c88750061aa9 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=654dc3b ] GEODE-6297: Add Process info to Launcher status failure msg This will provide some details about if the process is actually alive or not when FileProcessController.status throws IllegalStateException. When the test fails again, if Process is not alive then the underlying cause is probably something like a BindException preventing the startup of the Locator process. This info will also apply to GEODE-6183 which is nearly identical. I'm including the change in ServerLauncherRemoteIntegrationTestCase as well in case there's ever a similar failure starting up a server. > CI Failure: > LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed > with ConditionTimeoutException > > > Key: GEODE-6183 > URL: https://issues.apache.org/jira/browse/GEODE-6183 > Project: Geode > Issue Type: Bug > Components: ci, gfsh >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Major > > Test failed in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/223 > org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > > startDeletesStaleControlFiles FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase that > uses org.apache.geode.distributed.LocatorLauncher expected:<[online]> but > was:<[not responding]> within 300 seconds. > Caused by: > org.junit.ComparisonFailure: expected:<[online]> but was:<[not > responding]> -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6267) Subjects are not logged out when a client departs causing a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749131#comment-16749131
]
ASF subversion and git services commented on GEODE-6267:
Commit 27ba430047f73834c1959c13f5297f188550b855 in geode's branch
refs/heads/feature/GEODE-6267 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=27ba430 ]
GEODE-6267: Added annotations and cleaned up test code
> Subjects are not logged out when a client departs causing a memory leak
> ---
>
> Key: GEODE-6267
> URL: https://issues.apache.org/jira/browse/GEODE-6267
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a client with security enabled connects to a server, the
> IntegratedSecurityService logs in a Subject. This causes a SimpleSession to
> be created.
> The Subject is stored in ClientUserAuths.uniqueIdVsSubject.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:42.993 PST server1 Thread 0> tid=0x4e] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.newSessionInstance(DefaultSessionManager.java:163)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.doCreateSession(DefaultSessionManager.java:154)
> at
> org.apache.shiro.session.mgt.AbstractValidatingSessionManager.createSession(AbstractValidatingSessionManager.java:136)
> at
> org.apache.shiro.session.mgt.AbstractNativeSessionManager.start(AbstractNativeSessionManager.java:99)
> at
> org.apache.shiro.mgt.SessionsSecurityManager.start(SessionsSecurityManager.java:152)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:336)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:312)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.mergePrincipals(DefaultSubjectDAO.java:204)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.saveToSession(DefaultSubjectDAO.java:166)
> at org.apache.shiro.mgt.DefaultSubjectDAO.save(DefaultSubjectDAO.java:147)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.save(DefaultSecurityManager.java:383)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:350)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:183)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:283)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:139)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.verifyCredentials(HandShake.java:1688)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.setCredentials(ServerConnection.java:1044)
> at
> org.apache.geode.internal.cache.tier.sockets.command.PutUserCredentials.cmdExecute(PutUserCredentials.java:52)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:163)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:797)
> at
> org.apache.geode.internal.cache.tier.sockets.LegacyServerConnection.doOneMessage(LegacyServerConnection.java:85)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:641)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> When the client disconnects, the ClientUserAuths is cleaned up (in cleanup),
> but the Subjects are not logged out.
> With subscription-enabled=true, an additional Subject is created and stored
> in the CacheClientProxy subject. This Subject is not logged out either.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:43.023 PST server1 Thread 0> tid=0x52] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.ap
[jira] [Commented] (GEODE-6283) The v2 REST conrtoller have a LocatorClusterManagementService instance injected and created
[
https://issues.apache.org/jira/browse/GEODE-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749167#comment-16749167
]
ASF subversion and git services commented on GEODE-6283:
Commit a15136a2de85751ea57afa27d5d0dd91bfb75d91 in geode's branch
refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a15136a ]
GEODE-6283: have the management rest controller call the internal management
service
* GEODE-6283: have the management rest controller call the internal cluster
management service to actually create the region
* inject cluster management service to the rest controller
* have the controller produce json string for response
* refactor the controller exception handler to always send back json string
> The v2 REST conrtoller have a LocatorClusterManagementService instance
> injected and created
> ---
>
> Key: GEODE-6283
> URL: https://issues.apache.org/jira/browse/GEODE-6283
> Project: Geode
> Issue Type: Sub-task
> Components: configuration
>Reporter: Kenneth Howe
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As originally implemented, the controller is a noop. Inject a
> {ClusterManagementService}} into the controller and call it's {{create}}
> method.
> The result of this implementation should be:
> When: {{curl :7070/geode-management/v2}} with a cache element
> with region name and type
>
> Then: {{gfsh list regions}} should show that the region was created in the
> cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6283) The v2 REST conrtoller have a LocatorClusterManagementService instance injected and created
[
https://issues.apache.org/jira/browse/GEODE-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749168#comment-16749168
]
ASF subversion and git services commented on GEODE-6283:
Commit a15136a2de85751ea57afa27d5d0dd91bfb75d91 in geode's branch
refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a15136a ]
GEODE-6283: have the management rest controller call the internal management
service
* GEODE-6283: have the management rest controller call the internal cluster
management service to actually create the region
* inject cluster management service to the rest controller
* have the controller produce json string for response
* refactor the controller exception handler to always send back json string
> The v2 REST conrtoller have a LocatorClusterManagementService instance
> injected and created
> ---
>
> Key: GEODE-6283
> URL: https://issues.apache.org/jira/browse/GEODE-6283
> Project: Geode
> Issue Type: Sub-task
> Components: configuration
>Reporter: Kenneth Howe
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As originally implemented, the controller is a noop. Inject a
> {ClusterManagementService}} into the controller and call it's {{create}}
> method.
> The result of this implementation should be:
> When: {{curl :7070/geode-management/v2}} with a cache element
> with region name and type
>
> Then: {{gfsh list regions}} should show that the region was created in the
> cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6309) ClusterConfigLocatorRestartDUnitTest fails to spin up a new server
Bruce Schuchardt created GEODE-6309:
---
Summary: ClusterConfigLocatorRestartDUnitTest fails to spin up a
new server
Key: GEODE-6309
URL: https://issues.apache.org/jira/browse/GEODE-6309
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce Schuchardt
One of this class's tests starts a locator and two servers, then it
force-disconnects the locator and one of the servers & waits for the locator to
reconnect. After that it starts a third server and expects it to join the
cluster but this failed to happen in CI run 316:
{noformat}
> Task :geode-core:distributedTest
org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> serverRestartsAfterLocatorReconnects FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$46/1297938526.call
in VM 3 running on Host 74139c18c4e4 with 5 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:533)
at org.apache.geode.test.dunit.VM.invoke(VM.java:390)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:239)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:232)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:218)
at
org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:71)
Caused by:
org.apache.geode.SystemConnectException: Unable to join the distributed
system in 60032ms
{noformat}
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/316]
SHA: 654dc3bac3e50e66f33385bdbc38c88750061aa9
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6309) ClusterConfigLocatorRestartDUnitTest fails to spin up a new server
[
https://issues.apache.org/jira/browse/GEODE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-6309:
---
Assignee: Bruce Schuchardt
> ClusterConfigLocatorRestartDUnitTest fails to spin up a new server
> --
>
> Key: GEODE-6309
> URL: https://issues.apache.org/jira/browse/GEODE-6309
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>
> One of this class's tests starts a locator and two servers, then it
> force-disconnects the locator and one of the servers & waits for the locator
> to reconnect. After that it starts a third server and expects it to join the
> cluster but this failed to happen in CI run 316:
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$46/1297938526.call
> in VM 3 running on Host 74139c18c4e4 with 5 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:533)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:390)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:239)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:232)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:218)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:71)
> Caused by:
> org.apache.geode.SystemConnectException: Unable to join the
> distributed system in 60032ms
> {noformat}
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/316]
> SHA: 654dc3bac3e50e66f33385bdbc38c88750061aa9
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6309) ClusterConfigLocatorRestartDUnitTest fails to spin up a new server
[
https://issues.apache.org/jira/browse/GEODE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749218#comment-16749218
]
Bruce Schuchardt commented on GEODE-6309:
-
We either need to change the test's method that waits for the locator's
DistributedSystem to be connected (isConnected() == true) or we need to move
the code that stops the locator in InternalDistributedSystem.disconnect() to a
point before DisconnectListeners are invoked. That's currently done through
doDisconnects().
The test is finding the old InternalLocator and is thinking that the locator
has reconnected because the old InternalLocator's cluster configuration service
says it's running. A check for
internalLocator.getDistributedSystem().isConnected() in that method would fix
the problem.
> ClusterConfigLocatorRestartDUnitTest fails to spin up a new server
> --
>
> Key: GEODE-6309
> URL: https://issues.apache.org/jira/browse/GEODE-6309
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>
> One of this class's tests starts a locator and two servers, then it
> force-disconnects the locator and one of the servers & waits for the locator
> to reconnect. After that it starts a third server and expects it to join the
> cluster but this failed to happen in CI run 316:
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$46/1297938526.call
> in VM 3 running on Host 74139c18c4e4 with 5 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:533)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:390)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:239)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:232)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:218)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:71)
> Caused by:
> org.apache.geode.SystemConnectException: Unable to join the
> distributed system in 60032ms
> {noformat}
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/316]
> SHA: 654dc3bac3e50e66f33385bdbc38c88750061aa9
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6302) checkPom only checks dependencies, but not other Pom sections
[
https://issues.apache.org/jira/browse/GEODE-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-6302:
--
Labels: pull-request-available (was: )
> checkPom only checks dependencies, but not other Pom sections
> -
>
> Key: GEODE-6302
> URL: https://issues.apache.org/jira/browse/GEODE-6302
> Project: Geode
> Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
>
> Most notable, the {{dependencyManagement}} section can now change without the
> {{checkPom}} task failing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6303) Membership gets confused by multiple locators being specified by gfsh
[ https://issues.apache.org/jira/browse/GEODE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-6303: -- Labels: pull-request-available (was: ) > Membership gets confused by multiple locators being specified by gfsh > - > > Key: GEODE-6303 > URL: https://issues.apache.org/jira/browse/GEODE-6303 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > > I started a locator using gfsh and a gemfire.properties file that specified > that locator. > gfsh start locator --name=locator1 --properties-file=$PWD/gemfire.properties > gemfire.properties: > locators=trout.gemstone.com[30015] > locator-wait-time=120 > jmx-manager-start=true > jmx-manager-port=30016 > log-level=info > statistic-sampling-enabled=true > statistic-sample-rate=6 > max-wait-time-reconnect=5000 > log-level=fine > > Log files show that the locator was given two addresses in its "locators" > setting. One was the address I had in my gemfire.properties file and the > other was the same but using its numeric IPv4 address. > locators=trout.gemstone.com[30015],10.118.26.122[30015] > > Logs show that both of these addresses were contacted during startup and this > caused the locator to take more time starting up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6303) Membership gets confused by multiple locators being specified by gfsh
[ https://issues.apache.org/jira/browse/GEODE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749285#comment-16749285 ] ASF subversion and git services commented on GEODE-6303: Commit 106200b893a4d20ef988b38cdb4d0114000dab18 in geode's branch refs/heads/feature/GEODE-6303 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=106200b ] GEODE-6303 Membership gets confused by multiple locators being specified by gfsh Added canonicalization of locator addresses so that duplicate entries in the "locators" setting are ignored. > Membership gets confused by multiple locators being specified by gfsh > - > > Key: GEODE-6303 > URL: https://issues.apache.org/jira/browse/GEODE-6303 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > I started a locator using gfsh and a gemfire.properties file that specified > that locator. > gfsh start locator --name=locator1 --properties-file=$PWD/gemfire.properties > gemfire.properties: > locators=trout.gemstone.com[30015] > locator-wait-time=120 > jmx-manager-start=true > jmx-manager-port=30016 > log-level=info > statistic-sampling-enabled=true > statistic-sample-rate=6 > max-wait-time-reconnect=5000 > log-level=fine > > Log files show that the locator was given two addresses in its "locators" > setting. One was the address I had in my gemfire.properties file and the > other was the same but using its numeric IPv4 address. > locators=trout.gemstone.com[30015],10.118.26.122[30015] > > Logs show that both of these addresses were contacted during startup and this > caused the locator to take more time starting up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6310) upgrade classgraph version
Owen Nichols created GEODE-6310: --- Summary: upgrade classgraph version Key: GEODE-6310 URL: https://issues.apache.org/jira/browse/GEODE-6310 Project: Geode Issue Type: Bug Components: locator Reporter: Owen Nichols Observed that file descriptor is rapidly increasing to a high value such 20K-30K during starting up a cacheserver process with embedded locator. Problem goes away when classgraph-4.0.6.jar is replaced with classgraph-4.6.7.jar. A previous attempt to update Geode's classgraph version (GEODE-5996) was reverted due to increased memory usage concerns. In latest classgraph, memory usage can now be controlled by limiting number of threads, so we should be able to more forward once again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6211) Geode Native C# Example (Exception Handling)
[ https://issues.apache.org/jira/browse/GEODE-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-6211: -- Labels: pull-request-available (was: ) > Geode Native C# Example (Exception Handling) > > > Key: GEODE-6211 > URL: https://issues.apache.org/jira/browse/GEODE-6211 > Project: Geode > Issue Type: Sub-task > Components: examples, native client >Reporter: Charlie Black >Priority: Major > Labels: pull-request-available > > As a user, I would like to see an example of how to handle a common exception > thrown by Geode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6311) Create OQL query benchmarks
nabarun created GEODE-6311: -- Summary: Create OQL query benchmarks Key: GEODE-6311 URL: https://issues.apache.org/jira/browse/GEODE-6311 Project: Geode Issue Type: Bug Components: benchmarks Reporter: nabarun Add a basic query benchmark. Variants of this benchmark should include: * With(out) index * With(out) partition -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6280) Create new public module for the Management API
[ https://issues.apache.org/jira/browse/GEODE-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749329#comment-16749329 ] ASF subversion and git services commented on GEODE-6280: Commit 9bb8579df6f9669fe45fce96b6c6b617598f141d in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9bb8579 ] GEODE-6280: Create new public module for the Management API (#3083) - This moves the classes under `org.apache.geode.cache.configuration` package into a public module: `geode-managament`. The intent is that this module will have no dependencies to `geode-core` but will allow consumers to perform administration tasks (creating regions, etc.). - `geode-core` will now depend on both `geode-management` as well as `geode-common` (transitively). Suggestions on how to improve these new dependencies are welcome. Signed-off-by: Peter Tran Signed-off-by: Aditya Anchuri > Create new public module for the Management API > --- > > Key: GEODE-6280 > URL: https://issues.apache.org/jira/browse/GEODE-6280 > Project: Geode > Issue Type: New Feature > Components: configuration >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > We will need a new public module for the Management API. This separate > module, once compiled, will produce a jar that developers can download (via > Maven or otherwise) to access the Management API. Thus it is required that > any dependencies we have that are currently "internal" need to be moved into > this public module. > h3. Acceptance Criteria > *Given* I am a java developer > *and* configured my `build.gradle` to pull down the Geode Management API > module > *When* I do a gradlew build > *Then* I can write a java application that uses components inside this module > *and* the module is self contained and does not have other geode dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4337) Geode Native C++ Example (Server-side function execution)
[ https://issues.apache.org/jira/browse/GEODE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749349#comment-16749349 ] ASF subversion and git services commented on GEODE-4337: Commit c6027af43b4358db9a968ab295d998f416d3a392 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c6027af ] GEODE-4337, GEODE-4346 Geode-native user guide: Document function execution examples > Geode Native C++ Example (Server-side function execution) > - > > Key: GEODE-4337 > URL: https://issues.apache.org/jira/browse/GEODE-4337 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 8h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4337) Geode Native C++ Example (Server-side function execution)
[ https://issues.apache.org/jira/browse/GEODE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749351#comment-16749351 ] ASF subversion and git services commented on GEODE-4337: Commit c2c3bdaea0ea172eb010f088cf8dd7c3ba0b9991 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c2c3bda ] GEODE-4337, GEODE-4346 improve formatting > Geode Native C++ Example (Server-side function execution) > - > > Key: GEODE-4337 > URL: https://issues.apache.org/jira/browse/GEODE-4337 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 8h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4346) Geode Native C# Example (Server-side function example)
[ https://issues.apache.org/jira/browse/GEODE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749352#comment-16749352 ] ASF subversion and git services commented on GEODE-4346: Commit c2c3bdaea0ea172eb010f088cf8dd7c3ba0b9991 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c2c3bda ] GEODE-4337, GEODE-4346 improve formatting > Geode Native C# Example (Server-side function example) > -- > > Key: GEODE-4346 > URL: https://issues.apache.org/jira/browse/GEODE-4346 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 4h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4346) Geode Native C# Example (Server-side function example)
[ https://issues.apache.org/jira/browse/GEODE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749353#comment-16749353 ] ASF subversion and git services commented on GEODE-4346: Commit ec918b6192a417c935fca6f0ec99b3dcd0d30c80 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ec918b6 ] GEODE-4346 function execution: incorporate reviewer suggestions, flatten subnav hierarchy > Geode Native C# Example (Server-side function example) > -- > > Key: GEODE-4346 > URL: https://issues.apache.org/jira/browse/GEODE-4346 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 4h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4346) Geode Native C# Example (Server-side function example)
[ https://issues.apache.org/jira/browse/GEODE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749350#comment-16749350 ] ASF subversion and git services commented on GEODE-4346: Commit c6027af43b4358db9a968ab295d998f416d3a392 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c6027af ] GEODE-4337, GEODE-4346 Geode-native user guide: Document function execution examples > Geode Native C# Example (Server-side function example) > -- > > Key: GEODE-4346 > URL: https://issues.apache.org/jira/browse/GEODE-4346 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 4h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4346) Geode Native C# Example (Server-side function example)
[ https://issues.apache.org/jira/browse/GEODE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749354#comment-16749354 ] ASF subversion and git services commented on GEODE-4346: Commit ed8a29a5ae2f16d43285302cbb2c6a621631ab64 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ed8a29a ] Merge branch 'feature/GEODE-4346' into develop > Geode Native C# Example (Server-side function example) > -- > > Key: GEODE-4346 > URL: https://issues.apache.org/jira/browse/GEODE-4346 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 4h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6301) Add thread call stack support to ExecutorServiceRule
[ https://issues.apache.org/jira/browse/GEODE-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749368#comment-16749368 ] ASF subversion and git services commented on GEODE-6301: Commit f81d1854d33d31218d5131aa69b6c7c62c536333 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f81d185 ] GEODE-6301: Add call stack support to ExecutorServiceRule > Add thread call stack support to ExecutorServiceRule > > > Key: GEODE-6301 > URL: https://issues.apache.org/jira/browse/GEODE-6301 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > I need to add the ability to dump thread call stacks for use in a > RegressionTest for reproducing a deadlock with detailed failure message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6290) PdxInstance with an empty string as class name should not support class versioning
[ https://issues.apache.org/jira/browse/GEODE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749374#comment-16749374 ] ASF subversion and git services commented on GEODE-6290: Commit 8d97b01293b54f18526824cee5c4776b5a6df066 in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8d97b01 ] GEODE-6290: change PdxInstance.equals for empty class name (#3091) PdxInstance.equals will only act as if an instance has a field with the default value if the class name is not empty. If the class name is empty it will now require that both instances have all the same identity fields. If the class name is empty then neverDeserialize will be called automatically. > PdxInstance with an empty string as class name should not support class > versioning > -- > > Key: GEODE-6290 > URL: https://issues.apache.org/jira/browse/GEODE-6290 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Currently if you create a PdxInstanceFactory with the empty string as the > class name then the PdxInstances it creates support class versioning. Since > the empty string is not a class, these PdxInstances should not support class > versioning. The only place this shows up is in PdxInstance.equal which allows > two instances with different identity fields to still be equal. It does this > if the one that has the identity field has the default value for it. > What should happen if you have two PdxInstances with the class name "", is > that they are only equal if the have all the same identity fields. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6290) PdxInstance with an empty string as class name should not support class versioning
[ https://issues.apache.org/jira/browse/GEODE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6290. - Resolution: Fixed Fix Version/s: 1.9.0 > PdxInstance with an empty string as class name should not support class > versioning > -- > > Key: GEODE-6290 > URL: https://issues.apache.org/jira/browse/GEODE-6290 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently if you create a PdxInstanceFactory with the empty string as the > class name then the PdxInstances it creates support class versioning. Since > the empty string is not a class, these PdxInstances should not support class > versioning. The only place this shows up is in PdxInstance.equal which allows > two instances with different identity fields to still be equal. It does this > if the one that has the identity field has the default value for it. > What should happen if you have two PdxInstances with the class name "", is > that they are only equal if the have all the same identity fields. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6272) the JDBC connector should use PDX instances instead of JSON for composite keys
[
https://issues.apache.org/jira/browse/GEODE-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749384#comment-16749384
]
ASF subversion and git services commented on GEODE-6272:
Commit 56fda39a8ab41fc9ffeddb3da13322eaa1516084 in geode's branch
refs/heads/feature/GEODE-6267 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=56fda39 ]
GEODE-6272: change jdbc to use pdx as keys instead of json (#3076)
Composite keys for the jdbc connector must now be PdxInstances created with
"neverDeserialize".
* added PdxInstanceFactory.neverDeserialize and PdxInstance.isDeserializable as
new external APIs.
* improved the InternalPdxInstance interface to include Sendable.
Also this interface is now implemented by the pdx enum classes.
So now all classes that implement PdxInstance also implement InternalPdxInstance
* getCacheObject is now on the InternalPdxInstance interface.
* getRawField is now in the InternalPdxInstance interface.
A method that was on PdxInstanceImpl but only used by AttributeDescriptor
and that did not use any PdxInstanceImpl data is now on AttributeDescriptor.
This also got rid of a singleton lookup of the cache.
* removed unused FieldNotFoundInPdxVersion
* removed PdxFieldNotFoundException
> the JDBC connector should use PDX instances instead of JSON for composite keys
> --
>
> Key: GEODE-6272
> URL: https://issues.apache.org/jira/browse/GEODE-6272
> Project: Geode
> Issue Type: Improvement
> Components: docs, extensions
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> *As a* GemFire user with composite keys
> *I want to* to replace JSON with PDX for these keys
> *so that I can* support any order for the keys and have minimal memory impact.
>
> *Acceptance Criteria:*
> *Given* a jdbc-mapping uses a composite key
> *When* I do CRUD operations on data in the region
> *Then* I must specify the key as a "stable" PDX instance that contains fields
> that match those specified by {{--id}}.
> *Given* an existing cache with a jdbc-mapping that uses a composite key
> *When* I want to specify a composite key for a CRUD operation
> *Then* I have a method on the cache to create a "stable" PDX instance.
> *Given* an existing cache with a jdbc-mapping that uses a composite key
> *When* I want to specify a composite key for a CRUD operation
> *Then* I have a method on the cache to create a "stable" PDX instance and the
> order of fields in the composite key doesn't matter.
> *Given* an existing cache with pdx-read-serialized is set to false
> *When* I do an operation that triggers deserialization of a "stable" PDX
> instance
> *Then* the "stable" PDX instance will be deserialized as the same "stable"
> PDX instance.
> *Given* a "stable" PDX instance
> *When* I call its getObject method
> *Then* it will return the same "stable" PDX instance.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6267) Subjects are not logged out when a client departs causing a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749386#comment-16749386
]
ASF subversion and git services commented on GEODE-6267:
Commit 280d6a13f35a8e05ff659b034cd54a118d71bbd8 in geode's branch
refs/heads/feature/GEODE-6267 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=280d6a1 ]
GEODE-6267: Logged out subject
> Subjects are not logged out when a client departs causing a memory leak
> ---
>
> Key: GEODE-6267
> URL: https://issues.apache.org/jira/browse/GEODE-6267
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a client with security enabled connects to a server, the
> IntegratedSecurityService logs in a Subject. This causes a SimpleSession to
> be created.
> The Subject is stored in ClientUserAuths.uniqueIdVsSubject.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:42.993 PST server1 Thread 0> tid=0x4e] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.newSessionInstance(DefaultSessionManager.java:163)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.doCreateSession(DefaultSessionManager.java:154)
> at
> org.apache.shiro.session.mgt.AbstractValidatingSessionManager.createSession(AbstractValidatingSessionManager.java:136)
> at
> org.apache.shiro.session.mgt.AbstractNativeSessionManager.start(AbstractNativeSessionManager.java:99)
> at
> org.apache.shiro.mgt.SessionsSecurityManager.start(SessionsSecurityManager.java:152)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:336)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:312)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.mergePrincipals(DefaultSubjectDAO.java:204)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.saveToSession(DefaultSubjectDAO.java:166)
> at org.apache.shiro.mgt.DefaultSubjectDAO.save(DefaultSubjectDAO.java:147)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.save(DefaultSecurityManager.java:383)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:350)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:183)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:283)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:139)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.verifyCredentials(HandShake.java:1688)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.setCredentials(ServerConnection.java:1044)
> at
> org.apache.geode.internal.cache.tier.sockets.command.PutUserCredentials.cmdExecute(PutUserCredentials.java:52)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:163)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:797)
> at
> org.apache.geode.internal.cache.tier.sockets.LegacyServerConnection.doOneMessage(LegacyServerConnection.java:85)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:641)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> When the client disconnects, the ClientUserAuths is cleaned up (in cleanup),
> but the Subjects are not logged out.
> With subscription-enabled=true, an additional Subject is created and stored
> in the CacheClientProxy subject. This Subject is not logged out either.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:43.023 PST server1 Thread 0> tid=0x52] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.apache.shiro.session.mgt.D
[jira] [Commented] (GEODE-6267) Subjects are not logged out when a client departs causing a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749387#comment-16749387
]
ASF subversion and git services commented on GEODE-6267:
Commit 6aab53ec3389c5e65041b07b70073ecc9cb90925 in geode's branch
refs/heads/feature/GEODE-6267 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6aab53e ]
GEODE-6267: Added annotations and cleaned up test code
> Subjects are not logged out when a client departs causing a memory leak
> ---
>
> Key: GEODE-6267
> URL: https://issues.apache.org/jira/browse/GEODE-6267
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a client with security enabled connects to a server, the
> IntegratedSecurityService logs in a Subject. This causes a SimpleSession to
> be created.
> The Subject is stored in ClientUserAuths.uniqueIdVsSubject.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:42.993 PST server1 Thread 0> tid=0x4e] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.newSessionInstance(DefaultSessionManager.java:163)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.doCreateSession(DefaultSessionManager.java:154)
> at
> org.apache.shiro.session.mgt.AbstractValidatingSessionManager.createSession(AbstractValidatingSessionManager.java:136)
> at
> org.apache.shiro.session.mgt.AbstractNativeSessionManager.start(AbstractNativeSessionManager.java:99)
> at
> org.apache.shiro.mgt.SessionsSecurityManager.start(SessionsSecurityManager.java:152)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:336)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:312)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.mergePrincipals(DefaultSubjectDAO.java:204)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.saveToSession(DefaultSubjectDAO.java:166)
> at org.apache.shiro.mgt.DefaultSubjectDAO.save(DefaultSubjectDAO.java:147)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.save(DefaultSecurityManager.java:383)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:350)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:183)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:283)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:139)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.verifyCredentials(HandShake.java:1688)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.setCredentials(ServerConnection.java:1044)
> at
> org.apache.geode.internal.cache.tier.sockets.command.PutUserCredentials.cmdExecute(PutUserCredentials.java:52)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:163)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:797)
> at
> org.apache.geode.internal.cache.tier.sockets.LegacyServerConnection.doOneMessage(LegacyServerConnection.java:85)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:641)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> When the client disconnects, the ClientUserAuths is cleaned up (in cleanup),
> but the Subjects are not logged out.
> With subscription-enabled=true, an additional Subject is created and stored
> in the CacheClientProxy subject. This Subject is not logged out either.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:43.023 PST server1 Thread 0> tid=0x52] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.ap
[jira] [Commented] (GEODE-6187) describe jdbc-mapping should show if mapping is synchronous or not
[ https://issues.apache.org/jira/browse/GEODE-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749385#comment-16749385 ] ASF subversion and git services commented on GEODE-6187: Commit f38389928e575cf2d18825c93ac4f69b7edae3c9 in geode's branch refs/heads/feature/GEODE-6267 from BenjaminPerryRoss [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f383899 ] GEODE-6187: Added sorting and hid empty attributes for DescribeMappingCommand (#3079) Co-authored-by: Ben Ross Co-authored-by: Rob Day-Reynolds > describe jdbc-mapping should show if mapping is synchronous or not > -- > > Key: GEODE-6187 > URL: https://issues.apache.org/jira/browse/GEODE-6187 > Project: Geode > Issue Type: Improvement > Components: extensions, gfsh >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When a jdbc-mapping is created it is marked as synchronous or async. The > describe jdbc-mapping should also show this information. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6267) Subjects are not logged out when a client departs causing a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749388#comment-16749388
]
ASF subversion and git services commented on GEODE-6267:
Commit 80c82f43ebac081fdfbadb0a001c48810de381ab in geode's branch
refs/heads/feature/GEODE-6267 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=80c82f4 ]
GEODE-6267: Modified test to wait for ServerConnections and CacheClientProxy to
be closed
> Subjects are not logged out when a client departs causing a memory leak
> ---
>
> Key: GEODE-6267
> URL: https://issues.apache.org/jira/browse/GEODE-6267
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a client with security enabled connects to a server, the
> IntegratedSecurityService logs in a Subject. This causes a SimpleSession to
> be created.
> The Subject is stored in ClientUserAuths.uniqueIdVsSubject.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:42.993 PST server1 Thread 0> tid=0x4e] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSessionFactory.java:44)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.newSessionInstance(DefaultSessionManager.java:163)
> at
> org.apache.shiro.session.mgt.DefaultSessionManager.doCreateSession(DefaultSessionManager.java:154)
> at
> org.apache.shiro.session.mgt.AbstractValidatingSessionManager.createSession(AbstractValidatingSessionManager.java:136)
> at
> org.apache.shiro.session.mgt.AbstractNativeSessionManager.start(AbstractNativeSessionManager.java:99)
> at
> org.apache.shiro.mgt.SessionsSecurityManager.start(SessionsSecurityManager.java:152)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:336)
> at
> org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:312)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.mergePrincipals(DefaultSubjectDAO.java:204)
> at
> org.apache.shiro.mgt.DefaultSubjectDAO.saveToSession(DefaultSubjectDAO.java:166)
> at org.apache.shiro.mgt.DefaultSubjectDAO.save(DefaultSubjectDAO.java:147)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.save(DefaultSecurityManager.java:383)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:350)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:183)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:283)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:139)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.verifyCredentials(HandShake.java:1688)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.setCredentials(ServerConnection.java:1044)
> at
> org.apache.geode.internal.cache.tier.sockets.command.PutUserCredentials.cmdExecute(PutUserCredentials.java:52)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:163)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:797)
> at
> org.apache.geode.internal.cache.tier.sockets.LegacyServerConnection.doOneMessage(LegacyServerConnection.java:85)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:641)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> When the client disconnects, the ClientUserAuths is cleaned up (in cleanup),
> but the Subjects are not logged out.
> With subscription-enabled=true, an additional Subject is created and stored
> in the CacheClientProxy subject. This Subject is not logged out either.
> Here is a stack showing the SimpleSession creation:
> {noformat}
> [warning 2019/01/08 18:02:43.023 PST server1 Thread 0> tid=0x52] SimpleSession. invoked:
> java.lang.Exception
> at org.apache.shiro.session.mgt.SimpleSession.(SimpleSession.java:99)
> at
> org.apache.shiro.session.mgt.SimpleSessionFactory.createSession(SimpleSes
[jira] [Updated] (GEODE-6311) Create OQL query benchmarks
[ https://issues.apache.org/jira/browse/GEODE-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-6311: -- Labels: pull-request-available (was: ) > Create OQL query benchmarks > --- > > Key: GEODE-6311 > URL: https://issues.apache.org/jira/browse/GEODE-6311 > Project: Geode > Issue Type: Bug > Components: benchmarks >Reporter: nabarun >Priority: Major > Labels: pull-request-available > > Add a basic query benchmark. Variants of this benchmark should include: > * With(out) index > * With(out) partition -- This message was sent by Atlassian JIRA (v7.6.3#76005)
