[jira] [Updated] (GEODE-1989) CI failure: SharedConfigurationUsingDirDUnitTest updateClusterConfigDirWithTwoLocatorsAndRollingServerRestart

[ https://issues.apache.org/jira/browse/GEODE-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-1989: - Labels: ci flaky (was: ci) > CI failure: SharedConfigurationUsingDirDUnitTest > updateClusterConfigDirWi

[jira] [Assigned] (GEODE-1989) CI failure: SharedConfigurationUsingDirDUnitTest updateClusterConfigDirWithTwoLocatorsAndRollingServerRestart

[ https://issues.apache.org/jira/browse/GEODE-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-1989: Assignee: Kirk Lund > CI failure: SharedConfigurationUsingDirDUnitTest > updateClusterConfigDirWit

[jira] [Created] (GEODE-2132) Allow PostProcessor to be specified in Region Attributes

Kirk Lund created GEODE-2132: Summary: Allow PostProcessor to be specified in Region Attributes Key: GEODE-2132 URL: https://issues.apache.org/jira/browse/GEODE-2132 Project: Geode Issue Type: Wi

[jira] [Created] (GEODE-2131) PostProcessors should have access to roles

Kevin Duling created GEODE-2131: --- Summary: PostProcessors should have access to roles Key: GEODE-2131 URL: https://issues.apache.org/jira/browse/GEODE-2131 Project: Geode Issue Type: Improvemen

[jira] [Created] (GEODE-2130) Serialized data generated by DataSerializer.writeObject depends on the type of OutputStream

Dan Smith created GEODE-2130: Summary: Serialized data generated by DataSerializer.writeObject depends on the type of OutputStream Key: GEODE-2130 URL: https://issues.apache.org/jira/browse/GEODE-2130 Pro

[jira] [Updated] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2092: - Description: These three classes are currently in geode-core product package which implies they are fully

[jira] [Updated] (GEODE-2092) Security examples should not be in product package

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2092: - Summary: Security examples should not be in product package (was: Security examples should not be in the

[jira] [Updated] (GEODE-2129) Need to generate pdx type id random(or avoid sequential)

[ https://issues.apache.org/jira/browse/GEODE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra updated GEODE-2129: --- Summary: Need to generate pdx type id random(or avoid sequential) (was: Need to pdx type id r

[jira] [Commented] (GEODE-2120) MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI

[ https://issues.apache.org/jira/browse/GEODE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675283#comment-15675283 ] ASF subversion and git services commented on GEODE-2120: Commit c5

[jira] [Assigned] (GEODE-2129) Need to generate pdx type id random(or avoid sequential)

[ https://issues.apache.org/jira/browse/GEODE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra reassigned GEODE-2129: -- Assignee: Hitesh Khamesra > Need to generate pdx type id random(or avoid sequential) >

[jira] [Resolved] (GEODE-2120) MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI

[ https://issues.apache.org/jira/browse/GEODE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2120. -- Resolution: Fixed > MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI > -

[jira] [Created] (GEODE-2129) Need to pdx type id random

Hitesh Khamesra created GEODE-2129: -- Summary: Need to pdx type id random Key: GEODE-2129 URL: https://issues.apache.org/jira/browse/GEODE-2129 Project: Geode Issue Type: Bug Compon

[jira] [Updated] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2092: - Description: These three classes are currently in geode-core product package which implies they are fully

[jira] [Updated] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2092: - Description: These three classes are currently in geode-core product package which implies they are fully

[jira] [Commented] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675267#comment-15675267 ] Kirk Lund commented on GEODE-2092: -- In the future we will need to move the security examp

[jira] [Updated] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2092: - Description: These three classes are currently in geode-core product package which implies they are fully

[jira] [Commented] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675256#comment-15675256 ] ASF GitHub Bot commented on GEODE-2092: --- Github user kjduling commented on the issue

[jira] [Resolved] (GEODE-2096) CI Failure: PersistentColocatedPartitionedRegionDUnitTest.testMultipleColocatedChildPRsMissingWithSequencedStart

[ https://issues.apache.org/jira/browse/GEODE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenneth Howe resolved GEODE-2096. - Resolution: Duplicate Same problem on two tests in the DUnit test class > CI Failure: > Persiste

[jira] [Updated] (GEODE-2128) geode-modules-tomcat8 distributedTests use default cacher server port 40404 and may fail with BindExceptions

[ https://issues.apache.org/jira/browse/GEODE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2128: - Labels: CI (was: ) > geode-modules-tomcat8 distributedTests use default cacher server port 40404 > and m

[jira] [Assigned] (GEODE-2128) geode-modules-tomcat8 distributedTests use default cacher server port 40404 and may fail with BindExceptions

[ https://issues.apache.org/jira/browse/GEODE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2128: Assignee: Kirk Lund > geode-modules-tomcat8 distributedTests use default cacher server port 40404

[jira] [Created] (GEODE-2128) geode-modules-tomcat8 distributedTests use default cacher server port 40404 and may fail with BindExceptions

Kirk Lund created GEODE-2128: Summary: geode-modules-tomcat8 distributedTests use default cacher server port 40404 and may fail with BindExceptions Key: GEODE-2128 URL: https://issues.apache.org/jira/browse/GEODE-2128

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster's only server is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster's only server is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster's only server is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster's only server is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster's only server is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Issue Type: Improvement (was: Bug) > GFSH should provide information about Locators that go into reconnec

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Commented] (GEODE-2092) Security examples should not be in the product code

[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675091#comment-15675091 ] ASF GitHub Bot commented on GEODE-2092: --- GitHub user kjduling opened a pull request:

[jira] [Commented] (GEODE-2112) UITests are failing due to insufficient tearDown

[ https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675087#comment-15675087 ] ASF GitHub Bot commented on GEODE-2112: --- Github user jaredjstewart commented on the

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Commented] (GEODE-2112) UITests are failing due to insufficient tearDown

[ https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675079#comment-15675079 ] ASF GitHub Bot commented on GEODE-2112: --- GitHub user jaredjstewart opened a pull req

[jira] [Updated] (GEODE-2125) GFSH should provide information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Summary: GFSH should provide information about Locators that go into reconnect mode (was: GFSH should tel

[jira] [Updated] (GEODE-2125) GFSH should tell user that Locator it's connected to has gone into reconnect

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Updated] (GEODE-2125) GFSH should tell user that Locator it's connected to has gone into reconnect

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Component/s: (was: membership) > GFSH should tell user that Locator it's connected to has gone into re

[jira] [Updated] (GEODE-2125) GFSH should tell user that Locator it's connected to has gone into reconnect

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Reopened] (GEODE-2125) GFSH should tell user that Locator it's connected to has gone into reconnect

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reopened GEODE-2125: -- Assignee: Kirk Lund > GFSH should tell user that Locator it's connected to has gone into reconnect > -

[jira] [Updated] (GEODE-2125) GFSH should tell user that Locator it's connected to has gone into reconnect

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Summary: GFSH should tell user that Locator it's connected to has gone into reconnect (was: Network parti

[jira] [Resolved] (GEODE-2125) Network partition forceDisconnect leaves crippled Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2125. - Resolution: Not A Problem The logs clearly show that auto-reconnect went into effect when

[jira] [Commented] (GEODE-2126) CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines

[ https://issues.apache.org/jira/browse/GEODE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675047#comment-15675047 ] ASF subversion and git services commented on GEODE-2126: Commit ed

[jira] [Assigned] (GEODE-2127) old client support service is not set up to handle arrays

[ https://issues.apache.org/jira/browse/GEODE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-2127: --- Assignee: Bruce Schuchardt > old client support service is not set up to handle array

[jira] [Created] (GEODE-2127) old client support service is not set up to handle arrays

Bruce Schuchardt created GEODE-2127: --- Summary: old client support service is not set up to handle arrays Key: GEODE-2127 URL: https://issues.apache.org/jira/browse/GEODE-2127 Project: Geode

[jira] [Updated] (GEODE-2126) CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines

[ https://issues.apache.org/jira/browse/GEODE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2126: - Labels: CI Flaky (was: ) > CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines > -

[jira] [Assigned] (GEODE-2126) CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines

[ https://issues.apache.org/jira/browse/GEODE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2126: Assignee: Kirk Lund > CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines >

[jira] [Created] (GEODE-2126) CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines

Kirk Lund created GEODE-2126: Summary: CI failure: MiscellaneousCommandsDUnitTest.testShowLogNumLines Key: GEODE-2126 URL: https://issues.apache.org/jira/browse/GEODE-2126 Project: Geode Issue T

[jira] [Updated] (GEODE-2125) Network partition forceDisconnect leaves crippled Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Affects Version/s: 1.0.0-incubating > Network partition forceDisconnect leaves crippled Locator process ru

[jira] [Updated] (GEODE-2125) Network partition forceDisconnect leaves crippled Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Summary: Network partition forceDisconnect leaves crippled Locator process running (was: Network partitio

[jira] [Updated] (GEODE-2125) Network partition forceDisconnect leave Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Attachment: locator_failure-logs.txt Locator log file > Network partition forceDisconnect leave Locator p

[jira] [Updated] (GEODE-2125) Network partition forceDisconnect leave Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Attachment: thread_dump.txt > Network partition forceDisconnect leave Locator process running > --

[jira] [Updated] (GEODE-2125) Network partition forceDisconnect leave Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Description: If the Locator is started from GFSH and the cluster has one server which is killed, network

[jira] [Issue Comment Deleted] (GEODE-2125) Network partition forceDisconnect leave Locator process running

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Comment: was deleted (was: Locator log file) > Network partition forceDisconnect leave Locator process ru

[jira] [Created] (GEODE-2125) Network partition forceDisconnect leave Locator process running

Kirk Lund created GEODE-2125: Summary: Network partition forceDisconnect leave Locator process running Key: GEODE-2125 URL: https://issues.apache.org/jira/browse/GEODE-2125 Project: Geode Issue

[jira] [Updated] (GEODE-2124) Queries that invoke StructSet addAll fail with ClassCastException

[ https://issues.apache.org/jira/browse/GEODE-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby updated GEODE-2124: - Attachment: Position.java Portfolio.java The Portfolio and Position classes used a

[jira] [Created] (GEODE-2124) Queries that invoke StructSet addAll fail with ClassCastException

Barry Oglesby created GEODE-2124: Summary: Queries that invoke StructSet addAll fail with ClassCastException Key: GEODE-2124 URL: https://issues.apache.org/jira/browse/GEODE-2124 Project: Geode

[jira] [Updated] (GEODE-2124) Queries that invoke StructSet addAll fail with ClassCastException

[ https://issues.apache.org/jira/browse/GEODE-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby updated GEODE-2124: - Component/s: querying > Queries that invoke StructSet addAll fail with ClassCastException > --

[jira] [Updated] (GEODE-2122) Receiver still accepts put when it is low on memory

[ https://issues.apache.org/jira/browse/GEODE-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-2122: --- Component/s: wan > Receiver still accepts put when it is low on memory >

[jira] [Created] (GEODE-2123) Replace static members in ParallelgatewaySenderQueues with instance variables

nabarun created GEODE-2123: -- Summary: Replace static members in ParallelgatewaySenderQueues with instance variables Key: GEODE-2123 URL: https://issues.apache.org/jira/browse/GEODE-2123 Project: Geode

[jira] [Created] (GEODE-2122) Receiver still accepts put when it is low on memory

nabarun created GEODE-2122: -- Summary: Receiver still accepts put when it is low on memory Key: GEODE-2122 URL: https://issues.apache.org/jira/browse/GEODE-2122 Project: Geode Issue Type: Bug

[jira] [Created] (GEODE-2121) add DLockTest, MembershipTest, ClientServerTest, ClientSubscriptionTest and RestAPITest categories

Bruce Schuchardt created GEODE-2121: --- Summary: add DLockTest, MembershipTest, ClientServerTest, ClientSubscriptionTest and RestAPITest categories Key: GEODE-2121 URL: https://issues.apache.org/jira/browse/GEODE-

[jira] [Assigned] (GEODE-2121) add DLockTest, MembershipTest, ClientServerTest, ClientSubscriptionTest and RestAPITest categories

[ https://issues.apache.org/jira/browse/GEODE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-2121: --- Assignee: Bruce Schuchardt > add DLockTest, MembershipTest, ClientServerTest, ClientS

[jira] [Resolved] (GEODE-2100) Add new version of query client server messages

[ https://issues.apache.org/jira/browse/GEODE-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-2100. Resolution: Fixed > Add new version of query client server messages > --

[jira] [Resolved] (GEODE-2111) Add gfsh recommendation to put all --J options at end of command line

[ https://issues.apache.org/jira/browse/GEODE-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-2111. -- Resolution: Fixed Fix Version/s: 1.1.0-incubating The original bug GEODE-2104 has been fi

[jira] [Commented] (GEODE-2120) MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI

[ https://issues.apache.org/jira/browse/GEODE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15674396#comment-15674396 ] xiaojian zhou commented on GEODE-2120: -- The root cause is: concourse is slower than e

[jira] [Assigned] (GEODE-2120) MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI

[ https://issues.apache.org/jira/browse/GEODE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2120: Assignee: xiaojian zhou > MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI > --

[jira] [Created] (GEODE-2120) MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI

xiaojian zhou created GEODE-2120: Summary: MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI Key: GEODE-2120 URL: https://issues.apache.org/jira/browse/GEODE-2120 Project: Geode I

[jira] [Updated] (GEODE-2120) MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI

[ https://issues.apache.org/jira/browse/GEODE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2120: - Labels: CI (was: ) > MultipleOplogsRollingFeatureJUnitTest sometimes failed in CI > -