[jira] [Commented] (GEODE-5743) Refactor PdxType logic
[
https://issues.apache.org/jira/browse/GEODE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498142#comment-17498142
]
Michael Martell commented on GEODE-5743:
My name may be on this but I'm pretty sure I didn't write this ticket. And I
certainly haven't done the work.
> Refactor PdxType logic
> --
>
> Key: GEODE-5743
> URL: https://issues.apache.org/jira/browse/GEODE-5743
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Michael Martell
>Priority: Major
>
> It isn't publicly facing so I can be tackled after the next release but It
> should be refactored to make separate between C++ and .NET clean. This looks
> like the only faked type in the registry now to handle C++ and .NET override
> behavior. The rest have already been replaced with {{*Handler}} interfaces.
> This should be refactored out. It is not really a primitive type, it just
> pretends to be one. Give it the same treatment we did for {{PdxTypeHandler}}
> and {{DataSerializableHandler}}. In fact rename {{PdxTypeHander}} to
> {{PdxSerializableHandler}}, the current name is confusing with {{PdxType}},
> which is the meta-data about PDX objects. Then implement this {{PdxType}}
> logic as {{PdxTypeHandler}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager
[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498241#comment-17498241 ] ASF subversion and git services commented on GEODE-10063: - Commit 45cbe7f8df39704899b0305729749dc1cc9ffe89 in geode's branch refs/heads/develop from Eric Shu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=45cbe7f ] GEODE-10063: Correctly set primary queue connection. (#7382) * When adding QueueConnection to connectionList, also checks if the connection has been destroyed by another thread to prevent a bad connection is being added to the list. * Schedule RedundancySatisfierTask after remove connection so that bad connection can be detected. * During recoveryPrimary in RedundancySatisfierTask also check if primary connection is destroyed. If so, connection from backups will be promoted to primary. > A closed/destroyed connection can be set as a primary queueConnection in > QueueManager > - > > Key: GEODE-10063 > URL: https://issues.apache.org/jira/browse/GEODE-10063 > Project: Geode > Issue Type: Bug > Components: client queues, security >Affects Versions: 1.15.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available > > In certain race cases, a destroyed connection is set to be the primary queue > connection connected to servers. If re-auth is enabled, and server pauses the > primary queue waiting for the re-auth token, there will be no client to > server connection available to send the valid re-auth token for server to > unpause the queue. And the said client can not receive any events afterwards. > The situation should be detected during RedundancySatisfierTask, but it could > not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7232) CI: org.apache.geode.benchmark.tests.PartitionedPutAllLongBenchmark > run() FAILED
[ https://issues.apache.org/jira/browse/GEODE-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498253#comment-17498253 ] Geode Integration commented on GEODE-7232: -- Seen on support/1.14 in [benchmark-base #30|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/benchmark-base/builds/30]. > CI: org.apache.geode.benchmark.tests.PartitionedPutAllLongBenchmark > run() > FAILED > -- > > Key: GEODE-7232 > URL: https://issues.apache.org/jira/browse/GEODE-7232 > Project: Geode > Issue Type: Bug > Components: benchmarks, ci >Reporter: Jinmei Liao >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/596 > org.apache.geode.benchmark.tests.PartitionedPutAllLongBenchmark > run() FAILED > java.util.concurrent.CompletionException: java.lang.RuntimeException: > java.rmi.UnmarshalException: Error unmarshaling return header; nested > exception is: > java.io.EOFException > Caused by: > java.lang.RuntimeException: java.rmi.UnmarshalException: Error > unmarshaling return header; nested exception is: > java.io.EOFException > Caused by: > java.rmi.UnmarshalException: Error unmarshaling return header; > nested exception is: > java.io.EOFException > Caused by: > java.io.EOFException -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10085) Multiple Locators Not Working in New .NET Test Framework
Michael Martell created GEODE-10085: --- Summary: Multiple Locators Not Working in New .NET Test Framework Key: GEODE-10085 URL: https://issues.apache.org/jira/browse/GEODE-10085 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Martell If a cluster with more than one locator is used in the new .NET test framework, the test will fail. The failure results from trying to start JmxManager when it is already running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10085) Multiple Locators Not Working in New .NET Test Framework
[ https://issues.apache.org/jira/browse/GEODE-10085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10085: -- Labels: needsTriage (was: ) > Multiple Locators Not Working in New .NET Test Framework > > > Key: GEODE-10085 > URL: https://issues.apache.org/jira/browse/GEODE-10085 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: needsTriage > > If a cluster with more than one locator is used in the new .NET test > framework, the test will fail. The failure results from trying to start > JmxManager when it is already running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10085) Multiple Locators Not Working in New .NET Test Framework
[ https://issues.apache.org/jira/browse/GEODE-10085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498297#comment-17498297 ] ASF GitHub Bot commented on GEODE-10085: mmartell opened a new pull request #936: URL: https://github.com/apache/geode-native/pull/936 This adds support for multiple locators in the new .NET test framework. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Multiple Locators Not Working in New .NET Test Framework > > > Key: GEODE-10085 > URL: https://issues.apache.org/jira/browse/GEODE-10085 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: needsTriage > > If a cluster with more than one locator is used in the new .NET test > framework, the test will fail. The failure results from trying to start > JmxManager when it is already running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10085) Multiple Locators Not Working in New .NET Test Framework
[ https://issues.apache.org/jira/browse/GEODE-10085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10085: --- Labels: needsTriage pull-request-available (was: needsTriage) > Multiple Locators Not Working in New .NET Test Framework > > > Key: GEODE-10085 > URL: https://issues.apache.org/jira/browse/GEODE-10085 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: needsTriage, pull-request-available > > If a cluster with more than one locator is used in the new .NET test > framework, the test will fail. The failure results from trying to start > JmxManager when it is already running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10083) Fix RedisProxy to correctly process MOVED responses
[ https://issues.apache.org/jira/browse/GEODE-10083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10083: --- Labels: needsTriage pull-request-available (was: needsTriage) > Fix RedisProxy to correctly process MOVED responses > --- > > Key: GEODE-10083 > URL: https://issues.apache.org/jira/browse/GEODE-10083 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: needsTriage, pull-request-available > > The RedisProxy test helper rewrites various redis responses to allow for > address translation when using a docker-based redis cluster. Due to the way > the internal netty processing pipeline was constructed, a received MOVED > response could have disrupted subsequent requests flowing through the proxy. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10083) Fix RedisProxy to correctly process MOVED responses
[ https://issues.apache.org/jira/browse/GEODE-10083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498320#comment-17498320 ] ASF subversion and git services commented on GEODE-10083: - Commit b7297023c309210e70f3792980e75d10c54e7421 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b729702 ] GEODE-10083: Fix RedisProxy to correctly process MOVED response (#7394) - When a MOVED response is received, the already queued processor needs to be discarded otherwise subsequent requests may possibly be corrupted. > Fix RedisProxy to correctly process MOVED responses > --- > > Key: GEODE-10083 > URL: https://issues.apache.org/jira/browse/GEODE-10083 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: needsTriage, pull-request-available > > The RedisProxy test helper rewrites various redis responses to allow for > address translation when using a docker-based redis cluster. Due to the way > the internal netty processing pipeline was constructed, a received MOVED > response could have disrupted subsequent requests flowing through the proxy. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner resolved GEODE-9998. - Resolution: Fixed Fixed the issues this caused in geode benchmarks and in gemfire-test. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
