[jira] [Resolved] (GEODE-10306) CacheServerImpl should stop the acceptor immediately after stop is called

[ https://issues.apache.org/jira/browse/GEODE-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10306. - Fix Version/s: 1.16.0 Resolution: Fixed Moved up the acceptor close  > CacheServerImpl

[jira] [Assigned] (GEODE-10306) CacheServerImpl should stop the acceptor immediately after stop is called

[ https://issues.apache.org/jira/browse/GEODE-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-10306: --- Assignee: Mark Hanson > CacheServerImpl should stop the acceptor immediately after stop is

[jira] [Created] (GEODE-10306) CacheServerImpl should stop the acceptor immediately after stop is called

Mark Hanson created GEODE-10306: --- Summary: CacheServerImpl should stop the acceptor immediately after stop is called Key: GEODE-10306 URL: https://issues.apache.org/jira/browse/GEODE-10306 Project:

[jira] [Updated] (GEODE-10265) DurableClientSimpleDUnitTest.testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML cannot be run in parallel with itself.

[ https://issues.apache.org/jira/browse/GEODE-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-10265: Description: This test uses a hardcoded cache.xml with a server port inside that is hardcoded.

[jira] [Updated] (GEODE-10265) DurableClientSimpleDUnitTest.testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML cannot be run in parallel with itself.

[ https://issues.apache.org/jira/browse/GEODE-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-10265: Description: This test uses a hardcoded cache.xml with a server port inside that is hardcoded.

[jira] [Updated] (GEODE-10265) DurableClientSimpleDUnitTest.testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML cannot be run in parallel with itself.

[ https://issues.apache.org/jira/browse/GEODE-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-10265: Description: This test uses a hardcoded cache.xml with a server port inside that is hardcoded.

[jira] [Created] (GEODE-10265) DurableClientSimpleDUnitTest.testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML cannot be run in parallel with itself.

Mark Hanson created GEODE-10265: --- Summary: DurableClientSimpleDUnitTest.testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML cannot be run in parallel with itself. Key: GEODE-10265 URL:

[jira] [Commented] (GEODE-10228) CI Failure: DurableClientTestCase > testDurableHAFailover times out in await for failover

[ https://issues.apache.org/jira/browse/GEODE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529520#comment-17529520 ] Mark Hanson commented on GEODE-10228: - Tracked down a new issue found during stress-new-test of PR

[jira] [Commented] (GEODE-10228) CI Failure: DurableClientTestCase > testDurableHAFailover times out in await for failover

[ https://issues.apache.org/jira/browse/GEODE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528380#comment-17528380 ] Mark Hanson commented on GEODE-10228: - Awaiting PR review approvals at this point. The initial code

[jira] [Resolved] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10248. - Fix Version/s: 1.15.0 Resolution: Fixed > CI: DeployToMultiGroupDUnitTest encountered

[jira] [Commented] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528379#comment-17528379 ] Mark Hanson commented on GEODE-10248: - The core problem was that the test was outputting a string

[jira] [Commented] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17525157#comment-17525157 ] Mark Hanson commented on GEODE-10248: - Not sure why this is failing now. This is a log statement

[jira] [Assigned] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-10248: --- Assignee: Mark Hanson > CI: DeployToMultiGroupDUnitTest encountered suspect string >

[jira] [Assigned] (GEODE-10228) CI Failure: DurableClientTestCase > testDurableHAFailover times out in await for failover

[ https://issues.apache.org/jira/browse/GEODE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-10228: --- Assignee: Mark Hanson > CI Failure: DurableClientTestCase > testDurableHAFailover times

[jira] [Resolved] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9704. Fix Version/s: 1.15.0 Resolution: Fixed > When durable clients recovers, it sends "ready

[jira] [Created] (GEODE-10195) MicrometerBinderTest > processorMetricsBinderExists FAILED

Mark Hanson created GEODE-10195: --- Summary: MicrometerBinderTest > processorMetricsBinderExists FAILED Key: GEODE-10195 URL: https://issues.apache.org/jira/browse/GEODE-10195 Project: Geode

[jira] [Resolved] (GEODE-10153) Benchmarks: PartitionedPutAllBenchmark: net.schmizz.sshj.transport.TransportException: Connection reset

[ https://issues.apache.org/jira/browse/GEODE-10153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10153. - Resolution: Duplicate > Benchmarks: PartitionedPutAllBenchmark: >

[jira] [Resolved] (GEODE-10173) CI failure: P2pPartitionedGetBenchmark > run()

[ https://issues.apache.org/jira/browse/GEODE-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10173. - Resolution: Duplicate > CI failure: P2pPartitionedGetBenchmark > run() >

[jira] [Resolved] (GEODE-10178) CI Failure: PartitionedGetLongBenchmark > run()

[ https://issues.apache.org/jira/browse/GEODE-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10178. - Resolution: Duplicate > CI Failure: PartitionedGetLongBenchmark > run() >

[jira] [Resolved] (GEODE-10154) Benchmarks: PartitionedIndexedQueryBenchmark: net.schmizz.sshj.transport.TransportException: Server closed connection during identification exchange

[ https://issues.apache.org/jira/browse/GEODE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10154. - Resolution: Fixed This is benchmark job path issue fixed in concourse. > Benchmarks:

[jira] [Assigned] (GEODE-10153) Benchmarks: PartitionedPutAllBenchmark: net.schmizz.sshj.transport.TransportException: Connection reset

[ https://issues.apache.org/jira/browse/GEODE-10153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-10153: --- Assignee: Mark Hanson > Benchmarks: PartitionedPutAllBenchmark: >

[jira] [Commented] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512627#comment-17512627 ] Mark Hanson commented on GEODE-9704: PR 7442 is available. I have made  changes to fix the behavior

[jira] [Updated] (GEODE-5564) Flaky test ConcurrentIndexInitOnOverflowRegionDUnitTest > testIndexUpdateWithRegionClear

[ https://issues.apache.org/jira/browse/GEODE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5564: --- Affects Version/s: 1.14.0 > Flaky test ConcurrentIndexInitOnOverflowRegionDUnitTest > >

[jira] [Created] (GEODE-10154) Benchmarks: PartitionedIndexedQueryBenchmark: net.schmizz.sshj.transport.TransportException: Server closed connection during identification exchange

Mark Hanson created GEODE-10154: --- Summary: Benchmarks: PartitionedIndexedQueryBenchmark: net.schmizz.sshj.transport.TransportException: Server closed connection during identification exchange Key: GEODE-10154 URL:

[jira] [Created] (GEODE-10153) Benchmarks: PartitionedPutAllBenchmark: net.schmizz.sshj.transport.TransportException: Connection reset

Mark Hanson created GEODE-10153: --- Summary: Benchmarks: PartitionedPutAllBenchmark: net.schmizz.sshj.transport.TransportException: Connection reset Key: GEODE-10153 URL:

[jira] [Reopened] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reopened GEODE-9704: > When durable clients recovers, it sends "ready for event" signal before > register for interest,

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9704: --- Labels: GeodeOperationAPI blocks-1.15.1 pull-request-available (was: GeodeOperationAPI

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9704: --- Labels: GeodeOperationAPI blocks-1.15.0 pull-request-available (was: GeodeOperationAPI

[jira] [Created] (GEODE-10039) BucketProfiles can be stale in rare cases.

Mark Hanson created GEODE-10039: --- Summary: BucketProfiles can be stale in rare cases. Key: GEODE-10039 URL: https://issues.apache.org/jira/browse/GEODE-10039 Project: Geode Issue Type: Bug

[jira] [Resolved] (GEODE-9815) Recovering persistent members can result in extra copies of a bucket or two copies in the same redundancy zone

[ https://issues.apache.org/jira/browse/GEODE-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9815. Fix Version/s: 1.15.0 Resolution: Fixed The solution to this was to change the logic to

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9704: --- Description: This is the old Geode behavior, but may or may not be the correct behavior. When

[jira] [Assigned] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9704: -- Assignee: Mark Hanson (was: Kirk Lund) > When durable clients recovers, it sends "ready for

[jira] [Resolved] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9920. Resolution: Won't Fix This is a resource issue where we saw a 10 second delay on wakeup for stats.

[jira] [Commented] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470138#comment-17470138 ] Mark Hanson commented on GEODE-9920: Our initial diagnosis was that this was a port issue. This was

[jira] [Commented] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469595#comment-17469595 ] Mark Hanson commented on GEODE-9920: closed it, but then we started relooking at the problem after

[jira] [Closed] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson closed GEODE-9920. -- > CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and >

[jira] [Resolved] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9920. Resolution: Won't Fix This port issue has been fixed by Dale's changes on develop, that are now in

[jira] [Updated] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9920: --- Description: StopLocatorCommandDUnitTest.testWithInvalidMemberID failured with AssertionError and

[jira] [Commented] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469554#comment-17469554 ] Mark Hanson commented on GEODE-9920: 1.12 does not have [~demery]'s changes to make or port

[jira] [Assigned] (GEODE-9920) CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and RegionReliabilityDistNoAckDUnitTest > testLimitedAccess failed with port conflict

[ https://issues.apache.org/jira/browse/GEODE-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9920: -- Assignee: Mark Hanson > CI Failure: StopLocatorCommandDUnitTest > testWithInvalidMemberID and

[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append

[ https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468855#comment-17468855 ] Mark Hanson commented on GEODE-9885: I just took a look at the test and this doesn't look like a test

[jira] [Commented] (GEODE-9815) Recovering persistent members can result in extra copies of a bucket or two copies in the same redundancy zone

[ https://issues.apache.org/jira/browse/GEODE-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468755#comment-17468755 ] Mark Hanson commented on GEODE-9815: I have addressed all of the concerns with a solution that I am

[jira] [Created] (GEODE-9878) PostgresJdbcLoaderIntegrationTest. initializationError failed

Mark Hanson created GEODE-9878: -- Summary: PostgresJdbcLoaderIntegrationTest. initializationError failed Key: GEODE-9878 URL: https://issues.apache.org/jira/browse/GEODE-9878 Project: Geode

[jira] [Created] (GEODE-9877) GeodeRedisServerStartupDUnitTest. startupFailsGivenPortAlreadyInUse failed

Mark Hanson created GEODE-9877: -- Summary: GeodeRedisServerStartupDUnitTest. startupFailsGivenPortAlreadyInUse failed Key: GEODE-9877 URL: https://issues.apache.org/jira/browse/GEODE-9877 Project: Geode

[jira] [Commented] (GEODE-9876) SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest > testSerialGatewaySenderThreadsConnectToSameReceiver FAILED

[ https://issues.apache.org/jira/browse/GEODE-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454911#comment-17454911 ] Mark Hanson commented on GEODE-9876: Hi Mario, This looks like an error related to GEODE-8202. Can

[jira] [Assigned] (GEODE-9876) SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest > testSerialGatewaySenderThreadsConnectToSameReceiver FAILED

[ https://issues.apache.org/jira/browse/GEODE-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9876: -- Assignee: Mario Kevo > SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest > >

[jira] [Created] (GEODE-9876) SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest > testSerialGatewaySenderThreadsConnectToSameReceiver FAILED

Mark Hanson created GEODE-9876: -- Summary: SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest > testSerialGatewaySenderThreadsConnectToSameReceiver FAILED Key: GEODE-9876 URL:

[jira] [Commented] (GEODE-9815) Recovering persistent members can result in extra copies of a bucket or two copies in the same redundancy zone

[ https://issues.apache.org/jira/browse/GEODE-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452113#comment-17452113 ] Mark Hanson commented on GEODE-9815: I have addressed the two cases above. I am not particularly

[jira] [Commented] (GEODE-9856) SMoveNativeRedisAcceptanceTest is failing with cluster is down.

[ https://issues.apache.org/jira/browse/GEODE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450699#comment-17450699 ] Mark Hanson commented on GEODE-9856: Seems related. Should be confirmed. >

[jira] [Comment Edited] (GEODE-9856) SMoveNativeRedisAcceptanceTest is failing with cluster is down.

[ https://issues.apache.org/jira/browse/GEODE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450699#comment-17450699 ] Mark Hanson edited comment on GEODE-9856 at 11/29/21, 7:45 PM: --- GEODE-9428

[jira] [Created] (GEODE-9861) Windows: ResultModelTest.serializeFileToDownload Failed

Mark Hanson created GEODE-9861: -- Summary: Windows: ResultModelTest.serializeFileToDownload Failed Key: GEODE-9861 URL: https://issues.apache.org/jira/browse/GEODE-9861 Project: Geode Issue

[jira] [Updated] (GEODE-9859) Mass-Test-Run: WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED

[ https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9859: --- Summary: Mass-Test-Run: WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false,

[jira] [Created] (GEODE-9860) NativeRedisRenameRedirectionsDUnitTest. initializationError

Mark Hanson created GEODE-9860: -- Summary: NativeRedisRenameRedirectionsDUnitTest. initializationError Key: GEODE-9860 URL: https://issues.apache.org/jira/browse/GEODE-9860 Project: Geode Issue

[jira] [Assigned] (GEODE-9859) WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED

[ https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9859: -- Assignee: Alberto Gomez >

[jira] [Updated] (GEODE-9859) WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED

[ https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9859: --- Description: Looks like this might be failing from the original PR. I have linked to GEODE-9369 as

[jira] [Commented] (GEODE-9859) WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED

[ https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450670#comment-17450670 ] Mark Hanson commented on GEODE-9859: This test was failing under windows on the original PR. >

[jira] [Created] (GEODE-9859) WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED

Mark Hanson created GEODE-9859: -- Summary: WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED Key: GEODE-9859 URL: https://issues.apache.org/jira/browse/GEODE-9859

[jira] [Created] (GEODE-9858) Mass-Test-Run failure PingOpDistributedTest. memberShouldCorrectlyRedirectPingMessage

Mark Hanson created GEODE-9858: -- Summary: Mass-Test-Run failure PingOpDistributedTest. memberShouldCorrectlyRedirectPingMessage Key: GEODE-9858 URL: https://issues.apache.org/jira/browse/GEODE-9858

[jira] [Created] (GEODE-9857) ShowMissingDiskStoreCommandDUnitTest. stopAllMembersAndStart2ndLocator

Mark Hanson created GEODE-9857: -- Summary: ShowMissingDiskStoreCommandDUnitTest. stopAllMembersAndStart2ndLocator Key: GEODE-9857 URL: https://issues.apache.org/jira/browse/GEODE-9857 Project: Geode

[jira] [Updated] (GEODE-9857) ShowMissingDiskStoreCommandDUnitTest. stopAllMembersAndStart2ndLocator

[ https://issues.apache.org/jira/browse/GEODE-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9857: --- Labels: needsTriage (was: ) > ShowMissingDiskStoreCommandDUnitTest.

[jira] [Updated] (GEODE-9856) SMoveNativeRedisAcceptanceTest is failing with cluster is down.

[ https://issues.apache.org/jira/browse/GEODE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9856: --- Labels: needsTriage (was: ) > SMoveNativeRedisAcceptanceTest is failing with cluster is down. >

[jira] [Created] (GEODE-9856) SMoveNativeRedisAcceptanceTest is failing with cluster is down.

Mark Hanson created GEODE-9856: -- Summary: SMoveNativeRedisAcceptanceTest is failing with cluster is down. Key: GEODE-9856 URL: https://issues.apache.org/jira/browse/GEODE-9856 Project: Geode

[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly

[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17445643#comment-17445643 ] Mark Hanson commented on GEODE-8644:  I have rerun this on a variety of cloud instances trying to

[jira] [Assigned] (GEODE-9815) Recovering persistent members can result in extra copies of a bucket or two copies int the same redundancy zone

[ https://issues.apache.org/jira/browse/GEODE-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9815: -- Assignee: Mark Hanson > Recovering persistent members can result in extra copies of a bucket

[jira] [Assigned] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly

[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-8644: -- Assignee: Mark Hanson >

[jira] [Assigned] (GEODE-9425) AutoConnectionSource thread in client can't query for available locators when it is connected to a locator that was shut down

[ https://issues.apache.org/jira/browse/GEODE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9425: -- Assignee: (was: Mark Hanson) > AutoConnectionSource thread in client can't query for

[jira] [Commented] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client

[ https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17442142#comment-17442142 ] Mark Hanson commented on GEODE-8616: Added a couple of reproductions to the bug as attachments. These

[jira] [Updated] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client

[ https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-8616: --- Attachment: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz

[jira] [Assigned] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client

[ https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-8616: -- Assignee: Mark Hanson > ClientServerCacheOperationDUnitTest > >

[jira] [Assigned] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client

[ https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-8616: -- Assignee: (was: Mark Hanson) > ClientServerCacheOperationDUnitTest > >

[jira] [Commented] (GEODE-9425) AutoConnectionSource thread in client can't query for available locators when it is connected to a locator that was shut down

[ https://issues.apache.org/jira/browse/GEODE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437768#comment-17437768 ] Mark Hanson commented on GEODE-9425: Are there more logs available? > AutoConnectionSource thread in

[jira] [Assigned] (GEODE-9425) AutoConnectionSource thread in client can't query for available locators when it is connected to a locator that was shut down

[ https://issues.apache.org/jira/browse/GEODE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9425: -- Assignee: Mark Hanson > AutoConnectionSource thread in client can't query for available

[jira] [Resolved] (GEODE-9645) MultiUserAuth: DataSerializerRecoveryListener is called without auth information. Promptly fails

[ https://issues.apache.org/jira/browse/GEODE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9645. Fix Version/s: 1.15.0 Resolution: Fixed The code will not send DataSerializer registration

[jira] [Assigned] (GEODE-9617) CI Failure: PartitionedRegionSingleHopDUnitTest fails with ConditionTimeoutException waiting for server to bucket map size

[ https://issues.apache.org/jira/browse/GEODE-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9617: -- Assignee: Mark Hanson > CI Failure: PartitionedRegionSingleHopDUnitTest fails with >

[jira] [Commented] (GEODE-9617) CI Failure: PartitionedRegionSingleHopDUnitTest fails with ConditionTimeoutException waiting for server to bucket map size

[ https://issues.apache.org/jira/browse/GEODE-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427402#comment-17427402 ] Mark Hanson commented on GEODE-9617: I did a little cleanup and added an assert that should help in

[jira] [Updated] (GEODE-9645) MultiUserAuth: DataSerializerRecoveryListener is called without auth information. Promptly fails

[ https://issues.apache.org/jira/browse/GEODE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9645: --- Labels: pull-request-available (was: needsTriage pull-request-available) > MultiUserAuth:

[jira] [Updated] (GEODE-9647) MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer.

[ https://issues.apache.org/jira/browse/GEODE-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9647: --- Labels: (was: needsTriage) > MultiUserAuth: DataSerializer.Register throws when attempting to

[jira] [Resolved] (GEODE-9647) MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer.

[ https://issues.apache.org/jira/browse/GEODE-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9647. Resolution: Duplicate One solution can fix both of these issues as they are related. So closing

[jira] [Assigned] (GEODE-9647) MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer.

[ https://issues.apache.org/jira/browse/GEODE-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9647: -- Assignee: Mark Hanson > MultiUserAuth: DataSerializer.Register throws when attempting to

[jira] [Assigned] (GEODE-9645) MultiUserAuth: DataSerializerRecoveryListener is called without auth information. Promptly fails

[ https://issues.apache.org/jira/browse/GEODE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9645: -- Assignee: Mark Hanson > MultiUserAuth: DataSerializerRecoveryListener is called without auth

[jira] [Commented] (GEODE-9647) MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer.

[ https://issues.apache.org/jira/browse/GEODE-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17421565#comment-17421565 ] Mark Hanson commented on GEODE-9647: The solution appears to be to plumb the regionService down into

[jira] [Updated] (GEODE-9647) MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer.

[ https://issues.apache.org/jira/browse/GEODE-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9647: --- Description: When multiuserSecureModeEnabled is set, a user may attempt to register a

[jira] [Created] (GEODE-9647) MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer.

Mark Hanson created GEODE-9647: -- Summary: MultiUserAuth: DataSerializer.Register throws when attempting to register a new DataSerializer. Key: GEODE-9647 URL: https://issues.apache.org/jira/browse/GEODE-9647

[jira] [Updated] (GEODE-9645) MultiUserAuth: DataSerializerRecoveryListener is called without auth information. Promptly fails

[ https://issues.apache.org/jira/browse/GEODE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9645: --- Description: When multiuserSecureModeEnabled is enabled,  a user may register a DataSerializer.

[jira] [Created] (GEODE-9645) MultiUserAuth: DataSerializerRecoveryListener is called without auth information. Promptly fails

Mark Hanson created GEODE-9645: -- Summary: MultiUserAuth: DataSerializerRecoveryListener is called without auth information. Promptly fails Key: GEODE-9645 URL: https://issues.apache.org/jira/browse/GEODE-9645

[jira] [Resolved] (GEODE-9365) HARegionQueue over throttles when multiple threads attempt concurrent adds

[ https://issues.apache.org/jira/browse/GEODE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9365. Fix Version/s: 1.15.0 Resolution: Fixed This fix includes changes to reduce the number of

[jira] [Created] (GEODE-9603) BlockingHARegionJUnitTest is in need of a refactor. It is poorly written by current standards.

Mark Hanson created GEODE-9603: -- Summary: BlockingHARegionJUnitTest is in need of a refactor. It is poorly written by current standards. Key: GEODE-9603 URL: https://issues.apache.org/jira/browse/GEODE-9603

[jira] [Resolved] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail

[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9554. Fix Version/s: 1.15.0 1.14.1 1.13.5 1.12.5

[jira] [Commented] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail

[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17412119#comment-17412119 ] Mark Hanson commented on GEODE-9554: I have a new fix that should address this issue better, plus

[jira] [Created] (GEODE-9584) PartitionedRegionLoadModel.createRedundantBucket

Mark Hanson created GEODE-9584: -- Summary: PartitionedRegionLoadModel.createRedundantBucket Key: GEODE-9584 URL: https://issues.apache.org/jira/browse/GEODE-9584 Project: Geode Issue Type:

[jira] [Commented] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail

[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408994#comment-17408994 ] Mark Hanson commented on GEODE-9554: I have a new fix for this that will address all of the known

[jira] [Assigned] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail

[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9554: -- Assignee: Mark Hanson > Rebalancing a region with multiple redundancy zones can fail >

[jira] [Created] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail

Mark Hanson created GEODE-9554: -- Summary: Rebalancing a region with multiple redundancy zones can fail Key: GEODE-9554 URL: https://issues.apache.org/jira/browse/GEODE-9554 Project: Geode

[jira] [Updated] (GEODE-9520) create index gfsh command behavior seems inconsistent with other commands

[ https://issues.apache.org/jira/browse/GEODE-9520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-9520: --- Description: The way the command currently works, when you it uses the group of the region to

[jira] [Created] (GEODE-9520) Error message is not useful when trying to create index after using a cache xml for startup

Mark Hanson created GEODE-9520: -- Summary: Error message is not useful when trying to create index after using a cache xml for startup Key: GEODE-9520 URL: https://issues.apache.org/jira/browse/GEODE-9520

[jira] [Commented] (GEODE-9490) CI failure: NativeRedisSessionAcceptanceTest > executionError

[ https://issues.apache.org/jira/browse/GEODE-9490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397481#comment-17397481 ] Mark Hanson commented on GEODE-9490: Ignore ^ build 108 failure note. > CI failure:

[jira] [Resolved] (GEODE-9194) Move PR clear related statistics to the appropriate classes

[ https://issues.apache.org/jira/browse/GEODE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-9194. Fix Version/s: 1.15.0 Assignee: Mark Hanson Resolution: Fixed This has been merged

[jira] [Commented] (GEODE-9365) HARegionQueue over throttles when multiple threads attempt concurrent adds

[ https://issues.apache.org/jira/browse/GEODE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378311#comment-17378311 ] Mark Hanson commented on GEODE-9365: I am testing the "other solution". That seems like a simple

[jira] [Commented] (GEODE-8064) DeploymentSemanticVersionJarDUnitTest.java (GEODE-7421) is failing.

[ https://issues.apache.org/jira/browse/GEODE-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378295#comment-17378295 ] Mark Hanson commented on GEODE-8064: Another issue with this test  {noformat}

[jira] [Assigned] (GEODE-9365) HARegionQueue over throttles when multiple threads attempt concurrent adds

[ https://issues.apache.org/jira/browse/GEODE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-9365: -- Assignee: Mark Hanson > HARegionQueue over throttles when multiple threads attempt concurrent

  1   2   3   4   5   6   7   8   9   10   >