[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451604#comment-16451604
]
ASF subversion and git services commented on GEODE-925:
---
Commit 7c4c4e57cefcf49e2ea2a69250176c63ffcffc44 in geode's branch
refs/heads/feature/GEODE-5138 from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7c4c4e5 ]
Revert "GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up"
This reverts commit 9145fa352e84724dd21d598a855210c71340acfd.
Reverting due to spotless issue
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-5138) rename a stats for gateway sender with meaningful name
[ https://issues.apache.org/jira/browse/GEODE-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451607#comment-16451607 ] ASF subversion and git services commented on GEODE-5138: Commit 08262e5ec5986dad43254e778a07f308412c757c in geode's branch refs/heads/feature/GEODE-5138 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=08262e5 ] GEODE-5138: rename the gateway sender stats to a better name > rename a stats for gateway sender with meaningful name > -- > > Key: GEODE-5138 > URL: https://issues.apache.org/jira/browse/GEODE-5138 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Document team reviewed and suggest to use > EVENTS_DROPPED_DUE_TO_PRIMARY_SENDER_NOT_RUNNING: "Number of events dropped > because the primary gateway sender is not running." > instead of: > NOT_QUEUED_EVENTS_AT_YET_RUNNING_PRIMARY_SENDER: "Number of events not added > to primary queue due to sender yet running." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3451) Data inconsistency detected in distributed ack test on empty region
[
https://issues.apache.org/jira/browse/GEODE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451605#comment-16451605
]
ASF subversion and git services commented on GEODE-3451:
Commit 8020f37073ea08b6948d27a4d9220a1491532605 in geode's branch
refs/heads/feature/GEODE-5138 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8020f37 ]
GEODE-3451: add a flaky lable.
> Data inconsistency detected in distributed ack test on empty region
> ---
>
> Key: GEODE-3451
> URL: https://issues.apache.org/jira/browse/GEODE-3451
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Nick Reich
>Priority: Major
> Labels: ci, flaky
>
> {noformat}
> org.apache.geode.cache30.DistributedAckRegionCCEOffHeapDUnitTest >
> testConcurrentEventsOnEmptyRegion FAILED
> org.junit.ComparisonFailure: region contents are not consistent for
> cckey8 expected: but was:
> {noformat}
> Note: test failure was not readily reproduced
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4853) Remove serializer parameter in PdxWrapper constructor
[ https://issues.apache.org/jira/browse/GEODE-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-4853. --- Resolution: Fixed > Remove serializer parameter in PdxWrapper constructor > - > > Key: GEODE-4853 > URL: https://issues.apache.org/jira/browse/GEODE-4853 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Michael Oleske >Priority: Major > > The serializer is already registered with the TypeRegistry, so PdxWrapper can > just extract the serializer it needs from there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5059) AbstractRegionMap.basicPut should be refactored
[ https://issues.apache.org/jira/browse/GEODE-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5059: -- Labels: AbstractRegionMap pull-request-available (was: AbstractRegionMap) > AbstractRegionMap.basicPut should be refactored > --- > > Key: GEODE-5059 > URL: https://issues.apache.org/jira/browse/GEODE-5059 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: AbstractRegionMap, pull-request-available > > Recently the AbstractRegionMap.basicPut method was refactored into many > smaller methods that all take an instance of RegionMapPutContext. > These methods should be moved to another class (it could be named > RegionMapPut) and the RegionMapPutContext could go away since the > RegionMapPut instance could keep all the state of the put operation. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5082) Rolling Upgrade tests for Lucene reindex
[ https://issues.apache.org/jira/browse/GEODE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-5082: --- Issue Type: Sub-task (was: Bug) Parent: GEODE-3924 > Rolling Upgrade tests for Lucene reindex > > > Key: GEODE-5082 > URL: https://issues.apache.org/jira/browse/GEODE-5082 > Project: Geode > Issue Type: Sub-task > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario 1: > Status : The system has a new member and others which do not support reindex. > Action: The Apache Geode developer tries to create the index on the new > member (supports reindex) after the region has been created. > Accepted result : An exception must be thrown preventing the creation of the > lucene index. > > Scenario 2: > Status : The system has a mix of new members and old members which do not > support Lucene reindex. > Action: The Apache Geode developer creates the region on the new member, and > then creates the Lucene index. > The old members are now rolled to the new version which supports Lucene Index. > Create lucene index first on the freshly rolled members and then create > region. > Result: This operation must be successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5082) Rolling Upgrade tests for Lucene reindex
[ https://issues.apache.org/jira/browse/GEODE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-5082: --- Fix Version/s: (was: 1.7.0) > Rolling Upgrade tests for Lucene reindex > > > Key: GEODE-5082 > URL: https://issues.apache.org/jira/browse/GEODE-5082 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario 1: > Status : The system has a new member and others which do not support reindex. > Action: The Apache Geode developer tries to create the index on the new > member (supports reindex) after the region has been created. > Accepted result : An exception must be thrown preventing the creation of the > lucene index. > > Scenario 2: > Status : The system has a mix of new members and old members which do not > support Lucene reindex. > Action: The Apache Geode developer creates the region on the new member, and > then creates the Lucene index. > The old members are now rolled to the new version which supports Lucene Index. > Create lucene index first on the freshly rolled members and then create > region. > Result: This operation must be successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5082) Rolling Upgrade tests for Lucene reindex
[ https://issues.apache.org/jira/browse/GEODE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451399#comment-16451399 ] Diane Hardman commented on GEODE-5082: -- Note for docs: Scenario 2 described above is how Lucene indexing is supported today (since Geode 1.2.0) and should continue to work during a rolling upgrade. Scenario 1 is new behavior (ability to add a Lucene index on an existing region with data) and this will be blocked until the rolling upgrade is complete. In the code we detect that members in the cluster have different Geode versions and block adding the Lucene index until all members are at the same version. > Rolling Upgrade tests for Lucene reindex > > > Key: GEODE-5082 > URL: https://issues.apache.org/jira/browse/GEODE-5082 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario 1: > Status : The system has a new member and others which do not support reindex. > Action: The Apache Geode developer tries to create the index on the new > member (supports reindex) after the region has been created. > Accepted result : An exception must be thrown preventing the creation of the > lucene index. > > Scenario 2: > Status : The system has a mix of new members and old members which do not > support Lucene reindex. > Action: The Apache Geode developer creates the region on the new member, and > then creates the Lucene index. > The old members are now rolled to the new version which supports Lucene Index. > Create lucene index first on the freshly rolled members and then create > region. > Result: This operation must be successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5082) Rolling Upgrade tests for Lucene reindex
[ https://issues.apache.org/jira/browse/GEODE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5082: - Component/s: docs > Rolling Upgrade tests for Lucene reindex > > > Key: GEODE-5082 > URL: https://issues.apache.org/jira/browse/GEODE-5082 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario 1: > Status : The system has a new member and others which do not support reindex. > Action: The Apache Geode developer tries to create the index on the new > member (supports reindex) after the region has been created. > Accepted result : An exception must be thrown preventing the creation of the > lucene index. > > Scenario 2: > Status : The system has a mix of new members and old members which do not > support Lucene reindex. > Action: The Apache Geode developer creates the region on the new member, and > then creates the Lucene index. > The old members are now rolled to the new version which supports Lucene Index. > Create lucene index first on the freshly rolled members and then create > region. > Result: This operation must be successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451370#comment-16451370
]
ASF subversion and git services commented on GEODE-925:
---
Commit e80d3f4038485b7d71265690376b8c480bd8a515 in geode's branch
refs/heads/develop from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e80d3f4 ]
Revert "Revert "GEODE-925: Replaced all Wait.pause with Awaitility. Replaced
all ThreadUtils.join with an Awaitility. General code and lambda clean up""
This reverts commit 7c4c4e57cefcf49e2ea2a69250176c63ffcffc44.
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-3451) Data inconsistency detected in distributed ack test on empty region
[
https://issues.apache.org/jira/browse/GEODE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451352#comment-16451352
]
ASF subversion and git services commented on GEODE-3451:
Commit 8020f37073ea08b6948d27a4d9220a1491532605 in geode's branch
refs/heads/develop from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8020f37 ]
GEODE-3451: add a flaky lable.
> Data inconsistency detected in distributed ack test on empty region
> ---
>
> Key: GEODE-3451
> URL: https://issues.apache.org/jira/browse/GEODE-3451
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Nick Reich
>Priority: Major
> Labels: ci, flaky
>
> {noformat}
> org.apache.geode.cache30.DistributedAckRegionCCEOffHeapDUnitTest >
> testConcurrentEventsOnEmptyRegion FAILED
> org.junit.ComparisonFailure: region contents are not consistent for
> cckey8 expected: but was:
> {noformat}
> Note: test failure was not readily reproduced
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451345#comment-16451345
]
ASF subversion and git services commented on GEODE-925:
---
Commit 7c4c4e57cefcf49e2ea2a69250176c63ffcffc44 in geode's branch
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7c4c4e5 ]
Revert "GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up"
This reverts commit 9145fa352e84724dd21d598a855210c71340acfd.
Reverting due to spotless issue
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Resolved] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Kohlmeyer resolved GEODE-925.
-
Resolution: Fixed
Fix Version/s: 1.7.0
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
[jira] [Updated] (GEODE-5138) rename a stats for gateway sender with meaningful name
[ https://issues.apache.org/jira/browse/GEODE-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5138: -- Labels: pull-request-available (was: ) > rename a stats for gateway sender with meaningful name > -- > > Key: GEODE-5138 > URL: https://issues.apache.org/jira/browse/GEODE-5138 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > > Document team reviewed and suggest to use > EVENTS_DROPPED_DUE_TO_PRIMARY_SENDER_NOT_RUNNING: "Number of events dropped > because the primary gateway sender is not running." > instead of: > NOT_QUEUED_EVENTS_AT_YET_RUNNING_PRIMARY_SENDER: "Number of events not added > to primary queue due to sender yet running." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451310#comment-16451310 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-5138 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5138) rename a stats for gateway sender with meaningful name
[ https://issues.apache.org/jira/browse/GEODE-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451315#comment-16451315 ] ASF subversion and git services commented on GEODE-5138: Commit 20f8745e47bb3520150153087be01b9f5a654a3b in geode's branch refs/heads/feature/GEODE-5138 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=20f8745 ] GEODE-5138: rename the gateway sender stats to a better name > rename a stats for gateway sender with meaningful name > -- > > Key: GEODE-5138 > URL: https://issues.apache.org/jira/browse/GEODE-5138 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > > Document team reviewed and suggest to use > EVENTS_DROPPED_DUE_TO_PRIMARY_SENDER_NOT_RUNNING: "Number of events dropped > because the primary gateway sender is not running." > instead of: > NOT_QUEUED_EVENTS_AT_YET_RUNNING_PRIMARY_SENDER: "Number of events not added > to primary queue due to sender yet running." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451312#comment-16451312 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-5138 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451314#comment-16451314
]
ASF subversion and git services commented on GEODE-925:
---
Commit 9145fa352e84724dd21d598a855210c71340acfd in geode's branch
refs/heads/feature/GEODE-5138 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9145fa3 ]
GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up
Modify test to use test rules
remove TODO from test
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451313#comment-16451313 ] ASF subversion and git services commented on GEODE-5129: Commit d4b02cb93e67121fd2f96cfc90a1c1bc2ebbccec in geode's branch refs/heads/feature/GEODE-5138 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d4b02cb ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451311#comment-16451311 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-5138 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451309#comment-16451309 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-5138 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5138) rename a stats for gateway sender with meaningful name
[ https://issues.apache.org/jira/browse/GEODE-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451307#comment-16451307 ] ASF subversion and git services commented on GEODE-5138: Commit abdfcf97dff4cf4178e0aeb9a578810cd80e2031 in geode's branch refs/heads/feature/GEODE-5138 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=abdfcf9 ] GEODE-5138: rename the gateway sender stats to a better name > rename a stats for gateway sender with meaningful name > -- > > Key: GEODE-5138 > URL: https://issues.apache.org/jira/browse/GEODE-5138 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Fix For: 1.7.0 > > > Document team reviewed and suggest to use > EVENTS_DROPPED_DUE_TO_PRIMARY_SENDER_NOT_RUNNING: "Number of events dropped > because the primary gateway sender is not running." > instead of: > NOT_QUEUED_EVENTS_AT_YET_RUNNING_PRIMARY_SENDER: "Number of events not added > to primary queue due to sender yet running." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451296#comment-16451296 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-925 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451295#comment-16451295 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-925 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451301#comment-16451301
]
ASF subversion and git services commented on GEODE-925:
---
Commit 9145fa352e84724dd21d598a855210c71340acfd in geode's branch
refs/heads/develop from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9145fa3 ]
GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up
Modify test to use test rules
remove TODO from test
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451298#comment-16451298 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-925 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451299#comment-16451299 ] ASF subversion and git services commented on GEODE-5129: Commit d4b02cb93e67121fd2f96cfc90a1c1bc2ebbccec in geode's branch refs/heads/feature/GEODE-925 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d4b02cb ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry
[
https://issues.apache.org/jira/browse/GEODE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451291#comment-16451291
]
ASF subversion and git services commented on GEODE-4957:
Commit c020dc9aeaf68f91d9da1182cec78930550b5d6b in geode's branch
refs/heads/feature/GEODE-925 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c020dc9 ]
GEODE-4957: fix race in concurrent create on region (#1836)
Reverted the revert of GEODE-4957.
Only cleanup if basicPut created a new region entry and its value at the end is
still REMOVED_PHASE1
> The key used in a putIfAbsent call that returns null may not be the one in
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9
> creates the RegionEntry. You can see that because not only is oldRe=null for
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null);
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=1682369152; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=342592289; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry
[
https://issues.apache.org/jira/browse/GEODE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451293#comment-16451293
]
ASF subversion and git services commented on GEODE-4957:
Commit c020dc9aeaf68f91d9da1182cec78930550b5d6b in geode's branch
refs/heads/feature/GEODE-925 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c020dc9 ]
GEODE-4957: fix race in concurrent create on region (#1836)
Reverted the revert of GEODE-4957.
Only cleanup if basicPut created a new region entry and its value at the end is
still REMOVED_PHASE1
> The key used in a putIfAbsent call that returns null may not be the one in
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9
> creates the RegionEntry. You can see that because not only is oldRe=null for
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null);
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=1682369152; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=342592289; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451297#comment-16451297 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/feature/GEODE-925 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451300#comment-16451300
]
ASF subversion and git services commented on GEODE-925:
---
Commit 9145fa352e84724dd21d598a855210c71340acfd in geode's branch
refs/heads/feature/GEODE-925 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9145fa3 ]
GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up
Modify test to use test rules
remove TODO from test
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-5113) Update docs for EvictionAttributes.getMaximum() no longer throwing UnsupportedOperationException for LRU Heap
[ https://issues.apache.org/jira/browse/GEODE-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451294#comment-16451294 ] ASF subversion and git services commented on GEODE-5113: Commit 1d474c0457586c1b7b271f3c19cdc9d4218474b8 in geode's branch refs/heads/feature/GEODE-925 from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1d474c0 ] GEODE-5113: fix javadocs on getMaximum (#1843) > Update docs for EvictionAttributes.getMaximum() no longer throwing > UnsupportedOperationException for LRU Heap > - > > Key: GEODE-5113 > URL: https://issues.apache.org/jira/browse/GEODE-5113 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Fred Krone >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > TLDR: I think we can just document this updated change. I didn't have much > time to think about it earlier today but thinking about it now I can see why > we changed this. > Previously, the EvictionAttributes.getMaximum() used to throw an > UnsupportedOperationException if the user tried to configure a Maximum on an > LRU Heap Eviction Policy (Apache Geode 1.4). Now Geode (and by extension, > GemFire) will just silently return 0. > IF this change is intentional the docs should be updated accordingly. > [http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/EvictionAttributes.html#getMaximum--] > > in 1.4 > [https://github.com/apache/geode/blob/rel/v1.4.0/geode-core/src/main/java/org/apache/geode/internal/cache/EvictionAttributesImpl.java#L138-L144] > > in 1.5 > [https://github.com/apache/geode/blob/rel/v1.5.0/geode-core/src/main/java/org/apache/geode/internal/cache/EvictionAttributesImpl.java#L95-L101] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451286#comment-16451286 ] ASF subversion and git services commented on GEODE-5129: Commit d4b02cb93e67121fd2f96cfc90a1c1bc2ebbccec in geode's branch refs/heads/develop from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d4b02cb ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-4647. Resolution: Fixed > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451274#comment-16451274 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451275#comment-16451275 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451273#comment-16451273 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451276#comment-16451276 ] ASF subversion and git services commented on GEODE-4647: Commit e26889d4a3516542bc720156186513295fca8903 in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e26889d ] GEODE-4647 Document eventSecondaryQueueSize statistic (#1831) * GEODE-4647 Document eventSecondaryQueueSize statistic * GEODE-4647 New statistic is now named secondaryEventQueueSize * GEODE-4647 revise secondaryEventQueueSize defn wording, per review > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5137) clean up oql.g build warnings
[ https://issues.apache.org/jira/browse/GEODE-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5137: -- Labels: pull-request-available (was: ) > clean up oql.g build warnings > - > > Key: GEODE-5137 > URL: https://issues.apache.org/jira/browse/GEODE-5137 > Project: Geode > Issue Type: Task > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > > when building Geode, we see oql.g warning about nondeterminism in our > grammar. This is a ticket to address those issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5138) rename a stats for gateway sender with meaningful name
[ https://issues.apache.org/jira/browse/GEODE-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-5138: Assignee: xiaojian zhou > rename a stats for gateway sender with meaningful name > -- > > Key: GEODE-5138 > URL: https://issues.apache.org/jira/browse/GEODE-5138 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Fix For: 1.7.0 > > > Document team reviewed and suggest to use > EVENTS_DROPPED_DUE_TO_PRIMARY_SENDER_NOT_RUNNING: "Number of events dropped > because the primary gateway sender is not running." > instead of: > NOT_QUEUED_EVENTS_AT_YET_RUNNING_PRIMARY_SENDER: "Number of events not added > to primary queue due to sender yet running." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5138) rename a stats for gateway sender with meaningful name
xiaojian zhou created GEODE-5138: Summary: rename a stats for gateway sender with meaningful name Key: GEODE-5138 URL: https://issues.apache.org/jira/browse/GEODE-5138 Project: Geode Issue Type: Bug Components: wan Reporter: xiaojian zhou Fix For: 1.7.0 Document team reviewed and suggest to use EVENTS_DROPPED_DUE_TO_PRIMARY_SENDER_NOT_RUNNING: "Number of events dropped because the primary gateway sender is not running." instead of: NOT_QUEUED_EVENTS_AT_YET_RUNNING_PRIMARY_SENDER: "Number of events not added to primary queue due to sender yet running." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5137) clean up oql.g build warnings
[ https://issues.apache.org/jira/browse/GEODE-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh reassigned GEODE-5137: -- Assignee: Jason Huynh > clean up oql.g build warnings > - > > Key: GEODE-5137 > URL: https://issues.apache.org/jira/browse/GEODE-5137 > Project: Geode > Issue Type: Task > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > > when building Geode, we see oql.g warning about nondeterminism in our > grammar. This is a ticket to address those issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5137) clean up oql.g build warnings
Jason Huynh created GEODE-5137: -- Summary: clean up oql.g build warnings Key: GEODE-5137 URL: https://issues.apache.org/jira/browse/GEODE-5137 Project: Geode Issue Type: Task Components: querying Reporter: Jason Huynh when building Geode, we see oql.g warning about nondeterminism in our grammar. This is a ticket to address those issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-5070: -- Fix Version/s: 1.7.0 > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: docs, gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals
[ https://issues.apache.org/jira/browse/GEODE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reopened GEODE-4624: Assignee: Karen Smoler Miller (was: xiaojian zhou) Reopening ticket to complete documentation of new statistics. > Add a new stat for AyncEventQueue/GatewaySender to track the processing of > queueRemovals > > > Key: GEODE-4624 > URL: https://issues.apache.org/jira/browse/GEODE-4624 > Project: Geode > Issue Type: Bug > Components: docs, wan >Affects Versions: 1.5.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We currently track the number of events queues, queue size and > eventsDistributed ... but we don't track the number of events removed via > queue removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5136) [info 2018/04/24 16:41:06.599 EDT locator1 tid=0x1] Starting server location for Distribution Locator on
Joe created GEODE-5136: -- Summary: [info 2018/04/24 16:41:06.599 EDT locator1 tid=0x1] Starting server location for Distribution Locator on Key: GEODE-5136 URL: https://issues.apache.org/jira/browse/GEODE-5136 Project: Geode Issue Type: Bug Components: configuration Reporter: Joe the server just hangs with this error [info 2018/04/24 16:41:03.491 EDT locator1 tid=0x1] Starting peer location for Distribution Locator on R90N15R7.ptl.ad.penske.com[10334] [info 2018/04/24 16:41:03.511 EDT locator1 tid=0x1] Starting Distribution Locator on R90N15R7.ptl.ad.penske.com[10334] [info 2018/04/24 16:41:03.513 EDT locator1 tid=0x1] Locator was created at Tue Apr 24 16:41:03 EDT 2018 [info 2018/04/24 16:41:03.513 EDT locator1 tid=0x1] Listening on port 10334 bound on address 0.0.0.0/0.0.0.0 [info 2018/04/24 16:41:03.514 EDT locator1 tid=0x1] GemFire peer location service starting. Other locators: Locators preferred as coordinators: true Network partition detection enabled: true View persistence file: C:\gemfire\locator1\locator10334view.dat [info 2018/04/24 16:41:03.515 EDT locator1 tid=0x1] recovery file not found: C:\gemfire\locator1\locator10334view.dat [info 2018/04/24 16:41:03.518 EDT locator1 tid=0x1] Starting distributed system [info 2018/04/24 16:41:03.574 EDT locator1 tid=0x1] --- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --- Build-Date: 2018-03-19 16:50:34 + Build-Id: root 13 Build-Java-Version: 1.8.0_161 Build-Platform: Linux 4.4.0-89-generic amd64 GemFire-Source-Date: 2018-03-19 16:06:42 + GemFire-Source-Repository: support/9.4 GemFire-Source-Revision: a79a89636981719f3153c9a38db87aa49a7f2026 Product-Name: Pivotal GemFire Product-Version: 9.4.0 Source-Date: 2018-03-16 20:43:10 + Source-Repository: support/9.4 Source-Revision: f122abcb40ac9050680ed28b1e66ad73a60cba46 Native version: native code unavailable Running on: R90N15R7.ptl.ad.penske.com/3.144.68.80, 4 cpu(s), amd64 Windows 10 10.0 Communications version: 80 Process ID: 13744 User: 600165102 Current dir: C:\gemfire\locator1 Home dir: C:\Users\600165102 Command Line Parameters: -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=9223372036854775806 Class Path: C:\Users\600165102\Documents\bigdata\pivotal-gemfire-9.4.0\lib\geode-core-9.4.0.jar C:\Users\600165102\Documents\bigdata\pivotal-gemfire-9.4.0\lib\geode-dependencies.jar Library Path: C:\Program Files\Java\jdk-10\bin C:\Windows\Sun\Java\bin C:\Windows\system32 C:\Windows C:\ProgramData\Oracle\Java\javapath C:\Program Files\Java\jdk1.8.0_162 C:\Oracle11g\product\11.2.0\client_1\bin C:\Program Files (x86)\CA\SC\CAWIN\ C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Program Files\PKWARE\pkzipc C:\Program Files (x86)\IBM\Client Access\Shared C:\Program Files (x86)\IBM\Client Access\ C:\Program Files (x86)\Sennheiser\SoftphoneSDK\ C:\Program Files (x86)\CA\SC\Csam\SockAdapter\bin C:\Program Files (x86)\CA\SC\Csam\SockAdapter\bin64 C:\Program Files (x86)\CA\SC\CBB\ C:\Program Files (x86)\CA\DSM\bin C:\PROGRA~2\CA\SC\CAM\bin C:\Program Files\TortoiseGit\bin C:\Program Files\TortoiseSVN\bin C:\Program Files\Amazon\AWSCLI\ C:\Program Files (x86)\Greenplum\greenplum-clients-5.1.0\bin C:\Program Files (x86)\Greenplum\greenplum-clients-5.1.0\lib C:\Program Files\Progress\DataDirect\Connect64_for_ODBC_71\drivers C:\Users\600165102\Documents\bigdata\maven\apache-maven-3.5.2\bin C:\Program Files\Git\cmd C:\Program Files\Cloud Foundry C:\Program Files (x86)\scala\bin C:\PROGRA~2\Groovy\GROOVY~1.0\bin C:\Program Files\Java\jdk-10 C:\Program Files\Java\jdk-10\bin C:\Users\600165102\AppData\Local\Programs\Python\Python36-32\Scripts\ C:\Users\600165102\AppData\Local\Programs\Python\Python36-32\
[jira] [Updated] (GEODE-5136) [info 2018/04/24 16:41:06.599 EDT locator1 tid=0x1] Starting server location for Distribution Locator on
[ https://issues.apache.org/jira/browse/GEODE-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe updated GEODE-5136: --- Priority: Minor (was: Major) > [info 2018/04/24 16:41:06.599 EDT locator1 tid=0x1] Starting server > location for Distribution Locator on > > > Key: GEODE-5136 > URL: https://issues.apache.org/jira/browse/GEODE-5136 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Joe >Priority: Minor > > the server just hangs with this error > > [info 2018/04/24 16:41:03.491 EDT locator1 tid=0x1] Starting peer > location for Distribution Locator on R90N15R7.ptl.ad.penske.com[10334] > [info 2018/04/24 16:41:03.511 EDT locator1 tid=0x1] Starting > Distribution Locator on R90N15R7.ptl.ad.penske.com[10334] > [info 2018/04/24 16:41:03.513 EDT locator1 tid=0x1] Locator was > created at Tue Apr 24 16:41:03 EDT 2018 > [info 2018/04/24 16:41:03.513 EDT locator1 tid=0x1] Listening on port > 10334 bound on address 0.0.0.0/0.0.0.0 > [info 2018/04/24 16:41:03.514 EDT locator1 tid=0x1] GemFire peer > location service starting. Other locators: Locators preferred as > coordinators: true Network partition detection enabled: true View persistence > file: C:\gemfire\locator1\locator10334view.dat > [info 2018/04/24 16:41:03.515 EDT locator1 tid=0x1] recovery file not > found: C:\gemfire\locator1\locator10334view.dat > [info 2018/04/24 16:41:03.518 EDT locator1 tid=0x1] Starting > distributed system > [info 2018/04/24 16:41:03.574 EDT locator1 tid=0x1] > --- > > Licensed to the Apache Software Foundation (ASF) under one or more > contributor license agreements. See the NOTICE file distributed with this > work for additional information regarding copyright ownership. > > The ASF licenses this file to You under the Apache License, Version 2.0 > (the "License"); you may not use this file except in compliance with the > License. You may obtain a copy of the License at > > http://www.apache.org/licenses/LICENSE-2.0 > > Unless required by applicable law or agreed to in writing, software > distributed under the License is distributed on an "AS IS" BASIS, WITHOUT > WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the > License for the specific language governing permissions and limitations > under the License. > > --- > Build-Date: 2018-03-19 16:50:34 + > Build-Id: root 13 > Build-Java-Version: 1.8.0_161 > Build-Platform: Linux 4.4.0-89-generic amd64 > GemFire-Source-Date: 2018-03-19 16:06:42 + > GemFire-Source-Repository: support/9.4 > GemFire-Source-Revision: a79a89636981719f3153c9a38db87aa49a7f2026 > Product-Name: Pivotal GemFire > Product-Version: 9.4.0 > Source-Date: 2018-03-16 20:43:10 + > Source-Repository: support/9.4 > Source-Revision: f122abcb40ac9050680ed28b1e66ad73a60cba46 > Native version: native code unavailable > Running on: R90N15R7.ptl.ad.penske.com/3.144.68.80, 4 cpu(s), amd64 Windows > 10 10.0 > Communications version: 80 > Process ID: 13744 > User: 600165102 > Current dir: C:\gemfire\locator1 > Home dir: C:\Users\600165102 > Command Line Parameters: > -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=9223372036854775806 > Class Path: > > C:\Users\600165102\Documents\bigdata\pivotal-gemfire-9.4.0\lib\geode-core-9.4.0.jar > > C:\Users\600165102\Documents\bigdata\pivotal-gemfire-9.4.0\lib\geode-dependencies.jar > Library Path: > C:\Program Files\Java\jdk-10\bin > C:\Windows\Sun\Java\bin > C:\Windows\system32 > C:\Windows > C:\ProgramData\Oracle\Java\javapath > C:\Program Files\Java\jdk1.8.0_162 > C:\Oracle11g\product\11.2.0\client_1\bin > C:\Program Files (x86)\CA\SC\CAWIN\ > C:\Windows\system32 > C:\Windows > C:\Windows\System32\Wbem > C:\Windows\System32\WindowsPowerShell\v1.0\ > C:\Program Files\PKWARE\pkzipc > C:\Program Files (x86)\IBM\Client Access\Shared > C:\Program Files (x86)\IBM\Client Access\ > C:\Program Files (x86)\Sennheiser\SoftphoneSDK\ > C:\Program Files (x86)\CA\SC\Csam\SockAdapter\bin > C:\Program Files (x86)\CA\SC\Csam\SockAdapter\bin64 > C:\Program Files (x86)\CA\SC\CBB\ > C:\Program Files (x86)\CA\DSM\bin > C:\PROGRA~2\CA\SC\CAM\bin > C:\Program Files\TortoiseGit\bin > C:\Program Files\TortoiseSVN\bin > C:\Program Files\Amazon\AWSCLI\ > C:\Program Files (x86)\Greenplum\greenplum-clients-5.1.0\bin > C:\Program Files (x86)\Greenplum\greenplum-clients-5.1.0\lib > C:\Program
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450664#comment-16450664
]
ASF subversion and git services commented on GEODE-925:
---
Commit 53327dcbf5cb61f29ff044e7d8c8219a86f5c0ac in geode's branch
refs/heads/feature/GEODE-925 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=53327dc ]
GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up
Modify test to use test rules
remove TODO from test
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450660#comment-16450660 ] ASF subversion and git services commented on GEODE-5129: Commit a7b973694b6d2158f0875d7ea2b458768ec039de in geode's branch refs/heads/feature/GEODE-925 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a7b9736 ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry
[
https://issues.apache.org/jira/browse/GEODE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider resolved GEODE-4957.
-
Resolution: Fixed
Fix Version/s: 1.7.0
> The key used in a putIfAbsent call that returns null may not be the one in
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9
> creates the RegionEntry. You can see that because not only is oldRe=null for
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null);
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=1682369152; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=342592289; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5113) Update docs for EvictionAttributes.getMaximum() no longer throwing UnsupportedOperationException for LRU Heap
[ https://issues.apache.org/jira/browse/GEODE-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-5113. - Resolution: Fixed Fix Version/s: 1.7.0 > Update docs for EvictionAttributes.getMaximum() no longer throwing > UnsupportedOperationException for LRU Heap > - > > Key: GEODE-5113 > URL: https://issues.apache.org/jira/browse/GEODE-5113 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Fred Krone >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > TLDR: I think we can just document this updated change. I didn't have much > time to think about it earlier today but thinking about it now I can see why > we changed this. > Previously, the EvictionAttributes.getMaximum() used to throw an > UnsupportedOperationException if the user tried to configure a Maximum on an > LRU Heap Eviction Policy (Apache Geode 1.4). Now Geode (and by extension, > GemFire) will just silently return 0. > IF this change is intentional the docs should be updated accordingly. > [http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/EvictionAttributes.html#getMaximum--] > > in 1.4 > [https://github.com/apache/geode/blob/rel/v1.4.0/geode-core/src/main/java/org/apache/geode/internal/cache/EvictionAttributesImpl.java#L138-L144] > > in 1.5 > [https://github.com/apache/geode/blob/rel/v1.5.0/geode-core/src/main/java/org/apache/geode/internal/cache/EvictionAttributesImpl.java#L95-L101] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry
[
https://issues.apache.org/jira/browse/GEODE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450399#comment-16450399
]
ASF subversion and git services commented on GEODE-4957:
Commit c020dc9aeaf68f91d9da1182cec78930550b5d6b in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c020dc9 ]
GEODE-4957: fix race in concurrent create on region (#1836)
Reverted the revert of GEODE-4957.
Only cleanup if basicPut created a new region entry and its value at the end is
still REMOVED_PHASE1
> The key used in a putIfAbsent call that returns null may not be the one in
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9
> creates the RegionEntry. You can see that because not only is oldRe=null for
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null);
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=1682369152; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=342592289; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry
[
https://issues.apache.org/jira/browse/GEODE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450398#comment-16450398
]
ASF subversion and git services commented on GEODE-4957:
Commit c020dc9aeaf68f91d9da1182cec78930550b5d6b in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c020dc9 ]
GEODE-4957: fix race in concurrent create on region (#1836)
Reverted the revert of GEODE-4957.
Only cleanup if basicPut created a new region entry and its value at the end is
still REMOVED_PHASE1
> The key used in a putIfAbsent call that returns null may not be the one in
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9
> creates the RegionEntry. You can see that because not only is oldRe=null for
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null);
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=1682369152; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1;
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut
> eventKey=ComplexKey[identity=342592289; key=key];
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5059) AbstractRegionMap.basicPut should be refactored
[ https://issues.apache.org/jira/browse/GEODE-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-5059: --- Assignee: Darrel Schneider > AbstractRegionMap.basicPut should be refactored > --- > > Key: GEODE-5059 > URL: https://issues.apache.org/jira/browse/GEODE-5059 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: AbstractRegionMap > > Recently the AbstractRegionMap.basicPut method was refactored into many > smaller methods that all take an instance of RegionMapPutContext. > These methods should be moved to another class (it could be named > RegionMapPut) and the RegionMapPutContext could go away since the > RegionMapPut instance could keep all the state of the put operation. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5010) Introduce *ResultModel objects to replace *ResultData
[ https://issues.apache.org/jira/browse/GEODE-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-5010: --- Component/s: docs > Introduce *ResultModel objects to replace *ResultData > - > > Key: GEODE-5010 > URL: https://issues.apache.org/jira/browse/GEODE-5010 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > Introduce POJOs to be used as replacements for CompositeResultData, > TabularResultData, InfoResultData and ErrorResultData. > These POJOs will be json serializable using Jackson > Provide ability to use both legacy and these new POJOs until all commands > have been migrated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-5070: --- Component/s: docs > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: docs, gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450370#comment-16450370 ] ASF subversion and git services commented on GEODE-5129: Commit a7b973694b6d2158f0875d7ea2b458768ec039de in geode's branch refs/heads/feature/GEODE-5129 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a7b9736 ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450369#comment-16450369 ] ASF subversion and git services commented on GEODE-5129: Commit 6c066e6973576d80293723fabd9ddeb4d0c36988 in geode's branch refs/heads/feature/GEODE-5129 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6c066e6 ] GEODE-5129 Added vmCount to AbstractDistributedTestRule > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5120) Remove DistributedSystem from Public API
[ https://issues.apache.org/jira/browse/GEODE-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450359#comment-16450359 ] ASF subversion and git services commented on GEODE-5120: Commit 5ece73f40dc2f71c27d0ba13e415786fc0e2bc1f in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5ece73f ] GEODE-5120: Move DistributedSystem.hpp internal. > Remove DistributedSystem from Public API > > > Key: GEODE-5120 > URL: https://issues.apache.org/jira/browse/GEODE-5120 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > DistributedSystem not need to be exposed publicly anymore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5135) Refactor the static method AbstractRegionMap.createCBEvent
Darrel Schneider created GEODE-5135: --- Summary: Refactor the static method AbstractRegionMap.createCBEvent Key: GEODE-5135 URL: https://issues.apache.org/jira/browse/GEODE-5135 Project: Geode Issue Type: Improvement Components: transactions Reporter: Darrel Schneider AbstractRegionMap.createCBEvent would make more sense as a factory method on EntryEventImpl. Note that ProxyRegionMap currently calls static methods on AbstractRegionMap. Since ProxyRegionMap and AbstractRegionMap both implement the RegionMap interface it would be better to either have a common ancestor class for both these classes that contains this common code they share or move this code to methods on the RegionMap interface. It would be nice if ProxyRegionMap did not depend on anything in AbstractRegionMap. One idea would be to rename AbstractRegionMap to StorageRegionMap and then have the common ancestor class that both ProxyRegionMap and StorageRegionMap extend by named AbstractRegionMap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5134) RegionMap tx methods should expect the pendingCallbacks parameter to never be null
Darrel Schneider created GEODE-5134: --- Summary: RegionMap tx methods should expect the pendingCallbacks parameter to never be null Key: GEODE-5134 URL: https://issues.apache.org/jira/browse/GEODE-5134 Project: Geode Issue Type: Improvement Components: transactions Reporter: Darrel Schneider All the tx* methods on RegionMap (txApplyPut, txApplyInvalidate, txApplyDestroy) have a pendingCallbacks parameter. All the implementations of these methods have special code that handles pendingCallbacks being null. But the callers have been changed to never pass a null pendingCallbacks. Changing these methods to only handle a non-null pendingCallbacks will make these methods easier to understand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5103: Affects Version/s: 1.6.0 1.1.0 1.2.0 1.3.0 1.4.0 1.5.0 > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5103. - Resolution: Fixed Fix Version/s: 1.7.0 > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5040) CI Failure: RegionExpirationDistributedTest.regionExpiresAfterTtl
[
https://issues.apache.org/jira/browse/GEODE-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450319#comment-16450319
]
ASF subversion and git services commented on GEODE-5040:
Commit 65a2c0dc1c2a8ed16cb549578015341b19442f0f in geode's branch
refs/heads/feature/GEODE-925 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=65a2c0d ]
GEODE-5040: Fix intermittent RegionExpirationDistributedTest failure
Use Awaitility and avoid invoking assertThat(Map) for Region (which
is a Map).
> CI Failure: RegionExpirationDistributedTest.regionExpiresAfterTtl
> -
>
> Key: GEODE-5040
> URL: https://issues.apache.org/jira/browse/GEODE-5040
> Project: Geode
> Issue Type: Bug
> Components: expiration, tests
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.cache.RegionExpirationDistributedTest >
> regionExpiresAfterTtl(DESTROY) FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.RegionExpirationDistributedTest$$Lambda$63/1961035464.run
> in VM 1 running on Host 6bb748d43f1f with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.cache.RegionExpirationDistributedTest.regionExpiresAfterTtl(RegionExpirationDistributedTest.java:127)
> Caused by:
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/RegionExpirationDistributedTest_regionExpiresAfterTtl';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
> at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8834)
> at java.util.TreeMap.putAll(TreeMap.java:313)
> at java.util.TreeMap.(TreeMap.java:185)
> at
> org.assertj.core.presentation.StandardRepresentation.toSortedMapIfPossible(StandardRepresentation.java:304)
> at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:284)
> at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:167)
> at
> org.assertj.core.error.ShouldBeEqual.actualAndExpectedHaveSameStringRepresentation(ShouldBeEqual.java:131)
> at
> org.assertj.core.error.ShouldBeEqual.newAssertionError(ShouldBeEqual.java:109)
> at org.assertj.core.internal.Failures.failure(Failures.java:96)
> at org.assertj.core.internal.Objects.assertNull(Objects.java:360)
> at
> org.assertj.core.api.AbstractAssert.isNull(AbstractAssert.java:274)
> at
> org.apache.geode.cache.RegionExpirationDistributedTest$Verification.assertRegionStateInRemoteMember(RegionExpirationDistributedTest.java:184)
> at
> org.apache.geode.cache.RegionExpirationDistributedTest.lambda$regionExpiresAfterTtl$7f930bcf$3(RegionExpirationDistributedTest.java:128)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450330#comment-16450330
]
ASF subversion and git services commented on GEODE-925:
---
Commit 59a0d45779db01975f47ec9c2d5a07ef6f93b18e in geode's branch
refs/heads/feature/GEODE-925 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=59a0d45 ]
GEODE-925: Replaced all Wait.pause with Awaitility. Replaced all
ThreadUtils.join with an Awaitility. General code and lambda clean up
Modify test to use test rules
remove TODO from test
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Commented] (GEODE-5122) type arguments given on a raw type error
[
https://issues.apache.org/jira/browse/GEODE-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450328#comment-16450328
]
ASF subversion and git services commented on GEODE-5122:
Commit af3e575a120ba01b1db5c9a82e23ea6e95a5c5a0 in geode's branch
refs/heads/feature/GEODE-925 from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=af3e575 ]
GEODE-5122: Removed the type argument (#1840)
* Removed the type argument from the raw type.
* This was coming up as an error in IDE.
> type arguments given on a raw type error
> -
>
> Key: GEODE-5122
> URL: https://issues.apache.org/jira/browse/GEODE-5122
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In LuceneQueryFunctionJUnitTest we were seeing the following errors in the
> IDE
> {noformat}
> type arguments given on a raw type error
> {noformat}
> This was because we were assigning type arguments to the raw type Result
> Sender.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450323#comment-16450323 ] ASF subversion and git services commented on GEODE-5103: Commit 4a385b8ac4d7c1f6db6fc12c35e80871c7a1edbe in geode's branch refs/heads/feature/GEODE-925 from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a385b8 ] GEODE-5103: When applying transactional update on a replicate, callba… (#1825) * GEODE-5103: When applying transactional update on a replicate, callbacks should be always generated. Currently callbacks is not generated if a region entry is null possibly caused by rebalance etc. We still want the node to generate callbacks for its clients. > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3438) Collection added to itself
[
https://issues.apache.org/jira/browse/GEODE-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450325#comment-16450325
]
ASF subversion and git services commented on GEODE-3438:
Commit 147c9d54dcc2d03704e6cb4ddfc2fa36fa70278f in geode's branch
refs/heads/feature/GEODE-925 from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=147c9d5 ]
GEODE-3438: Removed unused constructor and method (#1832)
> Collection added to itself
> --
>
> Key: GEODE-3438
> URL: https://issues.apache.org/jira/browse/GEODE-3438
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: JC
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Hi
> In a recent github mirror, I've found suspicious code.
> Branch: master
> Path:
> geode-core/src/main/java/org/apache/geode/management/internal/cli/domain/DurableCqNamesResult.java
> {code:java}
> ...
> 27 private List cqNames = new ArrayList();
> ...
> 33 public DurableCqNamesResult(final String memberNameOrId, List
> cqNames) {
> 34 super(memberNameOrId);
> 35 cqNames.addAll(cqNames);
> 36 }
> {code}
> In Line 35, should `cqNames.addAll' be `this.cqNames.addAll'? This might not
> be an issue, but I wanted to report just in case.
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5020) Move HARegionQueue system properties to SystemPropertyHelper
[ https://issues.apache.org/jira/browse/GEODE-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450321#comment-16450321 ] ASF subversion and git services commented on GEODE-5020: Commit eb0bb8968c50a4580e920e214c8c96b92c9b6171 in geode's branch refs/heads/feature/GEODE-925 from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=eb0bb89 ] GEODE-5020: calculateThreadIdExpiryTime during ThreadIdentifierCustomExpiry ctor > Move HARegionQueue system properties to SystemPropertyHelper > > > Key: GEODE-5020 > URL: https://issues.apache.org/jira/browse/GEODE-5020 > Project: Geode > Issue Type: Improvement > Components: client queues >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The two system properties are "MessageTimeToLive" and "threadIdExpiryTime." > HARegionQueue should use SystemPropertyHelper to get the optional values for > these properties so that geode. or gemfire. may be used as the prefix. > (I ran into this while cleaning up tests for GEODE-1279) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450329#comment-16450329 ] ASF subversion and git services commented on GEODE-5129: Commit d5045a9623406a45b06662025be3c6b26c7a0914 in geode's branch refs/heads/feature/GEODE-925 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d5045a9 ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450327#comment-16450327 ] ASF subversion and git services commented on GEODE-5129: Commit 2fa94a0063d4f94881de939deb1c5ca689dc6e4c in geode's branch refs/heads/feature/GEODE-925 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2fa94a0 ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450322#comment-16450322 ] ASF subversion and git services commented on GEODE-5070: Commit 2dcc0820e823bf06e2b412c059e9d2d7d11cc4ca in geode's branch refs/heads/feature/GEODE-925 from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2dcc082 ] GEODE-5070: Use a random member for describe & list jdbc connector commands (#1849) Retrieves connections & mappings from CC(if running) or from a random member(if CC not running) > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450324#comment-16450324 ] ASF subversion and git services commented on GEODE-5103: Commit 4a385b8ac4d7c1f6db6fc12c35e80871c7a1edbe in geode's branch refs/heads/feature/GEODE-925 from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a385b8 ] GEODE-5103: When applying transactional update on a replicate, callba… (#1825) * GEODE-5103: When applying transactional update on a replicate, callbacks should be always generated. Currently callbacks is not generated if a region entry is null possibly caused by rebalance etc. We still want the node to generate callbacks for its clients. > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4996) NullPointerException during HAEventWrapper serialization
[
https://issues.apache.org/jira/browse/GEODE-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450326#comment-16450326
]
ASF subversion and git services commented on GEODE-4996:
Commit f6dd58f83528b32bb0fb1a44da9bb47ea29f5df3 in geode's branch
refs/heads/feature/GEODE-925 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f6dd58f ]
GEODE-4996: Addressed NPE by always using the region entry key
> NullPointerException during HAEventWrapper serialization
>
>
> Key: GEODE-4996
> URL: https://issues.apache.org/jira/browse/GEODE-4996
> Project: Geode
> Issue Type: Improvement
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> HAEventWrapper toData can throw NPE during HARegion GII.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.tier.sockets.HAEventWrapper.toData(HAEventWrapper.java:287)
> at
> org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2425)
> at
> org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1533)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2193)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2936)
> at org.apache.geode.internal.util.BlobHelper.serializeTo(BlobHelper.java:66)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.fillInValue(AbstractRegionEntry.java:411)
> at
> org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.chunkEntries(InitialImageOperation.java:1982)
> at
> org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.process(InitialImageOperation.java:1750)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1118)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:830)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450304#comment-16450304 ] ASF subversion and git services commented on GEODE-5129: Commit d5045a9623406a45b06662025be3c6b26c7a0914 in geode's branch refs/heads/develop from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d5045a9 ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5133) EvictionAttributes.getMaximum should return meaningful value for HEAP_LRU
Darrel Schneider created GEODE-5133: --- Summary: EvictionAttributes.getMaximum should return meaningful value for HEAP_LRU Key: GEODE-5133 URL: https://issues.apache.org/jira/browse/GEODE-5133 Project: Geode Issue Type: Improvement Components: eviction Reporter: Darrel Schneider Currently EvictionAttributes.getMaximum always returns zero for a HEAP_LRU. It would be better if it returned the percentage from the ResourceManager. Note that the percentage is different depending on the region type (heap or offheap). Also the percentage can be changed at runtime on the ResourceManager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450302#comment-16450302 ] ASF subversion and git services commented on GEODE-5129: Commit 4f54820bb8503254cbe1f593a0d9d43be499b1dd in geode's branch refs/heads/feature/GEODE-5129 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f54820 ] GEODE-5129 Amend DistributedTestRule to honor the vmCount parameter when < 4 hosts > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5122) type arguments given on a raw type error
[
https://issues.apache.org/jira/browse/GEODE-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450296#comment-16450296
]
ASF subversion and git services commented on GEODE-5122:
Commit af3e575a120ba01b1db5c9a82e23ea6e95a5c5a0 in geode's branch
refs/heads/develop from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=af3e575 ]
GEODE-5122: Removed the type argument (#1840)
* Removed the type argument from the raw type.
* This was coming up as an error in IDE.
> type arguments given on a raw type error
> -
>
> Key: GEODE-5122
> URL: https://issues.apache.org/jira/browse/GEODE-5122
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In LuceneQueryFunctionJUnitTest we were seeing the following errors in the
> IDE
> {noformat}
> type arguments given on a raw type error
> {noformat}
> This was because we were assigning type arguments to the raw type Result
> Sender.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5129) Amend DistributedTestRule to honor the vmCount paramter < 4
[ https://issues.apache.org/jira/browse/GEODE-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer resolved GEODE-5129. -- Resolution: Fixed Fix Version/s: 1.7.0 > Amend DistributedTestRule to honor the vmCount paramter < 4 > --- > > Key: GEODE-5129 > URL: https://issues.apache.org/jira/browse/GEODE-5129 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4996) NullPointerException during HAEventWrapper serialization
[
https://issues.apache.org/jira/browse/GEODE-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barry Oglesby resolved GEODE-4996.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> NullPointerException during HAEventWrapper serialization
>
>
> Key: GEODE-4996
> URL: https://issues.apache.org/jira/browse/GEODE-4996
> Project: Geode
> Issue Type: Improvement
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> HAEventWrapper toData can throw NPE during HARegion GII.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.tier.sockets.HAEventWrapper.toData(HAEventWrapper.java:287)
> at
> org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2425)
> at
> org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1533)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2193)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2936)
> at org.apache.geode.internal.util.BlobHelper.serializeTo(BlobHelper.java:66)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.fillInValue(AbstractRegionEntry.java:411)
> at
> org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.chunkEntries(InitialImageOperation.java:1982)
> at
> org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.process(InitialImageOperation.java:1750)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1118)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:830)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4996) NullPointerException during HAEventWrapper serialization
[
https://issues.apache.org/jira/browse/GEODE-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450258#comment-16450258
]
ASF subversion and git services commented on GEODE-4996:
Commit f6dd58f83528b32bb0fb1a44da9bb47ea29f5df3 in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f6dd58f ]
GEODE-4996: Addressed NPE by always using the region entry key
> NullPointerException during HAEventWrapper serialization
>
>
> Key: GEODE-4996
> URL: https://issues.apache.org/jira/browse/GEODE-4996
> Project: Geode
> Issue Type: Improvement
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> HAEventWrapper toData can throw NPE during HARegion GII.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.tier.sockets.HAEventWrapper.toData(HAEventWrapper.java:287)
> at
> org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2425)
> at
> org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1533)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2193)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2936)
> at org.apache.geode.internal.util.BlobHelper.serializeTo(BlobHelper.java:66)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.fillInValue(AbstractRegionEntry.java:411)
> at
> org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.chunkEntries(InitialImageOperation.java:1982)
> at
> org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.process(InitialImageOperation.java:1750)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1118)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:830)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450254#comment-16450254 ] ASF subversion and git services commented on GEODE-5103: Commit 4a385b8ac4d7c1f6db6fc12c35e80871c7a1edbe in geode's branch refs/heads/develop from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a385b8 ] GEODE-5103: When applying transactional update on a replicate, callba… (#1825) * GEODE-5103: When applying transactional update on a replicate, callbacks should be always generated. Currently callbacks is not generated if a region entry is null possibly caused by rebalance etc. We still want the node to generate callbacks for its clients. > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450255#comment-16450255 ] ASF subversion and git services commented on GEODE-5103: Commit 4a385b8ac4d7c1f6db6fc12c35e80871c7a1edbe in geode's branch refs/heads/develop from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a385b8 ] GEODE-5103: When applying transactional update on a replicate, callba… (#1825) * GEODE-5103: When applying transactional update on a replicate, callbacks should be always generated. Currently callbacks is not generated if a region entry is null possibly caused by rebalance etc. We still want the node to generate callbacks for its clients. > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3438) Collection added to itself
[
https://issues.apache.org/jira/browse/GEODE-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450256#comment-16450256
]
ASF subversion and git services commented on GEODE-3438:
Commit 147c9d54dcc2d03704e6cb4ddfc2fa36fa70278f in geode's branch
refs/heads/develop from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=147c9d5 ]
GEODE-3438: Removed unused constructor and method (#1832)
> Collection added to itself
> --
>
> Key: GEODE-3438
> URL: https://issues.apache.org/jira/browse/GEODE-3438
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: JC
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Hi
> In a recent github mirror, I've found suspicious code.
> Branch: master
> Path:
> geode-core/src/main/java/org/apache/geode/management/internal/cli/domain/DurableCqNamesResult.java
> {code:java}
> ...
> 27 private List cqNames = new ArrayList();
> ...
> 33 public DurableCqNamesResult(final String memberNameOrId, List
> cqNames) {
> 34 super(memberNameOrId);
> 35 cqNames.addAll(cqNames);
> 36 }
> {code}
> In Line 35, should `cqNames.addAll' be `this.cqNames.addAll'? This might not
> be an issue, but I wanted to report just in case.
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450246#comment-16450246 ] ASF subversion and git services commented on GEODE-4728: Commit be8afc2e3ac41ee558cd374ba79b3a1377124cfc in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=be8afc2 ] Merge branch 'feature/GEODE-4728' into develop * feature/GEODE-4728: GEODE-4728: Docs - Re-introduce files from earlier version for updating GEODE-4728: Docs - update dotnet example README > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450248#comment-16450248 ] ASF subversion and git services commented on GEODE-4728: Commit be8afc2e3ac41ee558cd374ba79b3a1377124cfc in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=be8afc2 ] Merge branch 'feature/GEODE-4728' into develop * feature/GEODE-4728: GEODE-4728: Docs - Re-introduce files from earlier version for updating GEODE-4728: Docs - update dotnet example README > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450247#comment-16450247 ] ASF subversion and git services commented on GEODE-4728: Commit be8afc2e3ac41ee558cd374ba79b3a1377124cfc in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=be8afc2 ] Merge branch 'feature/GEODE-4728' into develop * feature/GEODE-4728: GEODE-4728: Docs - Re-introduce files from earlier version for updating GEODE-4728: Docs - update dotnet example README > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450249#comment-16450249 ] ASF subversion and git services commented on GEODE-4728: Commit be8afc2e3ac41ee558cd374ba79b3a1377124cfc in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=be8afc2 ] Merge branch 'feature/GEODE-4728' into develop * feature/GEODE-4728: GEODE-4728: Docs - Re-introduce files from earlier version for updating GEODE-4728: Docs - update dotnet example README > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450245#comment-16450245 ] ASF subversion and git services commented on GEODE-4728: Commit cadbed83eb1b38c44fc938d49c6392f4de3571ce in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=cadbed8 ] GEODE-4728: Docs - update dotnet example README > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5130) Refactor pipeline in anticipation of PR pipeline
[ https://issues.apache.org/jira/browse/GEODE-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5130: -- Labels: pull-request-available (was: ) > Refactor pipeline in anticipation of PR pipeline > > > Key: GEODE-5130 > URL: https://issues.apache.org/jira/browse/GEODE-5130 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > In order to facilitate the upcoming PR Pipeline functionality, refactor the > geode pipeline to be branch-independent, and dry up configuration via > templates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5132) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED
[
https://issues.apache.org/jira/browse/GEODE-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-5132:
---
Affects Version/s: 1.7.0
> CI failure:
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest
> > testParallelPropagationLoopBack3Sites FAILED
> ---
>
> Key: GEODE-5132
> URL: https://issues.apache.org/jira/browse/GEODE-5132
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.7.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> This failure occurred during CI:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296
> {noformat}
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest
> > testParallelPropagationLoopBack3Sites FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest$$Lambda$162/1703391551.run
> in VM 4 running on Host 83b9797d6847 with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.testParallelPropagationLoopBack3Sites(ParallelWANPropagationLoopBackDUnitTest.java:210)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition defined as a
> lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that
> uses int, intorg.apache.geode.cache.Region null within 3 milliseconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2721)
> at
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2706)
> at
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.lambda$testParallelPropagationLoopBack3Sites$bb17a952$21(ParallelWANPropagationLoopBackDUnitTest.java:210)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5132) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED
Shelley Lynn Hughes-Godfrey created GEODE-5132:
--
Summary: CI failure:
org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest
> testParallelPropagationLoopBack3Sites FAILED
Key: GEODE-5132
URL: https://issues.apache.org/jira/browse/GEODE-5132
Project: Geode
Issue Type: Bug
Components: wan
Reporter: Shelley Lynn Hughes-Godfrey
This failure occurred during CI:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296
{noformat}
org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest
> testParallelPropagationLoopBack3Sites FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest$$Lambda$162/1703391551.run
in VM 4 running on Host 83b9797d6847 with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
at
org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.testParallelPropagationLoopBack3Sites(ParallelWANPropagationLoopBackDUnitTest.java:210)
Caused by:
org.awaitility.core.ConditionTimeoutException: Condition defined as a
lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses
int, intorg.apache.geode.cache.Region null within 3 milliseconds.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
at
org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2721)
at
org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2706)
at
org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.lambda$testParallelPropagationLoopBack3Sites$bb17a952$21(ParallelWANPropagationLoopBackDUnitTest.java:210)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5131) CI failure: org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > testParallelPropagationSenderResume FAILED
[
https://issues.apache.org/jira/browse/GEODE-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-5131:
---
Affects Version/s: 1.7.0
> CI failure:
> org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest
> > testParallelPropagationSenderResume FAILED
>
>
> Key: GEODE-5131
> URL: https://issues.apache.org/jira/browse/GEODE-5131
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.7.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> This failure occurred during CI on develop:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest
> > testParallelPropagationSenderResume FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderOperationsDUnitTest$$Lambda$79/470558236.run
> in VM 4 running on Host 1f5f8948cda6 with 8 VMs
> Caused by:
> java.lang.AssertionError: Expected events in all primary queues after
> drain is 0 expected:<0> but was:<1>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5120) Remove DistributedSystem from Public API
[ https://issues.apache.org/jira/browse/GEODE-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450221#comment-16450221 ] ASF subversion and git services commented on GEODE-5120: Commit 5b1411fe80174fcb3b306c1b426161389df1c9e3 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5b1411f ] GEODE-5120: Remove DistributedSystem from public API. > Remove DistributedSystem from Public API > > > Key: GEODE-5120 > URL: https://issues.apache.org/jira/browse/GEODE-5120 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > DistributedSystem not need to be exposed publicly anymore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5131) CI failure: org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > testParallelPropagationSenderResume FAILED
Shelley Lynn Hughes-Godfrey created GEODE-5131:
--
Summary: CI failure:
org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest
> testParallelPropagationSenderResume FAILED
Key: GEODE-5131
URL: https://issues.apache.org/jira/browse/GEODE-5131
Project: Geode
Issue Type: Bug
Components: wan
Reporter: Shelley Lynn Hughes-Godfrey
This failure occurred during CI on develop:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296
{noformat}
org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest
> testParallelPropagationSenderResume FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderOperationsDUnitTest$$Lambda$79/470558236.run
in VM 4 running on Host 1f5f8948cda6 with 8 VMs
Caused by:
java.lang.AssertionError: Expected events in all primary queues after
drain is 0 expected:<0> but was:<1>
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals
[ https://issues.apache.org/jira/browse/GEODE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-4624. -- Resolution: Fixed > Add a new stat for AyncEventQueue/GatewaySender to track the processing of > queueRemovals > > > Key: GEODE-4624 > URL: https://issues.apache.org/jira/browse/GEODE-4624 > Project: Geode > Issue Type: Bug > Components: docs, wan >Affects Versions: 1.5.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We currently track the number of events queues, queue size and > eventsDistributed ... but we don't track the number of events removed via > queue removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5020) Move HARegionQueue system properties to SystemPropertyHelper
[ https://issues.apache.org/jira/browse/GEODE-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5020. -- Resolution: Fixed Fix Version/s: 1.7.0 > Move HARegionQueue system properties to SystemPropertyHelper > > > Key: GEODE-5020 > URL: https://issues.apache.org/jira/browse/GEODE-5020 > Project: Geode > Issue Type: Improvement > Components: client queues >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The two system properties are "MessageTimeToLive" and "threadIdExpiryTime." > HARegionQueue should use SystemPropertyHelper to get the optional values for > these properties so that geode. or gemfire. may be used as the prefix. > (I ran into this while cleaning up tests for GEODE-1279) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5040) CI Failure: RegionExpirationDistributedTest.regionExpiresAfterTtl
[
https://issues.apache.org/jira/browse/GEODE-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-5040.
--
Resolution: Fixed
Fix Version/s: 1.7.0
Fix was merged to develop. I'm not sure why the automatic comment wasn't added.
> CI Failure: RegionExpirationDistributedTest.regionExpiresAfterTtl
> -
>
> Key: GEODE-5040
> URL: https://issues.apache.org/jira/browse/GEODE-5040
> Project: Geode
> Issue Type: Bug
> Components: expiration, tests
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.cache.RegionExpirationDistributedTest >
> regionExpiresAfterTtl(DESTROY) FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.RegionExpirationDistributedTest$$Lambda$63/1961035464.run
> in VM 1 running on Host 6bb748d43f1f with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.cache.RegionExpirationDistributedTest.regionExpiresAfterTtl(RegionExpirationDistributedTest.java:127)
> Caused by:
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/RegionExpirationDistributedTest_regionExpiresAfterTtl';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
> at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8834)
> at java.util.TreeMap.putAll(TreeMap.java:313)
> at java.util.TreeMap.(TreeMap.java:185)
> at
> org.assertj.core.presentation.StandardRepresentation.toSortedMapIfPossible(StandardRepresentation.java:304)
> at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:284)
> at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:167)
> at
> org.assertj.core.error.ShouldBeEqual.actualAndExpectedHaveSameStringRepresentation(ShouldBeEqual.java:131)
> at
> org.assertj.core.error.ShouldBeEqual.newAssertionError(ShouldBeEqual.java:109)
> at org.assertj.core.internal.Failures.failure(Failures.java:96)
> at org.assertj.core.internal.Objects.assertNull(Objects.java:360)
> at
> org.assertj.core.api.AbstractAssert.isNull(AbstractAssert.java:274)
> at
> org.apache.geode.cache.RegionExpirationDistributedTest$Verification.assertRegionStateInRemoteMember(RegionExpirationDistributedTest.java:184)
> at
> org.apache.geode.cache.RegionExpirationDistributedTest.lambda$regionExpiresAfterTtl$7f930bcf$3(RegionExpirationDistributedTest.java:128)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5130) Refactor pipeline in anticipation of PR pipeline
Sean Goller created GEODE-5130: -- Summary: Refactor pipeline in anticipation of PR pipeline Key: GEODE-5130 URL: https://issues.apache.org/jira/browse/GEODE-5130 Project: Geode Issue Type: Improvement Components: ci Reporter: Sean Goller In order to facilitate the upcoming PR Pipeline functionality, refactor the geode pipeline to be branch-independent, and dry up configuration via templates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450193#comment-16450193 ] ASF subversion and git services commented on GEODE-5070: Commit 2dcc0820e823bf06e2b412c059e9d2d7d11cc4ca in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2dcc082 ] GEODE-5070: Use a random member for describe & list jdbc connector commands (#1849) Retrieves connections & mappings from CC(if running) or from a random member(if CC not running) > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
