[jira] [Updated] (GEODE-9913) A retried event can fail if the original event is still being processed and a new event for that same key occurs at the same time
[ https://issues.apache.org/jira/browse/GEODE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-9913: - Labels: GeodeOperationAPI pull-request-available (was: pull-request-available) > A retried event can fail if the original event is still being processed and a > new event for that same key occurs at the same time > - > > Key: GEODE-9913 > URL: https://issues.apache.org/jira/browse/GEODE-9913 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9912) Add unique identifier to DUnit log lines
[
https://issues.apache.org/jira/browse/GEODE-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472191#comment-17472191
]
ASF subversion and git services commented on GEODE-9912:
Commit 0f9f23736edea3be62bb0add94a9076009dafc81 in geode's branch
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0f9f237 ]
GEODE-9924: Avoid merging repeat test logs (#7246)
PROBLEM
Our repeat test tasks merge the output from all executions of a given
test class, making it very difficult to diagnose failures in repeat
tests.
CAUSE
In order to run tests repeatedly, our repeat test tasks override Gradle
code to allow a test class to execute more than once. Gradle's test
reporting code does not expect this. It directs the output from each
test to a log associated with the test class name, not with the specific
execution of the test class. This results in merging the outputs from
different executions of the same class.
SOLUTION
Change Gradle to distinguish separate executions of a test class, and to
log the output from each execution separately.
Components:
- New `ExecutionTrackingTestResultProcessor` class: Wraps a given test
result processor to append an execution identifier (a simple counter)
to the name of the test class when reporting results. Gradle
associates the output with this execution-specific name instead of
with the class name.
- New `ExecutionTrackingTestClassProcessor` class: Wraps a given test
class processor to report via an
`ExecutionTrackingTestResultProcessor`.
- Change `RepeatTestExecuter` to use an
`ExecutionTrackingTestClassProcessor`.
This commit also reverts GEODE-9912, which partially addressed the same
problem by adding an execution ID to each log line from a DUnit ChildVM.
The execution ID made it possible to identify the source of each merged
log line. GEODE-9924 (this commit) makes the changes from GEODE-9912
unnecessary.
NOTES
- Gradle now creates distinct XML and HTML report files for each
execution of a given test class.
- The test summary HTML page created by Gradle lists each test class
execution separately. If a class named `FooTest` executes 50 times (as
in a stress test run), the summary will list `FooTest-01`,
`FooTest-02`, ..., `FooTest-50` as if they were separate test classes.
> Add unique identifier to DUnit log lines
>
>
> Key: GEODE-9912
> URL: https://issues.apache.org/jira/browse/GEODE-9912
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> Adding an arbitrary random string to DUnit log lines allows to distinguish
> individual test output for repeated tests. In such cases tests run in
> parallel and individual test log lines are interleaved making debugging very
> difficult. So log lines would look something like:
> {noformat}
> [vm0-51ec] [info 2021/12/24 15:43:54.367 UTC Connection(1)-10.138.0.70>; tid=0x1d] Reinitializing JarDeploymentService
> with new working directory: null
> [vm0-47b7] [info 2021/12/24 15:43:54.416 UTC Connection(1)-10.138.0.70> tid=0x1d] Reinitializing JarDeploymentService with
> new working directory: null
> [vm1-47b7] [info 2021/12/24 15:43:54.431 UTC Connection(1)-10.138.0.70> tid=0x1d] Received method:
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call with 0 args on
> object: IdentifiableCallable(0:start locator in vm0)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9924) Make repeat tests log each test class instance separately
[ https://issues.apache.org/jira/browse/GEODE-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472190#comment-17472190 ] ASF subversion and git services commented on GEODE-9924: Commit 0f9f23736edea3be62bb0add94a9076009dafc81 in geode's branch refs/heads/develop from Dale Emery [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0f9f237 ] GEODE-9924: Avoid merging repeat test logs (#7246) PROBLEM Our repeat test tasks merge the output from all executions of a given test class, making it very difficult to diagnose failures in repeat tests. CAUSE In order to run tests repeatedly, our repeat test tasks override Gradle code to allow a test class to execute more than once. Gradle's test reporting code does not expect this. It directs the output from each test to a log associated with the test class name, not with the specific execution of the test class. This results in merging the outputs from different executions of the same class. SOLUTION Change Gradle to distinguish separate executions of a test class, and to log the output from each execution separately. Components: - New `ExecutionTrackingTestResultProcessor` class: Wraps a given test result processor to append an execution identifier (a simple counter) to the name of the test class when reporting results. Gradle associates the output with this execution-specific name instead of with the class name. - New `ExecutionTrackingTestClassProcessor` class: Wraps a given test class processor to report via an `ExecutionTrackingTestResultProcessor`. - Change `RepeatTestExecuter` to use an `ExecutionTrackingTestClassProcessor`. This commit also reverts GEODE-9912, which partially addressed the same problem by adding an execution ID to each log line from a DUnit ChildVM. The execution ID made it possible to identify the source of each merged log line. GEODE-9924 (this commit) makes the changes from GEODE-9912 unnecessary. NOTES - Gradle now creates distinct XML and HTML report files for each execution of a given test class. - The test summary HTML page created by Gradle lists each test class execution separately. If a class named `FooTest` executes 50 times (as in a stress test run), the summary will list `FooTest-01`, `FooTest-02`, ..., `FooTest-50` as if they were separate test classes. > Make repeat tests log each test class instance separately > - > > Key: GEODE-9924 > URL: https://issues.apache.org/jira/browse/GEODE-9924 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Currently, our repeat test tasks merge the output from all executions of a > given test class, making it very difficult to diagnose failures in repeat > tests. > CAUSE: > In order to run tests repeatedly, our repeat test tasks override Gradle code > to allow a test class to execute more than once. > Gradle directs the output from each test to a log associated with the test > class name. > SOLUTION: > Change Gradle to distinguish separate executions of a test class, and to log > the output from each execution separately. This can be done by using a custom > "test result processor" that appends an iteration counter to the end of the > test class name before processing the result. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8980) bump dependencies for 1.15.0 [PERMANENT]
[ https://issues.apache.org/jira/browse/GEODE-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472209#comment-17472209 ] ASF subversion and git services commented on GEODE-8980: Commit 34041266fe518910eced77b1804d92d8bf9f3a38 in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3404126 ] GEODE-8980: bump dependencies (#7250) * Bump annotations from 22.0.0 to 23.0.0 * Bump assertj-core from 3.20.2 to 3.22.0 * Bump awaitility from 4.1.0 to 4.1.1 * Bump cargo from 1.9.7 to 1.9.9 * Bump classgraph from 4.8.115 to 4.8.138 * Bump fastutil from 8.5.4 to 8.5.6 * Bump geo from 0.7.7 to 0.8.0 * Bump guava from 30.1.1-jre to 31.0.1-jre * Bump httpcore from 4.4.14 to 4.4.15 * Bump jackson-databind from 2.12.3 to 2.13.1 * Bump java-jq from 1.1.0 to 1.2.0 * Bump jetty from 9.4.43.v20210629 to 9.4.44.v20210927 * Bump jna from 5.9.0 to 5.10.0 * Bump junit-jupiter from 5.7.2 to 5.8.2 * Bump lettuce from 6.1.4.RELEASE to 6.1.5.RELEASE * Bump micrometer from 1.7.3 to 1.8.1 * Bump mockito from 4.0.0 to 4.2.0 * Bump netty from 4.1.70.Final to 4.1.72.Final * Bump pmd from 6.37.0 to 6.41.0 * Bump randomizedtesting-runner from 2.7.8 to 2.7.9 * Bump slf4j from 1.7.30 to 1.7.32 * Bump spring from 5.3.9 to 5.3.14 * Bump spring-boot-starter from 2.5.4 to 2.6.2 * Bump spring-hateoas from 1.3.3 to 1.4.0 * Bump spring-ldap from 2.3.2.RELEASE to 2.3.5.RELEASE * Bump spring-security from 5.5.2 to 5.6.1 * Bump spring-session-data-redis from 2.5.2 to 2.6.1 * Bump tomcat from 9.0.50 to 9.0.56 > bump dependencies for 1.15.0 [PERMANENT] > > > Key: GEODE-8980 > URL: https://issues.apache.org/jira/browse/GEODE-8980 > Project: Geode > Issue Type: Improvement > Components: build >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > keeping up with the latest versions of 3rd-party libraries used by Geode is a > proactive way to reduce bugs and avoid security vulnerabilities. this ticket > will be used for ~monthly dependency bumps on develop until we get close to > cutting support/1.15 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-6588) Cleanup internal use of generics and other static analyzer warnings [PERMANENT]
[ https://issues.apache.org/jira/browse/GEODE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472215#comment-17472215 ] ASF subversion and git services commented on GEODE-6588: Commit 31b03862e349128f10f7cc513564b0b63f78319f in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=31b0386 ] GEODE-6588: Cleanup static analyzer warnings. > Cleanup internal use of generics and other static analyzer warnings > [PERMANENT] > --- > > Key: GEODE-6588 > URL: https://issues.apache.org/jira/browse/GEODE-6588 > Project: Geode > Issue Type: Task >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 8h 40m > Remaining Estimate: 0h > > Use generics where possible. > Cleanup other static analyzer issues along the way. > Generally make the IntelliJ analyzer gutter less cluttered. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7934) CI Failure: CacheManagementDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472214#comment-17472214
]
ASF subversion and git services commented on GEODE-7934:
Commit 4995d1814ba1994e80c77768ebba7372ff225e89 in geode's branch
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4995d18 ]
GEODE-7934: Use thread safe list type.
> CI Failure: CacheManagementDUnitTest
>
>
> Key: GEODE-7934
> URL: https://issues.apache.org/jira/browse/GEODE-7934
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Jacob Barrett
>Priority: Major
> Labels: flaky, pull-request-available
>
> CacheManagementDUnitTest.testNotification and
> CacheManagementDUnitTest.testManagerShutdown have failed with the following
> output:
>
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testNotification FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running
> on Host 12ab33057072 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:424)
> at
> org.apache.geode.management.CacheManagementDUnitTest.verifyNotificationsAndRegionSize(CacheManagementDUnitTest.java:637)
> at
> org.apache.geode.management.CacheManagementDUnitTest.testNotification(CacheManagementDUnitTest.java:266)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a org.apache.geode.management.CacheManagementDUnitTest
> expected:<[45]> but was:<[30]> within 300 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyNotificationsAndRegionSize$aeb9a697$1(CacheManagementDUnitTest.java:638)
> Caused by:
> org.junit.ComparisonFailure: expected:<[45]> but was:<[30]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.management.CacheManagementDUnitTest.lambda$null$4(CacheManagementDUnitTest.java:638)
> {code}
>
>
>
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testManagerShutdown
> FAILEDorg.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running
> on Host 9e4a1b86b19b with 4 VMsat
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)at
> org.apache.geode.test.dunit.VM.invoke(VM.java:424)at
> org.apache.geode.management.CacheManagementDUnitTest.verifyManagerStopped(CacheManagementDUnitTest.java:377)
> at
> org.apache.geode.management.CacheManagementDUnitTest.testManagerShutdown(CacheManagementDUnitTest.java:200)
> Caused by:java.lang.AssertionError: Expecting empty
> but was:<[GemFire:type=Member,member=memberVM-3]>at
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyManagerStopped$36a0fae1$1(CacheManagementDUnitTest.java:391)
> {code}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1699]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1676]
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1519
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9832) SMOVE Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472218#comment-17472218 ] ASF subversion and git services commented on GEODE-9832: Commit 8bbc5ef23045eab3983b3bcff59718028e7474c3 in geode's branch refs/heads/develop from Kris10 [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8bbc5ef ] GEODE-9832: SMOVE Command Support (#7227) > SMOVE Command Supported > --- > > Key: GEODE-9832 > URL: https://issues.apache.org/jira/browse/GEODE-9832 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > > The SMOVE command has been implemented but lacks sufficient testing to ensure > that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9869) Remove redis-related options from gfsh commands
[
https://issues.apache.org/jira/browse/GEODE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Ingles resolved GEODE-9869.
---
Fix Version/s: 1.15.0
Resolution: Fixed
Remove the GFSH options related to geode-for-redis and update docs, examples,
and tests to set such options via Java properties.
> Remove redis-related options from gfsh commands
> ---
>
> Key: GEODE-9869
> URL: https://issues.apache.org/jira/browse/GEODE-9869
> Project: Geode
> Issue Type: Improvement
> Components: gfsh, redis
>Reporter: Jens Deppe
>Assignee: Ray Ingles
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> To work towards Geode modularity, remove the redis-related options from gfsh
> commands. Specifically {{gfsh start server}} supports:
> * {{--geode-for-redis-port}}
> * {{--geode-for-redis-bind-address}}
> * {{--geode-for-redis-username}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9869) Remove redis-related options from gfsh commands
[
https://issues.apache.org/jira/browse/GEODE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Ingles reassigned GEODE-9869:
-
Assignee: Ray Ingles
> Remove redis-related options from gfsh commands
> ---
>
> Key: GEODE-9869
> URL: https://issues.apache.org/jira/browse/GEODE-9869
> Project: Geode
> Issue Type: Improvement
> Components: gfsh, redis
>Reporter: Jens Deppe
>Assignee: Ray Ingles
>Priority: Major
> Labels: pull-request-available
>
> To work towards Geode modularity, remove the redis-related options from gfsh
> commands. Specifically {{gfsh start server}} supports:
> * {{--geode-for-redis-port}}
> * {{--geode-for-redis-bind-address}}
> * {{--geode-for-redis-username}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9869) Remove redis-related options from gfsh commands
[
https://issues.apache.org/jira/browse/GEODE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472235#comment-17472235
]
ASF subversion and git services commented on GEODE-9869:
Commit e7ca26f6e7cfddead08a830bf1a3a16f17106111 in geode's branch
refs/heads/develop from Ray Ingles
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e7ca26f ]
GEODE-9869: Remove geode-for-redis properties from gfsh options (#7205)
Geode-for-Redis options are now gemfire properties. Remove the GFSH options
related to geode-for-redis and update docs, examples, and tests to set such
options as Java properties.
> Remove redis-related options from gfsh commands
> ---
>
> Key: GEODE-9869
> URL: https://issues.apache.org/jira/browse/GEODE-9869
> Project: Geode
> Issue Type: Improvement
> Components: gfsh, redis
>Reporter: Jens Deppe
>Assignee: Ray Ingles
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> To work towards Geode modularity, remove the redis-related options from gfsh
> commands. Specifically {{gfsh start server}} supports:
> * {{--geode-for-redis-port}}
> * {{--geode-for-redis-bind-address}}
> * {{--geode-for-redis-username}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (GEODE-9904) RedisSet spop and srandmember should not copy entire MemberSet
[ https://issues.apache.org/jira/browse/GEODE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen closed GEODE-9904. -- > RedisSet spop and srandmember should not copy entire MemberSet > -- > > Key: GEODE-9904 > URL: https://issues.apache.org/jira/browse/GEODE-9904 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Kristen >Priority: Major > Labels: release-blocker > > The current implementation of RedisSet spop and srandmember always copy the > entire MemberSet. So if you have a redis set with a million items, and than > ask for one random one, instead of it reading just one of the items out of > the set it first copies the entire set. > The call that makes the copy is "members.toArray". It should be pretty easy > to add spop and srandmember support to the MemberSet super class. Since > MemberSet uses a flat array to store its items it should work well with > supporting indexing of its array to get a random element. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9904) RedisSet spop and srandmember should not copy entire MemberSet
[ https://issues.apache.org/jira/browse/GEODE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen resolved GEODE-9904. Resolution: Not A Problem > RedisSet spop and srandmember should not copy entire MemberSet > -- > > Key: GEODE-9904 > URL: https://issues.apache.org/jira/browse/GEODE-9904 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Kristen >Priority: Major > Labels: release-blocker > > The current implementation of RedisSet spop and srandmember always copy the > entire MemberSet. So if you have a redis set with a million items, and than > ask for one random one, instead of it reading just one of the items out of > the set it first copies the entire set. > The call that makes the copy is "members.toArray". It should be pretty easy > to add spop and srandmember support to the MemberSet super class. Since > MemberSet uses a flat array to store its items it should work well with > supporting indexing of its array to get a random element. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9934) AbstractMemoryOverheadIntegrationTest is in the wrong package
[
https://issues.apache.org/jira/browse/GEODE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans resolved GEODE-9934.
Fix Version/s: 1.15.0
Resolution: Fixed
> AbstractMemoryOverheadIntegrationTest is in the wrong package
> -
>
> Key: GEODE-9934
> URL: https://issues.apache.org/jira/browse/GEODE-9934
> Project: Geode
> Issue Type: Task
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The class {{AbstractMemoryOverheadIntegrationTest}} and its subclasses
> currently reside in the
> {{org.apache.geode.redis.internal.commands.executor.hash}} package. This is
> incorrect, so the classes should be moved to a more appropriate package, such
> as {{{}org.apache.geode.redis.internal.data{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9934) AbstractMemoryOverheadIntegrationTest is in the wrong package
[
https://issues.apache.org/jira/browse/GEODE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472252#comment-17472252
]
ASF subversion and git services commented on GEODE-9934:
Commit 79c606ff8bf49dcdbea343ace050a9eb74bffa1d in geode's branch
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=79c606f ]
GEODE-9934: Move Redis MemoryOverheadIntegration test classes (#7249)
- Change package for AbstractMemoryOverheadIntegrationTest and child
classes from org.apache.geode.redis.internal.commands.executor.hash to
org.apache.geode.redis.internal.data
Authored-by: Donal Evans
> AbstractMemoryOverheadIntegrationTest is in the wrong package
> -
>
> Key: GEODE-9934
> URL: https://issues.apache.org/jira/browse/GEODE-9934
> Project: Geode
> Issue Type: Task
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The class {{AbstractMemoryOverheadIntegrationTest}} and its subclasses
> currently reside in the
> {{org.apache.geode.redis.internal.commands.executor.hash}} package. This is
> incorrect, so the classes should be moved to a more appropriate package, such
> as {{{}org.apache.geode.redis.internal.data{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9935) CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
Hale Bales created GEODE-9935:
-
Summary: CI Failure: RollingUpgradeWithGfshDUnitTest >
testRollingUpgradeWithDeployment
Key: GEODE-9935
URL: https://issues.apache.org/jira/browse/GEODE-9935
Project: Geode
Issue Type: Bug
Components: gfsh
Affects Versions: 1.15.0
Reporter: Hale Bales
CI Failure in upgrade tests in RollingUpgradeWithGfshDUnitTest >
testRollingUpgradeWithDeployment. starting locator exits with status of 1, not
the expected 0.
{code:java}
> Task :geode-assembly:upgradeTest
RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.10.0]
FAILED
org.opentest4j.AssertionFailedError: [Exit value from process started by
[e35c359d41713de9: gfsh -e start locator --name=loc2 --port=24585
--http-service-port=0 --locators=localhost[24583]
--J=-Dgemfire.jmx-manager-port=24586]]
expected: 0
but was: 1
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153)
at
org.apache.geode.management.RollingUpgradeWithGfshDUnitTest.testRollingUpgradeWithDeployment(RollingUpgradeWithGfshDUnitTest.java:107)
134 tests completed, 1 failed
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-results/upgradeTest/1641589807/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-artifacts/1641589807/upgradetestfiles-openjdk8-1.15.0-build.0767.tgz
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9935) CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
[
https://issues.apache.org/jira/browse/GEODE-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales updated GEODE-9935:
--
Labels: needsTriage (was: )
> CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
> --
>
> Key: GEODE-9935
> URL: https://issues.apache.org/jira/browse/GEODE-9935
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Priority: Major
> Labels: needsTriage
>
> CI Failure in upgrade tests in RollingUpgradeWithGfshDUnitTest >
> testRollingUpgradeWithDeployment. starting locator exits with status of 1,
> not the expected 0.
> {code:java}
> > Task :geode-assembly:upgradeTest
> RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.10.0]
> FAILED
> org.opentest4j.AssertionFailedError: [Exit value from process started by
> [e35c359d41713de9: gfsh -e start locator --name=loc2 --port=24585
> --http-service-port=0 --locators=localhost[24583]
> --J=-Dgemfire.jmx-manager-port=24586]]
> expected: 0
> but was: 1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153)
> at
> org.apache.geode.management.RollingUpgradeWithGfshDUnitTest.testRollingUpgradeWithDeployment(RollingUpgradeWithGfshDUnitTest.java:107)
> 134 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-results/upgradeTest/1641589807/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-artifacts/1641589807/upgradetestfiles-openjdk8-1.15.0-build.0767.tgz
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9935) CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
[
https://issues.apache.org/jira/browse/GEODE-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472263#comment-17472263
]
Geode Integration commented on GEODE-9935:
--
Seen in [upgrade-test-openjdk8
#81|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/81]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-results/upgradeTest/1641589807/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-artifacts/1641589807/upgradetestfiles-openjdk8-1.15.0-build.0767.tgz].
> CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
> --
>
> Key: GEODE-9935
> URL: https://issues.apache.org/jira/browse/GEODE-9935
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Priority: Major
> Labels: needsTriage
>
> CI Failure in upgrade tests in RollingUpgradeWithGfshDUnitTest >
> testRollingUpgradeWithDeployment. starting locator exits with status of 1,
> not the expected 0.
> {code:java}
> > Task :geode-assembly:upgradeTest
> RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.10.0]
> FAILED
> org.opentest4j.AssertionFailedError: [Exit value from process started by
> [e35c359d41713de9: gfsh -e start locator --name=loc2 --port=24585
> --http-service-port=0 --locators=localhost[24583]
> --J=-Dgemfire.jmx-manager-port=24586]]
> expected: 0
> but was: 1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153)
> at
> org.apache.geode.management.RollingUpgradeWithGfshDUnitTest.testRollingUpgradeWithDeployment(RollingUpgradeWithGfshDUnitTest.java:107)
> 134 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-results/upgradeTest/1641589807/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-artifacts/1641589807/upgradetestfiles-openjdk8-1.15.0-build.0767.tgz
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
[
https://issues.apache.org/jira/browse/GEODE-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales reassigned GEODE-9889:
-
Assignee: Hale Bales
> LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
> ---
>
> Key: GEODE-9889
> URL: https://issues.apache.org/jira/browse/GEODE-9889
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Ray Ingles
>Assignee: Hale Bales
>Priority: Major
>
> Seen in a CI build:
>
> {{> Task :geode-apis-compatible-with-redis:integrationTest}}
> {{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> > subscribePsubscribeSameClient FAILED}}
> {{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9936) Throw error for commands with multiple keys that contains the wrong type key
Kristen created GEODE-9936: -- Summary: Throw error for commands with multiple keys that contains the wrong type key Key: GEODE-9936 URL: https://issues.apache.org/jira/browse/GEODE-9936 Project: Geode Issue Type: Bug Reporter: Kristen For commands that take in multiple keys as arguments, it does not throw an error if the arguments consist of a valid key followed by a different type key. Fix it so a wrong type error is thrown and add two test. One test should takes in valid key followed by a different type key. Then the other test should switch the ordering of the keys. The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SDIFF, and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9936) Throw error for commands with multiple keys that contains the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9936: --- Labels: redis (was: ) > Throw error for commands with multiple keys that contains the wrong type key > > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug >Reporter: Kristen >Priority: Major > Labels: redis > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SDIFF, > and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9936) Throw error for commands with multiple keys that contains the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen reassigned GEODE-9936: -- Assignee: Kristen > Throw error for commands with multiple keys that contains the wrong type key > > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug >Reporter: Kristen >Assignee: Kristen >Priority: Major > Labels: redis > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SDIFF, > and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9902) Modify ZUnionStore and ZInterStore storing methods
[ https://issues.apache.org/jira/browse/GEODE-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen resolved GEODE-9902. Resolution: Fixed > Modify ZUnionStore and ZInterStore storing methods > -- > > Key: GEODE-9902 > URL: https://issues.apache.org/jira/browse/GEODE-9902 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Kristen >Assignee: Kristen >Priority: Major > Labels: pull-request-available, release-blocker > > Modify the way Redis SortedSets store the members for the ZUnionStore and > ZInterStore. It should follow what Redis Sets are doing for SUnionStore and > SInterStore. This is specifically related to the use of DeltaInfos. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9832) SMOVE Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen resolved GEODE-9832. Resolution: Fixed > SMOVE Command Supported > --- > > Key: GEODE-9832 > URL: https://issues.apache.org/jira/browse/GEODE-9832 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > > The SMOVE command has been implemented but lacks sufficient testing to ensure > that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9828) SDIFFSTORE Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen resolved GEODE-9828. Resolution: Fixed > SDIFFSTORE Command Supported > > > Key: GEODE-9828 > URL: https://issues.apache.org/jira/browse/GEODE-9828 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > > The SDIFFSTORE command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9936) Throw error for commands with multiple keys that contains the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9936: --- Description: For commands that take in multiple keys as arguments, it does not throw an error if the arguments consist of a valid key followed by a different type key. Fix it so a wrong type error is thrown and add two test. One test should takes in valid key followed by a different type key. Then the other test should switch the ordering of the keys. The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SMOVE, SDIFF, and SDIFFSTORE was: For commands that take in multiple keys as arguments, it does not throw an error if the arguments consist of a valid key followed by a different type key. Fix it so a wrong type error is thrown and add two test. One test should takes in valid key followed by a different type key. Then the other test should switch the ordering of the keys. The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SDIFF, and SDIFFSTORE > Throw error for commands with multiple keys that contains the wrong type key > > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug >Reporter: Kristen >Assignee: Kristen >Priority: Major > Labels: redis > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SMOVE, > SDIFF, and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9936) Throw error for commands with multiple keys that contains the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9936: --- Labels: (was: redis) > Throw error for commands with multiple keys that contains the wrong type key > > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug >Reporter: Kristen >Assignee: Kristen >Priority: Major > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SMOVE, > SDIFF, and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9936) Throw error for commands with multiple keys that contains the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9936: --- Component/s: redis > Throw error for commands with multiple keys that contains the wrong type key > > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Kristen >Assignee: Kristen >Priority: Major > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SMOVE, > SDIFF, and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9936) Throw error for commands with multiple keys that contain the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9936: --- Summary: Throw error for commands with multiple keys that contain the wrong type key (was: Throw error for commands with multiple keys that contains the wrong type key) > Throw error for commands with multiple keys that contain the wrong type key > --- > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Kristen >Assignee: Kristen >Priority: Major > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SMOVE, > SDIFF, and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9937) Add convenience methods to FileWatchingX509Extended*Manager
[ https://issues.apache.org/jira/browse/GEODE-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-9937: - Assignee: Jens Deppe > Add convenience methods to FileWatchingX509Extended*Manager > --- > > Key: GEODE-9937 > URL: https://issues.apache.org/jira/browse/GEODE-9937 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9937) Add convenience methods to FileWatchingX509Extended*Manager
Jens Deppe created GEODE-9937: - Summary: Add convenience methods to FileWatchingX509Extended*Manager Key: GEODE-9937 URL: https://issues.apache.org/jira/browse/GEODE-9937 Project: Geode Issue Type: Improvement Components: security Reporter: Jens Deppe -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9937) Add convenience methods to FileWatchingX509Extended*Manager
[ https://issues.apache.org/jira/browse/GEODE-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9937: -- Labels: pull-request-available (was: ) > Add convenience methods to FileWatchingX509Extended*Manager > --- > > Key: GEODE-9937 > URL: https://issues.apache.org/jira/browse/GEODE-9937 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-7934) CI Failure: CacheManagementDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett resolved GEODE-7934.
--
Resolution: Fixed
> CI Failure: CacheManagementDUnitTest
>
>
> Key: GEODE-7934
> URL: https://issues.apache.org/jira/browse/GEODE-7934
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Jacob Barrett
>Priority: Major
> Labels: flaky, pull-request-available
>
> CacheManagementDUnitTest.testNotification and
> CacheManagementDUnitTest.testManagerShutdown have failed with the following
> output:
>
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testNotification FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running
> on Host 12ab33057072 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:424)
> at
> org.apache.geode.management.CacheManagementDUnitTest.verifyNotificationsAndRegionSize(CacheManagementDUnitTest.java:637)
> at
> org.apache.geode.management.CacheManagementDUnitTest.testNotification(CacheManagementDUnitTest.java:266)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a org.apache.geode.management.CacheManagementDUnitTest
> expected:<[45]> but was:<[30]> within 300 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyNotificationsAndRegionSize$aeb9a697$1(CacheManagementDUnitTest.java:638)
> Caused by:
> org.junit.ComparisonFailure: expected:<[45]> but was:<[30]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.management.CacheManagementDUnitTest.lambda$null$4(CacheManagementDUnitTest.java:638)
> {code}
>
>
>
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testManagerShutdown
> FAILEDorg.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running
> on Host 9e4a1b86b19b with 4 VMsat
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)at
> org.apache.geode.test.dunit.VM.invoke(VM.java:424)at
> org.apache.geode.management.CacheManagementDUnitTest.verifyManagerStopped(CacheManagementDUnitTest.java:377)
> at
> org.apache.geode.management.CacheManagementDUnitTest.testManagerShutdown(CacheManagementDUnitTest.java:200)
> Caused by:java.lang.AssertionError: Expecting empty
> but was:<[GemFire:type=Member,member=memberVM-3]>at
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyManagerStopped$36a0fae1$1(CacheManagementDUnitTest.java:391)
> {code}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1699]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1676]
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1519
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9938) Optimize SRANDMEMBER
Wayne created GEODE-9938: Summary: Optimize SRANDMEMBER Key: GEODE-9938 URL: https://issues.apache.org/jira/browse/GEODE-9938 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne The SRANDMEMBER Command may require later optimization to minimally copy the target members to the result set. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9939) Typo in error message
Dave Barnes created GEODE-9939: -- Summary: Typo in error message Key: GEODE-9939 URL: https://issues.apache.org/jira/browse/GEODE-9939 Project: Geode Issue Type: Bug Affects Versions: 1.14.2 Reporter: Dave Barnes >From a community member: The spelling “perameterization” is wrong in the codebase [https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/ge\ ode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125](https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/ge\ ode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client
[
https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales updated GEODE-8616:
--
Affects Version/s: 1.15.0
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client
[
https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472360#comment-17472360
]
Geode Integration commented on GEODE-8616:
--
Seen in [distributed-test-openjdk8
#89|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/89]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0771/test-results/distributedTest/1641853546/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0771/test-artifacts/1641853546/distributedtestfiles-openjdk8-1.15.0-build.0771.tgz].
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client
[
https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales updated GEODE-8616:
--
Affects Version/s: 1.13.7
1.14.3
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1, 1.13.7, 1.14.3, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9940) ci improvements
Owen Nichols created GEODE-9940: --- Summary: ci improvements Key: GEODE-9940 URL: https://issues.apache.org/jira/browse/GEODE-9940 Project: Geode Issue Type: Improvement Components: ci, release Reporter: Owen Nichols mass test may not trigger, RC my trigger prematurely/twice, etc -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9936) Throw error for commands with multiple keys that contain the wrong type key
[ https://issues.apache.org/jira/browse/GEODE-9936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9936: -- Labels: pull-request-available (was: ) > Throw error for commands with multiple keys that contain the wrong type key > --- > > Key: GEODE-9936 > URL: https://issues.apache.org/jira/browse/GEODE-9936 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Kristen >Assignee: Kristen >Priority: Major > Labels: pull-request-available > > For commands that take in multiple keys as arguments, it does not throw an > error if the arguments consist of a valid key followed by a different type > key. > Fix it so a wrong type error is thrown and add two test. One test should > takes in valid key followed by a different type key. Then the other test > should switch the ordering of the keys. > The following commands need to be checked: ZUNIONSTORE, ZINTERSTORE, SMOVE, > SDIFF, and SDIFFSTORE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9940) ci improvements
[ https://issues.apache.org/jira/browse/GEODE-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9940: -- Labels: pull-request-available (was: ) > ci improvements > --- > > Key: GEODE-9940 > URL: https://issues.apache.org/jira/browse/GEODE-9940 > Project: Geode > Issue Type: Improvement > Components: ci, release >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > mass test may not trigger, RC my trigger prematurely/twice, etc -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9940) ci improvements
[ https://issues.apache.org/jira/browse/GEODE-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472447#comment-17472447 ] ASF subversion and git services commented on GEODE-9940: Commit 152b09f7c3f1e073b9e89a09687e676d468bfe0b in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=152b09f ] GEODE-9940: ci improvements (#7254) * fix mass test report trigger * fix mass test report hang * fix rc pipeline to trigger right the first time > ci improvements > --- > > Key: GEODE-9940 > URL: https://issues.apache.org/jira/browse/GEODE-9940 > Project: Geode > Issue Type: Improvement > Components: ci, release >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > mass test may not trigger, RC my trigger prematurely/twice, etc -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9940) ci improvements
[ https://issues.apache.org/jira/browse/GEODE-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9940: Description: mass test report hangs, mass test may not trigger, RC may trigger prematurely/twice (was: mass test may not trigger, RC my trigger prematurely/twice, etc) > ci improvements > --- > > Key: GEODE-9940 > URL: https://issues.apache.org/jira/browse/GEODE-9940 > Project: Geode > Issue Type: Improvement > Components: ci, release >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > mass test report hangs, mass test may not trigger, RC may trigger > prematurely/twice -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9940) ci improvements
[ https://issues.apache.org/jira/browse/GEODE-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-9940. - Fix Version/s: 1.15.0 Resolution: Fixed > ci improvements > --- > > Key: GEODE-9940 > URL: https://issues.apache.org/jira/browse/GEODE-9940 > Project: Geode > Issue Type: Improvement > Components: ci, release >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > mass test may not trigger, RC my trigger prematurely/twice, etc -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9735) Avoid wan-copy region command to copy entries updated after it started
[ https://issues.apache.org/jira/browse/GEODE-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472512#comment-17472512 ] ASF subversion and git services commented on GEODE-9735: Commit efc526a1dcd6f27f8456337094657620b31de65a in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=efc526a ] GEODE-9735: Do not copy entries that have been updated after the comm… (#7003) * GEODE-9735: Do not copy entries that have been updated after the command was run * GEODE-9735: check if concurrencyChecksEnabled is true to use timestamps > Avoid wan-copy region command to copy entries updated after it started > -- > > Key: GEODE-9735 > URL: https://issues.apache.org/jira/browse/GEODE-9735 > Project: Geode > Issue Type: Improvement > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > > The wan-copy region command must not copy entries that have been created or > updated after the command has started to copy entries. > There are two reasons for this: > * Efficiency: entries copied after the command has been started will be > replicated by the gateway sender anyway so the copying of these entries by > the command will be a waste of processing resources and duplicated events > will arrive to the remote site. > * Problematic reordering of events in the receiving side: if an entry is > modified in the same millisecond in the source site and the wan-copy region > command tries to copy this entry, it might happen that the command reads the > first version of the entry and sends it to the remote site. The gateway > sender will also send two events to the remote site, one with the first > version of the entry and one with the second. If the event of the wan-copy > region command containing the first version of the entry arrives to the > remote site after the second event sent by the gateway sender, it will > overwrite the second version causing an inconsistency between the two sites. > The reason is that the granularity of the timestamp of events is of > milliseconds and therefore the conflict resolver on the receiving side will > not be able to detect that the event sent by the command is prior to the one > received by the gateway sender. > If entries updated while the command is running are not copied by the > command, this problem is avoided. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
