[jira] [Commented] (GEODE-7270) WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
[
https://issues.apache.org/jira/browse/GEODE-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943267#comment-16943267
]
Barrett Oglesby commented on GEODE-7270:
The test is not waiting long enough for the locator exchange.
It starts 3 locators in 3 different distributed systems, then verifies each
site knows about the other.
It does this by comparing its known locators to the exchanged ones.
It gets the exchanged locator info like:
{noformat}
Map> allSiteMetaData = ((InternalLocator)
locator).getLocatorMembershipListener().getAllLocatorsInfo();
{noformat}
Then it iterates the known locators does and attempts to stream them:
{noformat}
for (Map.Entry> entry :
dsIdToLocatorAddresses.entrySet()) {
Set foundLocatorIds =
allSiteMetaData.get(entry.getKey());
final Set foundLocators = foundLocatorIds.stream()
{noformat}
If the allSiteMetaData doesn't contain the entry for the key yet, it fails with
an NPE.
Here is the output from the test:
Locators vm0 and vm1 start and vm1 exchanges locator information with vm0:
{noformat}
[vm0] [info 2019/10/02 17:10:58.909 GMT
tid=0x20] Listening on port 22506 bound on address localhost/127.0.0.1
[vm1] [info 2019/10/02 17:10:59.046 GMT
tid=0x20] Listening on port 27503 bound on address localhost/127.0.0.1
[vm1] [info 2019/10/02 17:10:59.201 GMT
tid=0x102] Locator discovery task exchanged locator information
localhost[27503] with localhost[22506]: {1=[localhost[22506]],
2=[localhost[27503]]}.
{noformat}
Locator vm2 starts, but before it exchanges locator information with vm0 and
vm1, vm0 throws the NPE:
{noformat}
[vm2] [info 2019/10/02 17:10:59.231 GMT
tid=0x20] Listening on port 21253 bound on address localhost/127.0.0.1
[vm0] [info 2019/10/02 17:10:59.423 GMT
tid=0x20] Got result: EXCEPTION_OCCURRED
[vm0] java.lang.NullPointerException
[vm0] at
org.apache.geode.internal.cache.wan.WANTestBase.lambda$checkAllSiteMetaData$21(WANTestBase.java:3027)
[vm0] at
org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
[vm0] at
org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:192)
[vm0] at
org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:179)
[vm0] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[vm0] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[vm0] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[vm0] at java.lang.Thread.run(Thread.java:748)
{noformat}
Then vm2 exchanges locator information with vm0 and vm1:
{noformat}
[vm2] [info 2019/10/02 17:10:59.452 GMT
tid=0x14e] Locator discovery task exchanged locator information
localhost[21253] with localhost[27503]: {1=[localhost[22506]],
2=[localhost[27503]], 3=[localhost[21253]]}.
{noformat}
The output should look like below. I added the logging for
WANTestBase.checkAllSiteMetaData. In this test, both vm1 and vm2 exchanged
locator information before checkAllSiteMetaData was invoked.
{noformat}
[vm0] [info 2019/10/02 17:30:45.590 PDT
tid=0x12] Listening on port 22500 bound on address localhost/127.0.0.1
[vm1] [info 2019/10/02 17:30:46.602 PDT
tid=0x12] Listening on port 27499 bound on address localhost/127.0.0.1
[vm1] [info 2019/10/02 17:30:47.020 PDT
tid=0x2d] Locator discovery task exchanged locator information localhost[27499]
with localhost[22500]: {1=[localhost[22500]], 2=[localhost[27499]]}.
[vm2] [info 2019/10/02 17:30:47.654 PDT
tid=0x12] Listening on port 21250 bound on address localhost/127.0.0.1
[vm2] [info 2019/10/02 17:30:48.043 PDT
tid=0x2d] Locator discovery task exchanged locator information localhost[21250]
with localhost[27499]: {1=[localhost[22500]], 2=[localhost[27499]],
3=[localhost[21250]]}.
[vm0] [info 2019/10/02 17:30:48.171 PDT tid=0x31]
WANTestBase.checkAllSiteMetaData allSiteMetaData={1=[localhost[22500]],
2=[localhost[27499]], 3=[localhost[21250]]}
[vm1] [info 2019/10/02 17:30:48.296 PDT tid=0x32]
WANTestBase.checkAllSiteMetaData allSiteMetaData={1=[localhost[22500]],
2=[localhost[27499]], 3=[localhost[21250]]}
[vm2] [info 2019/10/02 17:30:48.422 PDT tid=0x32]
WANTestBase.checkAllSiteMetaData allSiteMetaData={1=[localhost[22500]],
2=[localhost[27499]], 3=[localhost[21250]]}
{noformat}
> WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
> ---
>
> Key: GEODE-7270
> URL: https://issues.apache.org/jira/browse/GEODE-7270
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
>
> Wa
[jira] [Commented] (GEODE-7271) AlterRuntimeCommandDUnitTest.alterLogFileSizeLimit_changesConfigOnAllServers(true) [0] failed
[
https://issues.apache.org/jira/browse/GEODE-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943239#comment-16943239
]
Mark Hanson commented on GEODE-7271:
Failure occurs here in ExtensionClusterConfigurationDUnitTest >
testCreateExtensions as well.
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1139]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0175/test-results/distributedTest/1570058273/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0175/test-artifacts/1570058273/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0175.tgz
> AlterRuntimeCommandDUnitTest.alterLogFileSizeLimit_changesConfigOnAllServers(true)
> [0] failed
> --
>
> Key: GEODE-7271
> URL: https://issues.apache.org/jira/browse/GEODE-7271
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
>
> AlterRuntimeCommandDUnitTest.alterLogFileSizeLimit_changesConfigOnAllServers(true)
> [0] failed failed for JDK11.
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1129
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-results/distributedTest/1570042937/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-artifacts/1570042937/distributedtestfiles-OpenJDK11-1.11.0-SNAPSHOT.0174.tgz]
>
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 41[fatal 2019/10/02 17:08:53.388 GMT
> tid=3354] Uncaught exception in thread
> Thread[FederatingManager4,5,RMI Runtime]
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/_monitoringRegion_172.17.0.2441003';scope=DISTRIBUTED_NO_ACK';dataPolicy=REPLICATE]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7293)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2748)
> at
> org.apache.geode.internal.cache.LocalRegion.entrySet(LocalRegion.java:1905)
> at
> org.apache.geode.internal.cache.LocalRegion.entrySet(LocalRegion.java:8328)
> at
> org.apache.geode.management.internal.MBeanProxyFactory.removeAllProxies(MBeanProxyFactory.java:153)
> at
> org.apache.geode.management.internal.FederatingManager.removeMemberArtifacts(FederatingManager.java:215)
> at
> org.apache.geode.management.internal.FederatingManager.access$000(FederatingManager.java:67)
> at
> org.apache.geode.management.internal.FederatingManager$RemoveMemberTask.run(FederatingManager.java:564)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:380)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:193)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:148)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at
> junitparams.internal.ParameterisedTestMethodRunner.runMethodInvoker(ParameterisedTestMethodRunner.java:47)
> at
> junitparams.internal.ParameterisedTestMethodRunner.runTestMethod(ParameterisedTestMethodRunner.java:40)
> at
> junitparams.internal.ParameterisedTestClassRunner.runParameterisedTest(ParameterisedTestClassRunner.java:146)
> at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:446)
> at junitparams.JUni
[jira] [Updated] (GEODE-7261) Geode V1 admin rest does not start with Spring 5.x jars on the classpath
[
https://issues.apache.org/jira/browse/GEODE-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-7261:
--
Affects Version/s: 1.11.0
1.10.0
> Geode V1 admin rest does not start with Spring 5.x jars on the classpath
>
>
> Key: GEODE-7261
> URL: https://issues.apache.org/jira/browse/GEODE-7261
> Project: Geode
> Issue Type: Bug
> Components: gfsh, rest (admin)
>Affects Versions: 1.9.0, 1.9.1, 1.10.0, 1.11.0
>Reporter: Jens Deppe
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The geode-web war includes several spring jars, but does not include
> {{spring-core}}. With Jetty debug logging enabled we can see the following
> error:
> {noformat}
> [vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
> org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
> [vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
> [vm0] at java.lang.ClassLoader.defineClass1(Native Method)
> [vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> [vm0] at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> [vm0] at
> java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> [vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> {noformat}
> In addition, the war file also include {{commons-logging}} which causes the
> war logging to be redirected to stderr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7271) AlterRuntimeCommandDUnitTest.alterLogFileSizeLimit_changesConfigOnAllServers(true) [0] failed
Mark Hanson created GEODE-7271:
--
Summary:
AlterRuntimeCommandDUnitTest.alterLogFileSizeLimit_changesConfigOnAllServers(true)
[0] failed
Key: GEODE-7271
URL: https://issues.apache.org/jira/browse/GEODE-7271
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Mark Hanson
AlterRuntimeCommandDUnitTest.alterLogFileSizeLimit_changesConfigOnAllServers(true)
[0] failed failed for JDK11.
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1129
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-results/distributedTest/1570042937/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-artifacts/1570042937/distributedtestfiles-OpenJDK11-1.11.0-SNAPSHOT.0174.tgz]
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 41[fatal 2019/10/02 17:08:53.388 GMT
tid=3354] Uncaught exception in thread
Thread[FederatingManager4,5,RMI Runtime]
org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/_monitoringRegion_172.17.0.2441003';scope=DISTRIBUTED_NO_ACK';dataPolicy=REPLICATE]
at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7293)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2748)
at
org.apache.geode.internal.cache.LocalRegion.entrySet(LocalRegion.java:1905)
at
org.apache.geode.internal.cache.LocalRegion.entrySet(LocalRegion.java:8328)
at
org.apache.geode.management.internal.MBeanProxyFactory.removeAllProxies(MBeanProxyFactory.java:153)
at
org.apache.geode.management.internal.FederatingManager.removeMemberArtifacts(FederatingManager.java:215)
at
org.apache.geode.management.internal.FederatingManager.access$000(FederatingManager.java:67)
at
org.apache.geode.management.internal.FederatingManager$RemoveMemberTask.run(FederatingManager.java:564)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:380)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:193)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:148)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at
junitparams.internal.ParameterisedTestMethodRunner.runMethodInvoker(ParameterisedTestMethodRunner.java:47)
at
junitparams.internal.ParameterisedTestMethodRunner.runTestMethod(ParameterisedTestMethodRunner.java:40)
at
junitparams.internal.ParameterisedTestClassRunner.runParameterisedTest(ParameterisedTestClassRunner.java:146)
at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:446)
at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(S
[jira] [Created] (GEODE-7270) WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
Mark Hanson created GEODE-7270:
--
Summary: WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
Key: GEODE-7270
URL: https://issues.apache.org/jira/browse/GEODE-7270
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Mark Hanson
WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY failed with a Null
Pointer Exception.
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1138]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-results/distributedTest/1570043011/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-artifacts/1570043011/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0174.tgz]
{noformat}
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest$$Lambda$172/1647741944.run
in VM 0 running on Host 1cafba0ee536 with 8 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.test_TK_Recognises_LN_AND_NY(WanAutoDiscoveryDUnitTest.java:228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118)
at sun.reflect.NativeMethodAccessorI
[jira] [Updated] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick Cavender updated GEODE-7258:
-
Affects Version/s: 1.10.0
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.10.0
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Attachments: runsWithFineLevelLogging.zip
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> 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)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:379)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:658)
> ... 6 more
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create
> a new connection to s
[jira] [Commented] (GEODE-7227) ClassName attributes do not work with v2 rest api
[ https://issues.apache.org/jira/browse/GEODE-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943159#comment-16943159 ] ASF subversion and git services commented on GEODE-7227: Commit 42432eaf96bdb29d8648aa04b43d1c6abd8bba8a in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=42432ea ] GEODE-7227: Add default constructor to ClassName (#4111) Changed PdxManagementTest to include a ClassName attribute which caused the test to fail. Added default constructor to ClassName so that it can be serialized and test now passes. > ClassName attributes do not work with v2 rest api > - > > Key: GEODE-7227 > URL: https://issues.apache.org/jira/browse/GEODE-7227 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.10.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.11.0 > > Time Spent: 50m > Remaining Estimate: 0h > > If you try to specify a ClassName attribute with the v2 rest api, by calling > Pdx.setPdxSerializer or GatewayReceiver.setGatewayTransportFilters then an > exception will occur saying it could not create an instance of ClassName. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7227) ClassName attributes do not work with v2 rest api
[ https://issues.apache.org/jira/browse/GEODE-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-7227. - Fix Version/s: 1.11.0 Resolution: Fixed > ClassName attributes do not work with v2 rest api > - > > Key: GEODE-7227 > URL: https://issues.apache.org/jira/browse/GEODE-7227 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.10.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.11.0 > > Time Spent: 50m > Remaining Estimate: 0h > > If you try to specify a ClassName attribute with the v2 rest api, by calling > Pdx.setPdxSerializer or GatewayReceiver.setGatewayTransportFilters then an > exception will occur saying it could not create an instance of ClassName. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943146#comment-16943146
]
ASF subversion and git services commented on GEODE-7258:
Commit 10d5dcd8d9963da8df13e1af0cb7746bb59cd04f in geode's branch
refs/heads/develop from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=10d5dcd ]
GEODE-7258: Pulling the failing test while fixing (#4110)
GEODE-7258: Removing a failing test unitl fixed
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Attachments: runsWithFineLevelLogging.zip
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> 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)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
> org.apache.geode.internal.cache.execute.ServerRegion
[jira] [Commented] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943147#comment-16943147
]
ASF subversion and git services commented on GEODE-7258:
Commit 10d5dcd8d9963da8df13e1af0cb7746bb59cd04f in geode's branch
refs/heads/develop from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=10d5dcd ]
GEODE-7258: Pulling the failing test while fixing (#4110)
GEODE-7258: Removing a failing test unitl fixed
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Attachments: runsWithFineLevelLogging.zip
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> 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)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
> org.apache.geode.internal.cache.execute.ServerRegion
[jira] [Resolved] (GEODE-7134) Reduce overhead of PartitionedRegion.executeOnBucketSet
[
https://issues.apache.org/jira/browse/GEODE-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivanac resolved GEODE-7134.
-
Resolution: Fixed
> Reduce overhead of PartitionedRegion.executeOnBucketSet
> ---
>
> Key: GEODE-7134
> URL: https://issues.apache.org/jira/browse/GEODE-7134
> Project: Geode
> Issue Type: Improvement
> Components: functions, regions
>Reporter: Jacob Barrett
>Assignee: Mario Ivanac
>Priority: Major
> Labels: needs-review, performance, pull-request-available
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> {{PartitionedRegion.executeOnBucketSet}} spends 56% of function executions
> CPU time comparing and pruning bucket sets. It also accounts for 89% of the
> transient object allocation during function execution.
> Given that bucket sets are sets of integers let's look for a more suitable
> implementation of set operations on integers. Consider {{int[]}} as set of
> integers too reduce CPU and transient object allocations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7269) Benchmarks failure
[
https://issues.apache.org/jira/browse/GEODE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7269:
--
Assignee: Mark Hanson
> Benchmarks failure
> --
>
> Key: GEODE-7269
> URL: https://issues.apache.org/jira/browse/GEODE-7269
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Mark Hanson
>Assignee: Mark Hanson
>Priority: Major
>
> Benchmarks failed in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/607]
>
> {noformat}
> > Task :harness:analyzeRun
> Running analyzer
> Comparing test result at
> /tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/branch/benchmarks_20191002113518
> to baseline at
> /tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/baseline/benchmarks_20191002092613
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
> average ops/second Baseline:165126.55 Test:163322.19
> Difference: -1.1%
>ops/second standard error Baseline: 481.54 Test: 394.45
> Difference: -18.1%
>ops/second standard deviation Baseline: 8326.61 Test: 6832.03
> Difference: -17.9%
> YS 99th percentile latency Baseline: 1906.00 Test: 1905.00
> Difference: -0.1%
> median latency Baseline:633855.00 Test:630271.00
> Difference: -0.6%
> 90th percentile latency Baseline: 1326079.00 Test: 1367039.00
> Difference: +3.1%
> 99th percentile latency Baseline: 4591615.00 Test: 4644863.00
> Difference: +1.2%
>99.9th percentile latency Baseline: 1535.00 Test: 16809983.00
> Difference: +9.4%
> average latency Baseline:871151.53 Test:880810.13
> Difference: +1.1%
> latency standard deviation Baseline: 1050482.32 Test: 1100814.13
> Difference: +4.8%
> latency standard error Baseline: 149.28 Test: 157.30
> Difference: +5.4%
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
> average ops/second Baseline:459731.05 Test:453392.16
> Difference: -1.4%
>ops/second standard error Baseline: 394.19 Test: 332.85
> Difference: -15.6%
>ops/second standard deviation Baseline: 6816.12 Test: 5765.11
> Difference: -15.4%
> YS 99th percentile latency Baseline: 1405.00 Test: 1405.00
> Difference: +0.0%
> median latency Baseline:449791.00 Test:459519.00
> Difference: +2.2%
> 90th percentile latency Baseline:943615.00 Test:961023.00
> Difference: +1.8%
> 99th percentile latency Baseline: 3616767.00 Test: 3614719.00
> Difference: -0.1%
>99.9th percentile latency Baseline: 10559487.00 Test: 10551295.00
> Difference: -0.1%
> average latency Baseline:625412.03 Test:634121.49
> Difference: +1.4%
> latency standard deviation Baseline:788269.89 Test:788318.28
> Difference: +0.0%
> latency standard error Baseline:67.13 Test:67.60
> Difference: +0.7%
> org.apache.geode.benchmark.tests.PartitionedGetBenchmark
> average ops/second Baseline:841000.72 Test:828146.58
> Difference: -1.5%
>ops/second standard error Baseline: 558.63 Test: 507.87
> Difference: -9.1%
>ops/second standard deviation Baseline: 9659.55 Test: 8781.92
> Difference: -9.1%
> YS 99th percentile latency Baseline: 806.00 Test: 805.00
> Difference: -0.1%
> median latency Baseline:332287.00 Test:339967.00
> Difference: +2.3%
> 90th percentile latency Baseline:443391.00 Test:452351.00
> Difference: +2.0%
> 99th percentile latency Baseline: 2672639.00 Test: 2662399.00
> Difference: -0.4%
>99.9th percentile latency Baseline: 8089599.00 Test: 7974911.00
> Difference: -1.4%
> average latency Baseline:426878.72 Test:433532.06
> Difference: +1.6%
> latency standard deviation Baseline:546763.26 Test:542115.50
> Difference: -0.9%
> latency standard error Baseline:34.43 Test:34.40
> Difference: -0.1%
> org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark
> average ops/second Baseline:
[jira] [Assigned] (GEODE-7269) Benchmarks failure
[
https://issues.apache.org/jira/browse/GEODE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7269:
--
Assignee: Jacob Barrett (was: Mark Hanson)
> Benchmarks failure
> --
>
> Key: GEODE-7269
> URL: https://issues.apache.org/jira/browse/GEODE-7269
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Mark Hanson
>Assignee: Jacob Barrett
>Priority: Major
>
> Benchmarks failed in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/607]
>
> {noformat}
> > Task :harness:analyzeRun
> Running analyzer
> Comparing test result at
> /tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/branch/benchmarks_20191002113518
> to baseline at
> /tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/baseline/benchmarks_20191002092613
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
> average ops/second Baseline:165126.55 Test:163322.19
> Difference: -1.1%
>ops/second standard error Baseline: 481.54 Test: 394.45
> Difference: -18.1%
>ops/second standard deviation Baseline: 8326.61 Test: 6832.03
> Difference: -17.9%
> YS 99th percentile latency Baseline: 1906.00 Test: 1905.00
> Difference: -0.1%
> median latency Baseline:633855.00 Test:630271.00
> Difference: -0.6%
> 90th percentile latency Baseline: 1326079.00 Test: 1367039.00
> Difference: +3.1%
> 99th percentile latency Baseline: 4591615.00 Test: 4644863.00
> Difference: +1.2%
>99.9th percentile latency Baseline: 1535.00 Test: 16809983.00
> Difference: +9.4%
> average latency Baseline:871151.53 Test:880810.13
> Difference: +1.1%
> latency standard deviation Baseline: 1050482.32 Test: 1100814.13
> Difference: +4.8%
> latency standard error Baseline: 149.28 Test: 157.30
> Difference: +5.4%
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
> average ops/second Baseline:459731.05 Test:453392.16
> Difference: -1.4%
>ops/second standard error Baseline: 394.19 Test: 332.85
> Difference: -15.6%
>ops/second standard deviation Baseline: 6816.12 Test: 5765.11
> Difference: -15.4%
> YS 99th percentile latency Baseline: 1405.00 Test: 1405.00
> Difference: +0.0%
> median latency Baseline:449791.00 Test:459519.00
> Difference: +2.2%
> 90th percentile latency Baseline:943615.00 Test:961023.00
> Difference: +1.8%
> 99th percentile latency Baseline: 3616767.00 Test: 3614719.00
> Difference: -0.1%
>99.9th percentile latency Baseline: 10559487.00 Test: 10551295.00
> Difference: -0.1%
> average latency Baseline:625412.03 Test:634121.49
> Difference: +1.4%
> latency standard deviation Baseline:788269.89 Test:788318.28
> Difference: +0.0%
> latency standard error Baseline:67.13 Test:67.60
> Difference: +0.7%
> org.apache.geode.benchmark.tests.PartitionedGetBenchmark
> average ops/second Baseline:841000.72 Test:828146.58
> Difference: -1.5%
>ops/second standard error Baseline: 558.63 Test: 507.87
> Difference: -9.1%
>ops/second standard deviation Baseline: 9659.55 Test: 8781.92
> Difference: -9.1%
> YS 99th percentile latency Baseline: 806.00 Test: 805.00
> Difference: -0.1%
> median latency Baseline:332287.00 Test:339967.00
> Difference: +2.3%
> 90th percentile latency Baseline:443391.00 Test:452351.00
> Difference: +2.0%
> 99th percentile latency Baseline: 2672639.00 Test: 2662399.00
> Difference: -0.4%
>99.9th percentile latency Baseline: 8089599.00 Test: 7974911.00
> Difference: -1.4%
> average latency Baseline:426878.72 Test:433532.06
> Difference: +1.6%
> latency standard deviation Baseline:546763.26 Test:542115.50
> Difference: -0.9%
> latency standard error Baseline:34.43 Test:34.40
> Difference: -0.1%
> org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark
> averag
[jira] [Created] (GEODE-7269) Benchmarks failure
Mark Hanson created GEODE-7269:
--
Summary: Benchmarks failure
Key: GEODE-7269
URL: https://issues.apache.org/jira/browse/GEODE-7269
Project: Geode
Issue Type: Bug
Components: benchmarks
Reporter: Mark Hanson
Benchmarks failed in
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/607]
{noformat}
> Task :harness:analyzeRun
Running analyzer
Comparing test result at
/tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/branch/benchmarks_20191002113518
to baseline at
/tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/baseline/benchmarks_20191002092613
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
average ops/second Baseline:165126.55 Test:163322.19
Difference: -1.1%
ops/second standard error Baseline: 481.54 Test: 394.45
Difference: -18.1%
ops/second standard deviation Baseline: 8326.61 Test: 6832.03
Difference: -17.9%
YS 99th percentile latency Baseline: 1906.00 Test: 1905.00
Difference: -0.1%
median latency Baseline:633855.00 Test:630271.00
Difference: -0.6%
90th percentile latency Baseline: 1326079.00 Test: 1367039.00
Difference: +3.1%
99th percentile latency Baseline: 4591615.00 Test: 4644863.00
Difference: +1.2%
99.9th percentile latency Baseline: 1535.00 Test: 16809983.00
Difference: +9.4%
average latency Baseline:871151.53 Test:880810.13
Difference: +1.1%
latency standard deviation Baseline: 1050482.32 Test: 1100814.13
Difference: +4.8%
latency standard error Baseline: 149.28 Test: 157.30
Difference: +5.4%
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
average ops/second Baseline:459731.05 Test:453392.16
Difference: -1.4%
ops/second standard error Baseline: 394.19 Test: 332.85
Difference: -15.6%
ops/second standard deviation Baseline: 6816.12 Test: 5765.11
Difference: -15.4%
YS 99th percentile latency Baseline: 1405.00 Test: 1405.00
Difference: +0.0%
median latency Baseline:449791.00 Test:459519.00
Difference: +2.2%
90th percentile latency Baseline:943615.00 Test:961023.00
Difference: +1.8%
99th percentile latency Baseline: 3616767.00 Test: 3614719.00
Difference: -0.1%
99.9th percentile latency Baseline: 10559487.00 Test: 10551295.00
Difference: -0.1%
average latency Baseline:625412.03 Test:634121.49
Difference: +1.4%
latency standard deviation Baseline:788269.89 Test:788318.28
Difference: +0.0%
latency standard error Baseline:67.13 Test:67.60
Difference: +0.7%
org.apache.geode.benchmark.tests.PartitionedGetBenchmark
average ops/second Baseline:841000.72 Test:828146.58
Difference: -1.5%
ops/second standard error Baseline: 558.63 Test: 507.87
Difference: -9.1%
ops/second standard deviation Baseline: 9659.55 Test: 8781.92
Difference: -9.1%
YS 99th percentile latency Baseline: 806.00 Test: 805.00
Difference: -0.1%
median latency Baseline:332287.00 Test:339967.00
Difference: +2.3%
90th percentile latency Baseline:443391.00 Test:452351.00
Difference: +2.0%
99th percentile latency Baseline: 2672639.00 Test: 2662399.00
Difference: -0.4%
99.9th percentile latency Baseline: 8089599.00 Test: 7974911.00
Difference: -1.4%
average latency Baseline:426878.72 Test:433532.06
Difference: +1.6%
latency standard deviation Baseline:546763.26 Test:542115.50
Difference: -0.9%
latency standard error Baseline:34.43 Test:34.40
Difference: -0.1%
org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark
average ops/second Baseline: 1108020.75 Test: 1107517.03
Difference: -0.0%
ops/second standard error Baseline: 508.14 Test: 306.97
Difference: -39.6%
ops/second standard deviation Baseline: 8801.18 Test: 5307.94
Difference: -39.7%
YS 99th percentile latency Baseline: 902.00 Test: 902.00
Difference: +0.0%
median latency Baseline:27
[jira] [Updated] (GEODE-7261) Geode V1 admin rest does not start with Spring 5.x jars on the classpath
[
https://issues.apache.org/jira/browse/GEODE-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-7261:
---
Component/s: gfsh
> Geode V1 admin rest does not start with Spring 5.x jars on the classpath
>
>
> Key: GEODE-7261
> URL: https://issues.apache.org/jira/browse/GEODE-7261
> Project: Geode
> Issue Type: Bug
> Components: gfsh, rest (admin)
>Affects Versions: 1.9.0, 1.9.1
>Reporter: Jens Deppe
>Priority: Major
>
> The geode-web war includes several spring jars, but does not include
> {{spring-core}}. With Jetty debug logging enabled we can see the following
> error:
> {noformat}
> [vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
> org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
> [vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
> [vm0] at java.lang.ClassLoader.defineClass1(Native Method)
> [vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> [vm0] at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> [vm0] at
> java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> [vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> {noformat}
> In addition, the war file also include {{commons-logging}} which causes the
> war logging to be redirected to stderr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7268) Make gfsh alter region command similar to the API behavior
[ https://issues.apache.org/jira/browse/GEODE-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-7268: --- Summary: Make gfsh alter region command similar to the API behavior (was: Make gfsh alter command similar to the API behavior ) > Make gfsh alter region command similar to the API behavior > --- > > Key: GEODE-7268 > URL: https://issues.apache.org/jira/browse/GEODE-7268 > Project: Geode > Issue Type: Bug >Reporter: Nabarun Nag >Priority: Major > > * currently the gfsh command for alter region assigns the buckets to the > region, before starting with the PR update config. > * This is not what the API does while altering a region > * This was requirement from the Lucene reindex story but that feature > follows a different code path and will the be not affected if the assign > buckets command was removed from the gfsh command. > * This also results in soft hangs when there are a lot of regions and > gateway senders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7268) Make gfsh alter command similar to the API behavior
Nabarun Nag created GEODE-7268: -- Summary: Make gfsh alter command similar to the API behavior Key: GEODE-7268 URL: https://issues.apache.org/jira/browse/GEODE-7268 Project: Geode Issue Type: Bug Reporter: Nabarun Nag * currently the gfsh command for alter region assigns the buckets to the region, before starting with the PR update config. * This is not what the API does while altering a region * This was requirement from the Lucene reindex story but that feature follows a different code path and will the be not affected if the assign buckets command was removed from the gfsh command. * This also results in soft hangs when there are a lot of regions and gateway senders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7267) ClassName validation code should be in a validator or removed
Darrel Schneider created GEODE-7267: --- Summary: ClassName validation code should be in a validator or removed Key: GEODE-7267 URL: https://issues.apache.org/jira/browse/GEODE-7267 Project: Geode Issue Type: Bug Components: management Reporter: Darrel Schneider org.apache.geode.management.configuration.ClassName has a method isClassNameValid that is public and is called from the constructor to validate the class name. This validation should be reviewed for the v2 api. Should it be moved to a validator? Also does the management external apis need to expose it as a method users can call? Also should we be implementing code to verify the syntax of a legal java class name or deferring to the jvm for this? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7034) need to refactor the PeerTypeRegistration to be junit testable
[ https://issues.apache.org/jira/browse/GEODE-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans reassigned GEODE-7034: -- Assignee: Donal Evans > need to refactor the PeerTypeRegistration to be junit testable > -- > > Key: GEODE-7034 > URL: https://issues.apache.org/jira/browse/GEODE-7034 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Donal Evans >Priority: Major > > The PeerTypeRegistration has no junit test. We are using dunit test and > integration test to cover the code. > According to Darrel's suggestion, we should refactor it to be junit testable > and add junit tests for each components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7266) ClassName javadocs need to be cleaned up
Darrel Schneider created GEODE-7266: --- Summary: ClassName javadocs need to be cleaned up Key: GEODE-7266 URL: https://issues.apache.org/jira/browse/GEODE-7266 Project: Geode Issue Type: Bug Components: management Reporter: Darrel Schneider org.apache.geode.management.configuration.ClassName is used by the v2 management api. But the javadocs on it have references to gfsh and to the internal DeclarableTypeInstantiator even though it is not longer used by them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7227) ClassName attributes do not work with v2 rest api
[ https://issues.apache.org/jira/browse/GEODE-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-7227: --- Assignee: Darrel Schneider > ClassName attributes do not work with v2 rest api > - > > Key: GEODE-7227 > URL: https://issues.apache.org/jira/browse/GEODE-7227 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.10.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If you try to specify a ClassName attribute with the v2 rest api, by calling > Pdx.setPdxSerializer or GatewayReceiver.setGatewayTransportFilters then an > exception will occur saying it could not create an instance of ClassName. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7134) Reduce overhead of PartitionedRegion.executeOnBucketSet
[
https://issues.apache.org/jira/browse/GEODE-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942954#comment-16942954
]
ASF subversion and git services commented on GEODE-7134:
Commit f05074ae80134dad024674072c261638017939ef in geode's branch
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f05074a ]
GEODE-7134: Replace bucket Set with bucket int[] (#4002)
> Reduce overhead of PartitionedRegion.executeOnBucketSet
> ---
>
> Key: GEODE-7134
> URL: https://issues.apache.org/jira/browse/GEODE-7134
> Project: Geode
> Issue Type: Improvement
> Components: functions, regions
>Reporter: Jacob Barrett
>Assignee: Mario Ivanac
>Priority: Major
> Labels: needs-review, performance, pull-request-available
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> {{PartitionedRegion.executeOnBucketSet}} spends 56% of function executions
> CPU time comparing and pruning bucket sets. It also accounts for 89% of the
> transient object allocation during function execution.
> Given that bucket sets are sets of integers let's look for a more suitable
> implementation of set operations on integers. Consider {{int[]}} as set of
> integers too reduce CPU and transient object allocations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaojian Zhou updated GEODE-7258:
-
Labels: GeodeCommons (was: )
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Attachments: runsWithFineLevelLogging.zip
>
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> 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)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:379)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:658)
> ... 6 more
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create
> a new connection to server 38006782570a:24478
> 108 tests completed, 1 failed
> > Task :geode-lucene
[jira] [Updated] (GEODE-7205) sync wiki page of Cluster Management Service with Swagger page
[ https://issues.apache.org/jira/browse/GEODE-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gang Yan updated GEODE-7205: Description: #WHY there are a lot of stuff need to sync-up from Swagger page to wiki, Including but not limited to : - class - config --> configuration - links - group & groups - experies And we do not want to update the wiki page again and again, and also the more we delivered , the more update we need to publish on wiki page, so we need to find a way to generate wiki page from Swagger page in programming way. #WHAT there is a Swagger page and api-docs, everything is there, so we need to find a way to parse the swagger page to generate Wiki page. 1. find input 2. find output format on wiki 3. parse the input to output format was: ### WHY there are a lot of stuff need to sync-up from Swagger page to wiki, Including but not limited to : - class - config --> configuration - links - group & groups - experies And we do not want to update the wiki page again and again, and also the more we delivered , the more update we need to publish on wiki page, so we need to find a way to generate wiki page from Swagger page in programming way. ### WHAT there is a Swagger page and api-docs, everything is there, so we need to find a way to parse the swagger page to generate Wiki page. 1. find input 2. find output format on wiki 3. parse the input to output format > sync wiki page of Cluster Management Service with Swagger page > -- > > Key: GEODE-7205 > URL: https://issues.apache.org/jira/browse/GEODE-7205 > Project: Geode > Issue Type: Improvement > Components: management, rest (admin) >Reporter: Gang Yan >Priority: Major > > > #WHY > there are a lot of stuff need to sync-up from Swagger page to wiki, > Including but not limited to : > - class > - config --> configuration > - links > - group & groups > - experies > And we do not want to update the wiki page again and again, and also the more > we delivered , the more update we need to publish on wiki page, so we need to > find a way to generate wiki page from Swagger page in programming way. > #WHAT > there is a Swagger page and api-docs, everything is there, so we need to find > a way to parse the swagger page to generate Wiki page. > 1. find input > 2. find output format on wiki > 3. parse the input to output format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7205) sync wiki page of Cluster Management Service with Swagger page
[ https://issues.apache.org/jira/browse/GEODE-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gang Yan updated GEODE-7205: Description: ### WHY there are a lot of stuff need to sync-up from Swagger page to wiki, Including but not limited to : - class - config --> configuration - links - group & groups - experies And we do not want to update the wiki page again and again, and also the more we delivered , the more update we need to publish on wiki page, so we need to find a way to generate wiki page from Swagger page in programming way. ### WHAT there is a Swagger page and api-docs, everything is there, so we need to find a way to parse the swagger page to generate Wiki page. 1. find input 2. find output format on wiki 3. parse the input to output format was: there are a lot of stuff need to sync-up from Swagger page to wiki, Including but not limited to : class config --> configuration links group & groups > sync wiki page of Cluster Management Service with Swagger page > -- > > Key: GEODE-7205 > URL: https://issues.apache.org/jira/browse/GEODE-7205 > Project: Geode > Issue Type: Improvement > Components: management, rest (admin) >Reporter: Gang Yan >Priority: Major > > > ### WHY > there are a lot of stuff need to sync-up from Swagger page to wiki, > Including but not limited to : > - class > - config --> configuration > - links > - group & groups > - experies > And we do not want to update the wiki page again and again, and also the more > we delivered , the more update we need to publish on wiki page, so we need to > find a way to generate wiki page from Swagger page in programming way. > ### WHAT > there is a Swagger page and api-docs, everything is there, so we need to find > a way to parse the swagger page to generate Wiki page. > 1. find input > 2. find output format on wiki > 3. parse the input to output format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7257) Minimize test usage of log4j-core and log4j-core:tests
[ https://issues.apache.org/jira/browse/GEODE-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-7257. -- Fix Version/s: 1.11.0 Resolution: Fixed > Minimize test usage of log4j-core and log4j-core:tests > -- > > Key: GEODE-7257 > URL: https://issues.apache.org/jira/browse/GEODE-7257 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Fix For: 1.11.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The following test classes use log4j-core and log4j-core:tests but could > easily be reimplemented to not depend on log4j-core: > * ManagementRequestLoggingDUnitTest > * GfshParserAutoCompletionTest > * GoldenTestCase > These geode modules declare dependency on log4j-core and log4j-core:tests but > could remove it if the above files are changed: > * geode-junit > * geode-pulse > * geode-serialization > * geode-assembly -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6945) geode-managment should create its own set of configuration objects for IndexConfiguration
[ https://issues.apache.org/jira/browse/GEODE-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942942#comment-16942942 ] ASF subversion and git services commented on GEODE-6945: Commit a1f83ac437225404dc91eb2bb67e6b85ad885044 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a1f83ac ] GEODE-6945: remove deprecated types in v2 RegionType (#4108) * experimental api should not have deprecated apis. > geode-managment should create its own set of configuration objects for > IndexConfiguration > - > > Key: GEODE-6945 > URL: https://issues.apache.org/jira/browse/GEODE-6945 > Project: Geode > Issue Type: Sub-task > Components: management >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.11.0 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > IndexConfiguration > only add the supported attributes > modify the implementation of ConfigurationManager to do the bridging between > the configuration objects and xml domain objects -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7265) Avoid creating default locator VM when ClusterStartupRule is used
Jens Deppe created GEODE-7265: - Summary: Avoid creating default locator VM when ClusterStartupRule is used Key: GEODE-7265 URL: https://issues.apache.org/jira/browse/GEODE-7265 Project: Geode Issue Type: Improvement Components: tests Reporter: Jens Deppe It's not needed, so why create it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7265) Avoid creating default locator VM when ClusterStartupRule is used
[ https://issues.apache.org/jira/browse/GEODE-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-7265: - Assignee: Jens Deppe > Avoid creating default locator VM when ClusterStartupRule is used > - > > Key: GEODE-7265 > URL: https://issues.apache.org/jira/browse/GEODE-7265 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > > It's not needed, so why create it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7264) Jackson-databind vulnerabilities
Gang Yan created GEODE-7264: --- Summary: Jackson-databind vulnerabilities Key: GEODE-7264 URL: https://issues.apache.org/jira/browse/GEODE-7264 Project: Geode Issue Type: Bug Components: rest (admin) Reporter: Gang Yan In case it is by when the customer can expect a patch that addresses these vulnerabilities? [1] [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12814] [2] [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12384] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942917#comment-16942917
]
Joey McAllister commented on GEODE-7260:
+1 to contributing the Docker image. Great idea!
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942909#comment-16942909
]
Dave Barnes commented on GEODE-7260:
> BTW, do you think this Docker image I have done is something valuable to be
>contributed to Geode?
+1
Yes, Alberto, it's an excellent idea - makes it much easier for community
members to build their own docs to reflect recent and local changes.
The geode-native community did that - see geode-native/docs/docker and
geode-native/docs/README.md for more information. Also see the ticket that was
filed just yesterday, GEODE-7263: Geode Native: Dockerfile for building the
user guide needs updating.
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-7260.
-
Fix Version/s: 1.11.0
Resolution: Fixed
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942901#comment-16942901
]
ASF subversion and git services commented on GEODE-7260:
Commit a83f153a357c123bcf51199c99874c77f480f5ad in geode's branch
refs/heads/develop from Alberto Bustamante Reyes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a83f153 ]
GEODE-7260: Fix wrong statement in geode-book/README (#4109)
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6988) Implement JavaBeanAccessorMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Ramos updated GEODE-6988: -- Description: Implement the [JavaBeanAccessorMethodAuthorizer |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-JavaBeanAccessorMethodAuthorizer] class. * Make sure the class is immutable and thread safe. * Implement unit tests for the class and all of its methods. * Add comprehensive and clear documentation to the class and all its public methods so customers can use it without leaving their IDE. was: Implement the [JavaBeanAccessorBasedMethodAuthorizer |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-JavaBeanAccessorBasedMethodAuthorizer] class. * Make sure the class is immutable and thread safe. * Implement unit tests for the class and all of its methods. * Add comprehensive and clear documentation to the class and all its public methods so customers can use it without leaving their IDE. > Implement JavaBeanAccessorMethodAuthorizer > -- > > Key: GEODE-6988 > URL: https://issues.apache.org/jira/browse/GEODE-6988 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Priority: Major > Labels: GeodeCommons > > Implement the [JavaBeanAccessorMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-JavaBeanAccessorMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6987) Implement RegExMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Ramos updated GEODE-6987: -- Description: Implement the [RegExMethodAuthorizer |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegExMethodAuthorizer] class. * Make sure the class is immutable and thread safe. * Implement unit tests for the class and all of its methods. * Add comprehensive and clear documentation to the class and all its public methods so customers can use it without leaving their IDE. was: Implement the [RegexBasedMethodAuthorizer |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegexBasedMethodAuthorizer] class. * Make sure the class is immutable and thread safe. * Implement unit tests for the class and all of its methods. * Add comprehensive and clear documentation to the class and all its public methods so customers can use it without leaving their IDE. > Implement RegExMethodAuthorizer > --- > > Key: GEODE-6987 > URL: https://issues.apache.org/jira/browse/GEODE-6987 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons > > Implement the [RegExMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegExMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6988) Implement JavaBeanAccessorMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Ramos updated GEODE-6988: -- Summary: Implement JavaBeanAccessorMethodAuthorizer (was: Implement JavaBeanAccessorBasedMethodAuthorizer) > Implement JavaBeanAccessorMethodAuthorizer > -- > > Key: GEODE-6988 > URL: https://issues.apache.org/jira/browse/GEODE-6988 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Priority: Major > Labels: GeodeCommons > > Implement the [JavaBeanAccessorBasedMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-JavaBeanAccessorBasedMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6987) Implement RegExMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Ramos updated GEODE-6987: -- Summary: Implement RegExMethodAuthorizer (was: Implement RegExBasedMethodAuthorizer) > Implement RegExMethodAuthorizer > --- > > Key: GEODE-6987 > URL: https://issues.apache.org/jira/browse/GEODE-6987 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons > > Implement the [RegexBasedMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegexBasedMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6070) CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
[
https://issues.apache.org/jira/browse/GEODE-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942872#comment-16942872
]
Aaron Lindsey commented on GEODE-6070:
--
I tried looking at this yesterday. [~upthewaterspout]'s idea seems plausible,
but something I don't understand is: The code in ShutdownFunction.execute seems
to _wait_ until the cache is shutdown, _then_ send the reply. So it seems that
the shutdown would _always_ happen before the reply. Given that, I don't
understand why this test doesn't fail every time.
> CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
> --
>
> Key: GEODE-6070
> URL: https://issues.apache.org/jira/browse/GEODE-6070
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Priority: Major
> Labels: GeodeCommons
>
> Failed with stacktrace:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest
> > testShutdownAll FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 302
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.3(server-1:496):41002 started at Thu Nov
> 15 19:47:58 UTC 2018: Message distribution has terminated
> {noformat}
> Test results can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-results/distributedTest/1542315851/classes/org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest.html#testShutdownAll
>
> Test Artifacts can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-artifacts/1542315851/distributedtestfiles-OpenJDK8-1.9.0-build.158.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes updated GEODE-7260:
Labels: pull-request-available (was: )
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-7260:
---
Assignee: Alberto Bustamante Reyes
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942759#comment-16942759
]
Alberto Bustamante Reyes commented on GEODE-7260:
-
I agree with you that introducing a manual step is a waste of time. I was
thinking on publishing the documentation automatically. The thing is that the
requirement of installing ruby and bookbinder to generate the documentation
locally is something I dont like at all, so when I saw that sentece in the
README, I thought that maybe publishing the latest version of the documentation
was something done in the past.
Anyway, I have been able to generate a docker image with ruby and bookbinder
that automatically build and publish the user guide from your repo, so now I
dont see the utility of publishing the develop version of the user guide in the
web.
I will change the README and send the PR.
BTW, do you think this Docker image I have done is something valuable to be
contributed to Geode?
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Priority: Major
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6987) Implement RegExBasedMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Ramos updated GEODE-6987: -- Summary: Implement RegExBasedMethodAuthorizer (was: Implement RegexBasedMethodAuthorizer) > Implement RegExBasedMethodAuthorizer > > > Key: GEODE-6987 > URL: https://issues.apache.org/jira/browse/GEODE-6987 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons > > Implement the [RegexBasedMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegexBasedMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
