[jira] [Commented] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036096#comment-17036096
]
ASF subversion and git services commented on GEODE-7789:
Commit 71e156a55228d89efafd048e1533debba606c064 in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=71e156a ]
GEODE-7789: Cache DurableClienAttributes (#4687)
Keep the last known 'DurableClienAttributes' cached within the
'InternalDistributedMember' class to avoid the overhead of creating a
new instance every time.
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos resolved GEODE-7789.
---
Fix Version/s: 1.13.0
Resolution: Fixed
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036143#comment-17036143
]
ASF subversion and git services commented on GEODE-7756:
Commit 5dd7a8420bbe43657abc82e5b8d073eb01b51d8d in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dd7a84 ]
GEODE-7756: Do not use authorization cache for CQs (#4677)
CQs are executed on individual entries whenever an event is triggered
for them and the execution context is always cleared before the actual
evaluation, thus using an internal cache to keep already authorized
methods is useless (will always be a cache miss and the computation
required just adds overhead).
- Fixed the CQ creation to always set the 'cqQueryContext' flag.
- Modified the query engine to avoid using the internal cache for
already authorized methods when the context belongs to a CQ.
- Avoid the creation and concatenation of unnecessary Strings, using
the Method class directly instead.
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos resolved GEODE-7756.
---
Fix Version/s: 1.13.0
Resolution: Fixed
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7756:
--
Affects Version/s: 1.12.0
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7756:
--
Affects Version/s: (was: 1.12.0)
1.11.0
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7789:
--
Affects Version/s: 1.11.0
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7630) Break dependency on OSProcess in membership
[ https://issues.apache.org/jira/browse/GEODE-7630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036366#comment-17036366 ] ASF subversion and git services commented on GEODE-7630: Commit 6e6bd45678c51f309fbac6cd4656e036647c67fa in geode's branch refs/heads/feature/GEODE-7630b from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6e6bd45 ] GEODE-7630 - restore DistributionConfig.GEMFIRE_PREFIX > Break dependency on OSProcess in membership > --- > > Key: GEODE-7630 > URL: https://issues.apache.org/jira/browse/GEODE-7630 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Priority: Major > Fix For: 1.12.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036383#comment-17036383
]
ASF subversion and git services commented on GEODE-7789:
Commit 46a9d9468437dba4ee227e74be767f0224d050e5 in geode's branch
refs/heads/release/1.12.0 from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=46a9d94 ]
GEODE-7789: Cache DurableClienAttributes (#4687)
Keep the last known 'DurableClienAttributes' cached within the
'InternalDistributedMember' class to avoid the overhead of creating a
new instance every time.
(cherry picked from commit 71e156a55228d89efafd048e1533debba606c064)
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7789:
--
Fix Version/s: 1.12.0
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0, 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7789:
--
Affects Version/s: (was: 1.12.0)
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0, 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7789:
--
Fix Version/s: (was: 1.13.0)
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036387#comment-17036387
]
ASF subversion and git services commented on GEODE-7756:
Commit 9ca80438c392db7ab2cd8523662bcb4c76c0ad29 in geode's branch
refs/heads/release/1.12.0 from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9ca8043 ]
GEODE-7756: Do not use authorization cache for CQs (#4677)
CQs are executed on individual entries whenever an event is triggered
for them and the execution context is always cleared before the actual
evaluation, thus using an internal cache to keep already authorized
methods is useless (will always be a cache miss and the computation
required just adds overhead).
- Fixed the CQ creation to always set the 'cqQueryContext' flag.
- Modified the query engine to avoid using the internal cache for
already authorized methods when the context belongs to a CQ.
- Avoid the creation and concatenation of unnecessary Strings, using
the Method class directly instead.
(cherry picked from commit 5dd7a8420bbe43657abc82e5b8d073eb01b51d8d)
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7798) CI: org.apache.geode.redis.PubSubTest failed intermittently on Windows
Jinmei Liao created GEODE-7798: -- Summary: CI: org.apache.geode.redis.PubSubTest failed intermittently on Windows Key: GEODE-7798 URL: https://issues.apache.org/jira/browse/GEODE-7798 Project: Geode Issue Type: Bug Reporter: Jinmei Liao https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1240 https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1242 org.apache.geode.redis.PubSubTest > testTwoSubscribersOneChannel FAILED org.junit.ComparisonFailure: expected:<[2]L> but was:<[1]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testTwoSubscribersOneChannel(PubSubTest.java:163) org.apache.geode.redis.PubSubTest > testOneSubscriberSubscribingToTwoChannels FAILED org.junit.ComparisonFailure: expected:<[1]L> but was:<[2]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testOneSubscriberSubscribingToTwoChannels(PubSubTest.java:124) org.apache.geode.redis.PubSubTest > testDeadSubscriber FAILED org.junit.ComparisonFailure: expected:<[0]L> but was:<[2]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testDeadSubscriber(PubSubTest.java:250) org.apache.geode.redis.PubSubTest > testOneSubscriberOneChannelTwoTimes FAILED org.junit.ComparisonFailure: expected:<[1]L> but was:<[3]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testOneSubscriberOneChannelTwoTimes(PubSubTest.java:210) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-7789:
Fix Version/s: 1.13.0
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0, 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7798) CI: org.apache.geode.redis.PubSubTest failed intermittently on Windows
[ https://issues.apache.org/jira/browse/GEODE-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-7798: - Assignee: Jens Deppe > CI: org.apache.geode.redis.PubSubTest failed intermittently on Windows > > > Key: GEODE-7798 > URL: https://issues.apache.org/jira/browse/GEODE-7798 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Jens Deppe >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1240 > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1242 > org.apache.geode.redis.PubSubTest > testTwoSubscribersOneChannel FAILED > org.junit.ComparisonFailure: expected:<[2]L> but was:<[1]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.redis.PubSubTest.testTwoSubscribersOneChannel(PubSubTest.java:163) > org.apache.geode.redis.PubSubTest > testOneSubscriberSubscribingToTwoChannels > FAILED > org.junit.ComparisonFailure: expected:<[1]L> but was:<[2]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.redis.PubSubTest.testOneSubscriberSubscribingToTwoChannels(PubSubTest.java:124) > org.apache.geode.redis.PubSubTest > testDeadSubscriber FAILED > org.junit.ComparisonFailure: expected:<[0]L> but was:<[2]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.redis.PubSubTest.testDeadSubscriber(PubSubTest.java:250) > org.apache.geode.redis.PubSubTest > testOneSubscriberOneChannelTwoTimes FAILED > org.junit.ComparisonFailure: expected:<[1]L> but was:<[3]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.redis.PubSubTest.testOneSubscriberOneChannelTwoTimes(PubSubTest.java:210) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-7756:
Fix Version/s: 1.12.0
Affects Version/s: (was: 1.12.0)
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0, 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7717) ClusterManagementListResult should contain a list ConfigurationInfo (config per id)
[ https://issues.apache.org/jira/browse/GEODE-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-7717: Fix Version/s: 1.13.0 > ClusterManagementListResult should contain a list ConfigurationInfo (config > per id) > --- > > Key: GEODE-7717 > URL: https://issues.apache.org/jira/browse/GEODE-7717 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Priority: Major > Labels: tech-debt, technical_debt > Fix For: 1.12.0, 1.13.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Currently ClusterManagementListResult contains a list > ConfigurationResult(config per group), those configs are not grouped by id, > so a region that belongs to multiple groups might be dispersed in the list. > Since ClsuterManagementGetResult contains a single ConfigurationInfo, it > seems to make sense to have the ListResult contains a list of > ConfigurationInfo. > Also, after the ClusterManagementListResult contains the list grouped by id, > it would be good for us to display "links" in the ConfigurationInfo level > instead of ConfigurationResult level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7760) NPE in reconnecting Locator
[
https://issues.apache.org/jira/browse/GEODE-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-7760:
Fix Version/s: 1.13.0
> NPE in reconnecting Locator
> ---
>
> Key: GEODE-7760
> URL: https://issues.apache.org/jira/browse/GEODE-7760
> Project: Geode
> Issue Type: Bug
> Components: management, membership
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Fix For: 1.12.0, 1.13.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> A v1.9 locator was forced out of the cluster and then threw an NPE when it
> was reconnecting. Apparently the new DistributedSystem was also kicked out
> of the cluster during this time.
> {noformat}
> [fatal 2019/12/18 02:14:55.647 UTC
> tid=0xb1a5] Uncaught exception in thread Thread[Location services restart
> thread,5,main]
> java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:690)
> at
> org.apache.geode.distributed.internal.InternalLocator.restartWithDS(InternalLocator.java:1124)
> at
> org.apache.geode.distributed.internal.InternalLocator.attemptReconnect(InternalLocator.java:1062)
> at
> org.apache.geode.distributed.internal.InternalLocator.lambda$launchRestartThread$1(InternalLocator.java:983)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> This wasn't from a CI run and there are no other artifacts available.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7799) Rebalance state needs to be distributed to other locators
Darrel Schneider created GEODE-7799:
---
Summary: Rebalance state needs to be distributed to other locators
Key: GEODE-7799
URL: https://issues.apache.org/jira/browse/GEODE-7799
Project: Geode
Issue Type: Improvement
Components: management
Reporter: Darrel Schneider
Why
Within certain environments, users could be connected to a singular locator
point of contact which is then unintelligently routed to one of the locators.
If I kick off an operation from one Locator, but then check on it using another
locator I will get a missing operation message.
Acceptance Criteria
Operation in one read by another
Scenario:
Given a cluster is up with 2 locators (locater1,locater2) as well as 2 servers
And a user submits a POST operation to
locator1:7070/management/experimental/operations/rebalances
And that rebalance is in progress
When a user submits a get operation to
locator2:7070/management/experimental/operations/reblances/{id}
Then they would receive the status of the operation started on locator1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7799) Rebalance state needs to be distributed to other locators
[
https://issues.apache.org/jira/browse/GEODE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider reassigned GEODE-7799:
---
Assignee: Darrel Schneider
> Rebalance state needs to be distributed to other locators
> -
>
> Key: GEODE-7799
> URL: https://issues.apache.org/jira/browse/GEODE-7799
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>
> Why
> Within certain environments, users could be connected to a singular locator
> point of contact which is then unintelligently routed to one of the locators.
> If I kick off an operation from one Locator, but then check on it using
> another locator I will get a missing operation message.
> Acceptance Criteria
> Operation in one read by another
> Scenario:
> Given a cluster is up with 2 locators (locater1,locater2) as well as 2 servers
> And a user submits a POST operation to
> locator1:7070/management/experimental/operations/rebalances
> And that rebalance is in progress
> When a user submits a get operation to
> locator2:7070/management/experimental/operations/reblances/{id}
> Then they would receive the status of the operation started on locator1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7791) MergeLogsDistributedTest fails with extra log files
[ https://issues.apache.org/jira/browse/GEODE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036544#comment-17036544 ] ASF subversion and git services commented on GEODE-7791: Commit 5d2b1d1003982de248953230a8429f7ec19de692 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5d2b1d1 ] GEODE-7791: fix MergeLogsDistributedTest (#4697) > MergeLogsDistributedTest fails with extra log files > --- > > Key: GEODE-7791 > URL: https://issues.apache.org/jira/browse/GEODE-7791 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Priority: Major > Labels: Windows > Time Spent: 0.5h > Remaining Estimate: 0h > > Note: these failures are on Windows with Open JDK 8 and 11 > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK8/builds/1288] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/1297] > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest > > testExportInNewProcess FAILED > java.lang.AssertionError: > Expected size:<4> but was:<5> in: > > <[C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\locator\locator56675views.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator-0.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator56791views.log, > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm1\server-1.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm2\server-2.log]> > at > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest.testExportInNewProcess(MergeLogsDistributedTest.java:97) > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest > > testExportInProcess FAILED > java.lang.AssertionError: > Expected size:<4> but was:<5> in: > > <[C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\locator\locator56675views.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator-0.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator56821views.log, > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm1\server-1.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm2\server-2.log]> > at > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest.testExportInProcess(MergeLogsDistributedTest.java:85) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7751) Tomcat9CachingClientServerTest.containersShouldExpireInSetTimeframe failed.
[ https://issues.apache.org/jira/browse/GEODE-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-7751: -- Assignee: (was: Mark Hanson) > Tomcat9CachingClientServerTest.containersShouldExpireInSetTimeframe failed. > --- > > Key: GEODE-7751 > URL: https://issues.apache.org/jira/browse/GEODE-7751 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Priority: Major > Labels: flaky > > Test run > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2937 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7135) Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
[
https://issues.apache.org/jira/browse/GEODE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7135:
--
Assignee: (was: Mark Hanson)
> Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
>
>
> Key: GEODE-7135
> URL: https://issues.apache.org/jira/browse/GEODE-7135
> Project: Geode
> Issue Type: Bug
>Reporter: Murtuza Boxwala
>Priority: Major
> Labels: flaky
>
> {code:java}
> org.apache.geode.modules.session.Tomcat8SessionsDUnitTest >
> testSessionExpiration1 FAILED
> java.net.ConnectException: Connection refused (Connection refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7098) Tomcat8SessionsClientServerDUnitTest fails with ConnectException
[ https://issues.apache.org/jira/browse/GEODE-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-7098: -- Assignee: (was: Mark Hanson) > Tomcat8SessionsClientServerDUnitTest fails with ConnectException > > > Key: GEODE-7098 > URL: https://issues.apache.org/jira/browse/GEODE-7098 > Project: Geode > Issue Type: Bug >Reporter: Benjamin P Ross >Priority: Major > Labels: flaky > > We've seen Tomcat8SessionsClientServerDUnitTest.testExtraSessionsNotCreated > fail with > a ConnectException > org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest > > testExtraSessionsNotCreated FAILED > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > This could be an environmental error, but if a pattern develops it could be > due to a flaky test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036561#comment-17036561
]
Mark Hanson commented on GEODE-7664:
New failures.
{noformat}
deleteRegionOnSpecificGroup
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/335
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/238
{noformat}
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1858[error 2020/02/10 07:47:54.929 GMT
tid=358]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]
org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]
at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7322)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8282)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
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.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
at java.lang.Thread.run(Thread.java:748)
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:393)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:185)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:69)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.ru
[jira] [Updated] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson updated GEODE-7664:
---
Description:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
{code:java}
org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
strings were written to the log during this run.Fix the strings or use
IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1874
[error 2020/01/09 18:52:37.224 GMT tid=353]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled] at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256) at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
was:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454
{code:java}
org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
strings were written to the log during this run.Fix the strings or use
IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1874
[error 2020/01/09 18:52:37.224 GMT tid=353]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled] at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256) at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessa
[jira] [Commented] (GEODE-7684) Implement the Bucket region clear messages and handling
[ https://issues.apache.org/jira/browse/GEODE-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036563#comment-17036563 ] ASF subversion and git services commented on GEODE-7684: Commit dbe59ece4749d07cdb65d7878a1472703e81c68c in geode's branch refs/heads/feature/GEODE-7665 from BenjaminPerryRoss [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dbe59ec ] GEODE-7684: Create messaging class for PR Clear (#4689) * Added new message class and test Co-authored-by: Benjamin Ross Co-authored-by: Donal Evans > Implement the Bucket region clear messages and handling > --- > > Key: GEODE-7684 > URL: https://issues.apache.org/jira/browse/GEODE-7684 > Project: Geode > Issue Type: New Feature > Components: regions >Reporter: Nabarun Nag >Priority: Major > Labels: GeodeCommons > Time Spent: 4h 10m > Remaining Estimate: 0h > > Implement the bucket region clear message, and the handling of the message. > Upon receiving this message the bucket region must be cleared. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson updated GEODE-7664:
---
Description:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
{code:java}
org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
strings were written to the log during this run.Fix the strings or use
IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1874 [error 2020/01/09 18:52:37.224 GMT
tid=353]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256) at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
was:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
{code:java}
org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
strings were written to the log during this run.Fix the strings or use
IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1874
[error 2020/01/09 18:52:37.224 GMT tid=353]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled] at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256) at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessa
[jira] [Updated] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson updated GEODE-7664:
---
Description:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
{code:java}
org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
strings were written to the log during this run.Fix the strings or use
IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1874 [error 2020/01/09 18:52:37.224 GMT
tid=353]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]
org.apache.geode.cache.RegionDestroyedException:org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]
at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
was:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
{code:java}
org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
strings were written to the log during this run.Fix the strings or use
IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1874 [error 2020/01/09 18:52:37.224 GMT
tid=353]
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]org.apache.geode.cache.RegionDestroyedException:
org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled]at
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
at
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
at
org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256) at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
at
org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
at
org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
at
org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(
[jira] [Commented] (GEODE-7210) RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU fails intermittently with CacheClientProxy was not fulfilled
[
https://issues.apache.org/jira/browse/GEODE-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036577#comment-17036577
]
ASF subversion and git services commented on GEODE-7210:
Commit 8c40d5e66d1d8743f4b547de8cf429de8a187801 in geode's branch
refs/heads/develop from Ivan Godwin
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8c40d5e ]
GEODE-7210: Fix RedundancyLevelPart1DUnitTest
- Add awaits to assertions dependent on asynchronous calls
Co-authored-by: Mark Hanson
Co-authored-by: Kirk Lund
> RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU
> fails intermittently with CacheClientProxy was not fulfilled
> -
>
> Key: GEODE-7210
> URL: https://issues.apache.org/jira/browse/GEODE-7210
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Darrel Schneider
>Assignee: Ivan Godwin
>Priority: Major
> Labels: flaky
> Fix For: 1.12.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> It failed in this run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1098
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest$$Lambda$180/1742098249.run
> in VM 2 running on Host 672aa6424308 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU(RedundancyLevelPart1DUnitTest.java:237)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelTestBase that
> uses org.apache.geode.internal.cache.tier.sockets.CacheClientProxy was not
> fulfilled within 300 seconds.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7664:
--
Assignee: Mark Hanson
> CI Failure: ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup
> -
>
> Key: GEODE-7664
> URL: https://issues.apache.org/jira/browse/GEODE-7664
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Mark Hanson
>Priority: Major
> Labels: Flaky
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
>
> {code:java}
> org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
> strings were written to the log during this run.Fix the strings or use
> IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1874 [error 2020/01/09 18:52:37.224 GMT
> tid=353]
> org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> org.apache.geode.cache.RegionDestroyedException:org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
> at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
>
> at
> org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
>
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
> at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-4263) CI Failure: ResourceManagerWithQueryMonitorDUnitTest. testRM* are failing
[
https://issues.apache.org/jira/browse/GEODE-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036579#comment-17036579
]
ASF subversion and git services commented on GEODE-4263:
Commit 5c6529a76dfad174be6a29438bf196013952b05b in geode's branch
refs/heads/develop from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5c6529a ]
Geode 4263 (#4691)
GEODE-4263: Cleaned up and phase 1 ready.
- Initial refactor to cleanup
- removing a bunch of thread sleeps
- adding awaits
- One key fix was to increase the latch wait time.
- Added a latch to fix an issue where we might not be waiting long enough
- Requested changes made.
> CI Failure: ResourceManagerWithQueryMonitorDUnitTest. testRM* are failing
> -
>
> Key: GEODE-4263
> URL: https://issues.apache.org/jira/browse/GEODE-4263
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Nabarun Nag
>Assignee: Mark Hanson
>Priority: Major
> Labels: flaky
>
> {noformat}
> java.lang.AssertionError: queryExecution.getResult() threw Exception
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doTestCriticalHeapAndQueryTimeout(ResourceManagerWithQueryMonitorDUnitTest.java:738)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doCriticalMemoryHitTest(ResourceManagerWithQueryMonitorDUnitTest.java:321)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.testRMAndTimeoutSet(ResourceManagerWithQueryMonitorDUnitTest.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInv
[jira] [Commented] (GEODE-7778) Add PUBLISH, SUBSCRIBE and UNSUBSCRIBE Redis commands
[ https://issues.apache.org/jira/browse/GEODE-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036581#comment-17036581 ] ASF subversion and git services commented on GEODE-7778: Commit d3ecaaafd7b08c667c1a7a4eb36060ea560b0347 in geode's branch refs/heads/mass-test-run from Sarah Abbey [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d3ecaaa ] GEODE-7778: Add PUBLISH, SUBSCRIBE and UNSUBSCRIBE Redis commands (#4682) Redis PUBLISH/SUBSCRIBE is described here: https://redis.io/topics/pubsub This implementation introduces 3 new command classes to support this: `SubscribeExecutor`, `PublishExecutor` and `UnsubscribeExecutor`. At a high level, the flow is as follows: - A Redis client issues a SUBSCRIBE command. The server maintains a list of subscribed clients and associate channel(s) in the `Subscribers` class. A subscribed `Client` uses Netty's notion of a `uniqueID` to identify itself uniquely. - When a client PUBLISHes a message on a channel, the publish 'event' uses an `onMembers` function call to distribute the channel/message to all members. Each member then publishes the message to any `Client`s registered on the channel. Points to note: Redis pub/sub is not HA. i.e. A subscriber only receives those messages published after it has successfully subscribed. If the client is disconnected and reconnects, it will not receive messages published during the disconnect window. When clients subscribe, an open connection is established to the server and the client blocks waiting for messages. This implementation does not require messages to be published on the same server to which the clients, executing subscribe, are connected since the published message is distributed to all servers. Co-authored-by: Jens Deppe Co-authored-by: Prasath Durairaj Co-authored-by: Murtuza Boxwala Co-authored-by: Sarah Abbey Co-authored-by: John Hutchison Co-authored-by: Ray Ingles > Add PUBLISH, SUBSCRIBE and UNSUBSCRIBE Redis commands > - > > Key: GEODE-7778 > URL: https://issues.apache.org/jira/browse/GEODE-7778 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Time Spent: 10h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7210) RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU fails intermittently with CacheClientProxy was not fulfilled
[
https://issues.apache.org/jira/browse/GEODE-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036586#comment-17036586
]
ASF subversion and git services commented on GEODE-7210:
Commit 8c40d5e66d1d8743f4b547de8cf429de8a187801 in geode's branch
refs/heads/mass-test-run from Ivan Godwin
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8c40d5e ]
GEODE-7210: Fix RedundancyLevelPart1DUnitTest
- Add awaits to assertions dependent on asynchronous calls
Co-authored-by: Mark Hanson
Co-authored-by: Kirk Lund
> RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU
> fails intermittently with CacheClientProxy was not fulfilled
> -
>
> Key: GEODE-7210
> URL: https://issues.apache.org/jira/browse/GEODE-7210
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Darrel Schneider
>Assignee: Ivan Godwin
>Priority: Major
> Labels: flaky
> Fix For: 1.12.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> It failed in this run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1098
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest$$Lambda$180/1742098249.run
> in VM 2 running on Host 672aa6424308 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU(RedundancyLevelPart1DUnitTest.java:237)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelTestBase that
> uses org.apache.geode.internal.cache.tier.sockets.CacheClientProxy was not
> fulfilled within 300 seconds.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-4263) CI Failure: ResourceManagerWithQueryMonitorDUnitTest. testRM* are failing
[
https://issues.apache.org/jira/browse/GEODE-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036587#comment-17036587
]
ASF subversion and git services commented on GEODE-4263:
Commit 5c6529a76dfad174be6a29438bf196013952b05b in geode's branch
refs/heads/mass-test-run from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5c6529a ]
Geode 4263 (#4691)
GEODE-4263: Cleaned up and phase 1 ready.
- Initial refactor to cleanup
- removing a bunch of thread sleeps
- adding awaits
- One key fix was to increase the latch wait time.
- Added a latch to fix an issue where we might not be waiting long enough
- Requested changes made.
> CI Failure: ResourceManagerWithQueryMonitorDUnitTest. testRM* are failing
> -
>
> Key: GEODE-4263
> URL: https://issues.apache.org/jira/browse/GEODE-4263
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Nabarun Nag
>Assignee: Mark Hanson
>Priority: Major
> Labels: flaky
>
> {noformat}
> java.lang.AssertionError: queryExecution.getResult() threw Exception
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doTestCriticalHeapAndQueryTimeout(ResourceManagerWithQueryMonitorDUnitTest.java:738)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doCriticalMemoryHitTest(ResourceManagerWithQueryMonitorDUnitTest.java:321)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.testRMAndTimeoutSet(ResourceManagerWithQueryMonitorDUnitTest.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$Dispatch
[jira] [Commented] (GEODE-7792) configure logging for geode-membership integration tests
[ https://issues.apache.org/jira/browse/GEODE-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036580#comment-17036580 ] ASF subversion and git services commented on GEODE-7792: Commit c5a3b16593445367f593f5dfbb61c50f81dc2627 in geode's branch refs/heads/mass-test-run from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c5a3b16 ] GEODE-7792: configure logging for geode-membership integration tests (#4688) > configure logging for geode-membership integration tests > > > Key: GEODE-7792 > URL: https://issues.apache.org/jira/browse/GEODE-7792 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Bruce J Schuchardt >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Integration tests for geode-management do not have a log4j configuration. > The subproject cannot depend on geode-log4j because that pulls in geode-core > with its Alert appender and other things. > Add a log4j configuration for tests in geode-management so we can get proper > log output from tests to diagnose failures. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7796) CI: org.apache.geode.distributed.LocatorDUnitTest testCrashLocatorMultipleTimes hung
[ https://issues.apache.org/jira/browse/GEODE-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036582#comment-17036582 ] ASF subversion and git services commented on GEODE-7796: Commit 185442318e6d32c0bae63240e107834b1edc38f0 in geode's branch refs/heads/mass-test-run from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1854423 ] GEODE-7796: CI failure in LocatorDUnitTest (#4693) The new test hung during a CI run due to a flaw in Geode. I'm disabling it until the flaw is corrected. > CI: org.apache.geode.distributed.LocatorDUnitTest > testCrashLocatorMultipleTimes hung > > > Key: GEODE-7796 > URL: https://issues.apache.org/jira/browse/GEODE-7796 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jinmei Liao >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1563 > in the artifacts callbacks/dunit-hang.txt, > Started @ 2020-02-11 00:30:32.499 + > 2020-02-11 01:07:59.054 + org.apache.geode.distributed.LocatorDUnitTest > testCrashLocatorMultipleTimes > Ended @ 2020-02-11 02:05:31.891 + > and the stacktraces shows thread gets blocked for a long time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7756) Performance Degradation on Clusters with CQs Introduced in GEODE-6989
[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036584#comment-17036584
]
ASF subversion and git services commented on GEODE-7756:
Commit 5dd7a8420bbe43657abc82e5b8d073eb01b51d8d in geode's branch
refs/heads/mass-test-run from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dd7a84 ]
GEODE-7756: Do not use authorization cache for CQs (#4677)
CQs are executed on individual entries whenever an event is triggered
for them and the execution context is always cleared before the actual
evaluation, thus using an internal cache to keep already authorized
methods is useless (will always be a cache miss and the computation
required just adds overhead).
- Fixed the CQ creation to always set the 'cqQueryContext' flag.
- Modified the query engine to avoid using the internal cache for
already authorized methods when the context belongs to a CQ.
- Avoid the creation and concatenation of unnecessary Strings, using
the Method class directly instead.
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> -
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0, 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7789) Performance Degradation on Servers with Client Subscription Introduced in GEODE-7358
[
https://issues.apache.org/jira/browse/GEODE-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036583#comment-17036583
]
ASF subversion and git services commented on GEODE-7789:
Commit 71e156a55228d89efafd048e1533debba606c064 in geode's branch
refs/heads/mass-test-run from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=71e156a ]
GEODE-7789: Cache DurableClienAttributes (#4687)
Keep the last known 'DurableClienAttributes' cached within the
'InternalDistributedMember' class to avoid the overhead of creating a
new instance every time.
> Performance Degradation on Servers with Client Subscription Introduced in
> GEODE-7358
>
>
> Key: GEODE-7789
> URL: https://issues.apache.org/jira/browse/GEODE-7789
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.11.0
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0, 1.13.0
>
> Attachments: Geode_1.10_Count.png, Geode_Develop_Count.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with pool subscriptions enabled, a performance degradation was
> introduced by GEODE-7358 for regular cache operations.
> The {{InternalDistributedMember.getDurableClientAttributes()}} method is
> indirectly invoked by the methods {{hashCode()}} and {{equals()}} within the
> {{ClientProxyMembershipID}} class, which is stored in several Java Collection
> classes across the product (including different types of {{Map}} instances).
> Prior to GEODE-7358 the {{DurableClientAttributes}} class instance was cached
> within the {{NetMember}} class, but now is created every time the method is
> invoked, resulting in a performance penalty for regular cache operations on
> servers with subscription enabled (not only extra garbage, the constructor
> itself also does some string manipulation).
> Using one of our internal testing scenarios and a java profiler we detected
> that we create ~24 instances of {{DurableClientAttributes}} using Geode 1.10,
> but ~ 404.037.243 instances using the latest {{develop}} branch (screenshots
> attached).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7791) MergeLogsDistributedTest fails with extra log files
[ https://issues.apache.org/jira/browse/GEODE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036585#comment-17036585 ] ASF subversion and git services commented on GEODE-7791: Commit 5d2b1d1003982de248953230a8429f7ec19de692 in geode's branch refs/heads/mass-test-run from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5d2b1d1 ] GEODE-7791: fix MergeLogsDistributedTest (#4697) > MergeLogsDistributedTest fails with extra log files > --- > > Key: GEODE-7791 > URL: https://issues.apache.org/jira/browse/GEODE-7791 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Priority: Major > Labels: Windows > Time Spent: 0.5h > Remaining Estimate: 0h > > Note: these failures are on Windows with Open JDK 8 and 11 > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK8/builds/1288] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/1297] > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest > > testExportInNewProcess FAILED > java.lang.AssertionError: > Expected size:<4> but was:<5> in: > > <[C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\locator\locator56675views.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator-0.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator56791views.log, > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm1\server-1.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm2\server-2.log]> > at > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest.testExportInNewProcess(MergeLogsDistributedTest.java:97) > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest > > testExportInProcess FAILED > java.lang.AssertionError: > Expected size:<4> but was:<5> in: > > <[C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\locator\locator56675views.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator-0.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator56821views.log, > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm1\server-1.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm2\server-2.log]> > at > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest.testExportInProcess(MergeLogsDistributedTest.java:85) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7603) RepeatedRebalanceDUnitTest.testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers
[
https://issues.apache.org/jira/browse/GEODE-7603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Godwin reassigned GEODE-7603:
--
Assignee: Ivan Godwin
> RepeatedRebalanceDUnitTest.testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers
>
>
> Key: GEODE-7603
> URL: https://issues.apache.org/jira/browse/GEODE-7603
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Ivan Godwin
>Priority: Major
> Labels: flaky
>
> RepeatedRebalanceDUnitTest.testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers
> failed twice as a part of the mass test run.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2160]
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2130]
>
> {noformat}
> 10:56:44org.apache.geode.management.internal.cli.commands.RepeatedRebalanceDUnitTest
> > testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers FAILED
> 10:56:44java.lang.AssertionError: [List check last element]
> 10:56:44Expecting:
> 10:56:44 <"0">
> 10:56:44not to be equal to:
> 10:56:44 <"0">
> 10:56:44at
> org.apache.geode.management.internal.cli.commands.RepeatedRebalanceDUnitTest.assertPrimariesTransfered(RepeatedRebalanceDUnitTest.java:204)
> 10:56:44at
> org.apache.geode.management.internal.cli.commands.RepeatedRebalanceDUnitTest.testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers(RepeatedRebalanceDUnitTest.java:124)
> 11:06:20
> 11:06:20352 tests completed, 1 failed, 5 skipped
> 11:06:22
> 11:06:22> Task :geode-gfsh:distributedTest FAILED
> 11:54:40
> 11:54:40> Task :geode-core:distributedTest
> 11:54:40{noformat}
>
> {noformat}
> 22:06:33org.apache.geode.management.internal.cli.commands.RepeatedRebalanceDUnitTest
> > testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers FAILED
> 22:06:33java.lang.AssertionError: [List check last element]
> 22:06:33Expecting:
> 22:06:33 <"0">
> 22:06:33not to be equal to:
> 22:06:33 <"0">
> 22:06:33at
> org.apache.geode.management.internal.cli.commands.RepeatedRebalanceDUnitTest.assertPrimariesTransfered(RepeatedRebalanceDUnitTest.java:204)
> 22:06:33at
> org.apache.geode.management.internal.cli.commands.RepeatedRebalanceDUnitTest.testSecondRebalanceIsNotNecessaryWithAddedAndRestartedMembers(RepeatedRebalanceDUnitTest.java:124)
> 22:16:05 {noformat}
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6284) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test[from_v1X0, with reindex=false]
[
https://issues.apache.org/jira/browse/GEODE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036648#comment-17036648
]
Jinmei Liao commented on GEODE-6284:
Additional failures:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK8/builds/1531
org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> test[from_v1.11.0, with reindex=false, singleHopEnabled=true] FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 9067
java.io.EOFException: Locator at /172.17.0.25:27318 did not respond. This
is normal if the locator was shutdown. If it wasn't check its log for
exceptions.
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:232)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:202)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:192)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:274)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.access$200(AutoConnectionSourceImpl.java:63)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl$UpdateLocatorListTask.run2(AutoConnectionSourceImpl.java:477)
at
org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1305)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:276)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:267)
at
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2616)
at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:227)
... 12 more
> CI Failure:
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test[from_v1X0,
> with reindex=false]
>
>
> Key: GEODE-6284
> URL: https://issues.apache.org/jira/browse/GEODE-6284
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0
>Reporter: Ryan McMahon
>Priority: Major
>
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host
> 34bae3263b09 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:537)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:352)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:57)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:496)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:484)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRu
