[jira] [Commented] (GEODE-6740) TLS endpoint identification fails using hostnames

[ https://issues.apache.org/jira/browse/GEODE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834011#comment-16834011 ] Dan Smith commented on GEODE-6740: -- Ken and I looked a little bit into where the IP address is coming

[jira] [Assigned] (GEODE-6727) CI failure: AcceptorImplClientQueueDistributedTest. clientSubscriptionQueueInitializationShouldNotBlockNewConnections

[ https://issues.apache.org/jira/browse/GEODE-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6727: Assignee: Ryan McMahon > CI failure: AcceptorImplClientQueueDistributedTest. >

[jira] [Commented] (GEODE-6727) CI failure: AcceptorImplClientQueueDistributedTest. clientSubscriptionQueueInitializationShouldNotBlockNewConnections

[ https://issues.apache.org/jira/browse/GEODE-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831768#comment-16831768 ] Dan Smith commented on GEODE-6727: -- This test failed again, and now we get the actual IO error!

[jira] [Updated] (GEODE-6593) ConnectionManagerJUnitTest.testBlocking is consistently failing on windows

[ https://issues.apache.org/jira/browse/GEODE-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6593: - Issue Type: Bug (was: Improvement) > ConnectionManagerJUnitTest.testBlocking is consistently failing on

[jira] [Created] (GEODE-6593) ConnectionManagerJUnitTest.testBlocking is consistently failing on windows

Dan Smith created GEODE-6593: Summary: ConnectionManagerJUnitTest.testBlocking is consistently failing on windows Key: GEODE-6593 URL: https://issues.apache.org/jira/browse/GEODE-6593 Project: Geode

[jira] [Commented] (GEODE-167) Leverage the @ConditionalIgnore annotation and corresponding JUnit Rule to setup conditional test exclusions in the test suite based on timestamp or complex condition im

[ https://issues.apache.org/jira/browse/GEODE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805487#comment-16805487 ] Dan Smith commented on GEODE-167: - Yeah, I don't like the idea of the time delayed test failure - seems

[jira] [Commented] (GEODE-698) Concurrent transactional and non transactional operations on the same key can result in inconsistency

[ https://issues.apache.org/jira/browse/GEODE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804466#comment-16804466 ] Dan Smith commented on GEODE-698: - [~amb] Yes, that's our recommendation. But if you mix them, you don't

[jira] [Resolved] (GEODE-6557) Move admin rest classes into the geode-web project

[ https://issues.apache.org/jira/browse/GEODE-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6557. -- Resolution: Fixed Fix Version/s: 1.10.0 > Move admin rest classes into the geode-web project >

[jira] [Resolved] (GEODE-85) Extract memcached adaptor from core

[ https://issues.apache.org/jira/browse/GEODE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-85. Resolution: Fixed Fix Version/s: 1.10.0 > Extract memcached adaptor from core >

[jira] [Assigned] (GEODE-6557) Move admin rest classes into the geode-web project

[ https://issues.apache.org/jira/browse/GEODE-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6557: Assignee: Dan Smith > Move admin rest classes into the geode-web project >

[jira] [Created] (GEODE-6557) Move admin rest classes into the geode-web project

Dan Smith created GEODE-6557: Summary: Move admin rest classes into the geode-web project Key: GEODE-6557 URL: https://issues.apache.org/jira/browse/GEODE-6557 Project: Geode Issue Type:

[jira] [Assigned] (GEODE-788) Provide region.clear() implementation for Partitioned Regions

[ https://issues.apache.org/jira/browse/GEODE-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-788: --- Assignee: Dan Smith (was: Nick Vallely) > Provide region.clear() implementation for Partitioned

[jira] [Commented] (GEODE-6271) Unknown pdx type error occurs when a single client is connected to two separate clusters

[ https://issues.apache.org/jira/browse/GEODE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797373#comment-16797373 ] Dan Smith commented on GEODE-6271: -- The above changes partially fix this issue, but not completely.

[jira] [Assigned] (GEODE-6271) Unknown pdx type error occurs when a single client is connected to two separate clusters

[ https://issues.apache.org/jira/browse/GEODE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6271: Assignee: Dan Smith > Unknown pdx type error occurs when a single client is connected to two >

[jira] [Resolved] (GEODE-6503) Move Redis apapter to geode-redis module

[ https://issues.apache.org/jira/browse/GEODE-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6503. -- Resolution: Fixed Fix Version/s: 1.10.0 > Move Redis apapter to geode-redis module >

[jira] [Resolved] (GEODE-6447) In CI, Windows Acceptance and Integration tests should not run in parallel

[ https://issues.apache.org/jira/browse/GEODE-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6447. -- Resolution: Fixed > In CI, Windows Acceptance and Integration tests should not run in parallel >

[jira] [Resolved] (GEODE-4240) DeprecatedCacheServerLauncherIntegrationTest fails sporadically with execution timeout

[ https://issues.apache.org/jira/browse/GEODE-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-4240. -- Resolution: Fixed The most recent failures are due to GEODE-6447 - we are running the windows tests

[jira] [Commented] (GEODE-6447) In CI, Windows Acceptance and Integration tests should not run in parallel

[ https://issues.apache.org/jira/browse/GEODE-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790972#comment-16790972 ] Dan Smith commented on GEODE-6447: -- We discovered that these jobs are still running in parallel. The

[jira] [Reopened] (GEODE-6447) In CI, Windows Acceptance and Integration tests should not run in parallel

[ https://issues.apache.org/jira/browse/GEODE-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reopened GEODE-6447: -- > In CI, Windows Acceptance and Integration tests should not run in parallel >

[jira] [Assigned] (GEODE-6503) Move Redis apapter to geode-redis module

[ https://issues.apache.org/jira/browse/GEODE-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6503: Assignee: Dan Smith > Move Redis apapter to geode-redis module >

[jira] [Created] (GEODE-6503) Move Redis apapter to geode-redis module

Dan Smith created GEODE-6503: Summary: Move Redis apapter to geode-redis module Key: GEODE-6503 URL: https://issues.apache.org/jira/browse/GEODE-6503 Project: Geode Issue Type: Bug

[jira] [Resolved] (GEODE-6348) CI Failure: PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown

[ https://issues.apache.org/jira/browse/GEODE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6348. -- Resolution: Fixed Fix Version/s: 1.10.0 > CI Failure: >

[jira] [Assigned] (GEODE-6463) Use storage.googleapis.com for snapshots in the geode-examples build

[ https://issues.apache.org/jira/browse/GEODE-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6463: Assignee: Dan Smith > Use storage.googleapis.com for snapshots in the geode-examples build >

[jira] [Resolved] (GEODE-6463) Use storage.googleapis.com for snapshots in the geode-examples build

[ https://issues.apache.org/jira/browse/GEODE-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6463. -- Resolution: Fixed Fix Version/s: 1.9.0 > Use storage.googleapis.com for snapshots in the

[jira] [Created] (GEODE-6463) Use storage.googleapis.com for snapshots in the geode-examples build

Dan Smith created GEODE-6463: Summary: Use storage.googleapis.com for snapshots in the geode-examples build Key: GEODE-6463 URL: https://issues.apache.org/jira/browse/GEODE-6463 Project: Geode

[jira] [Updated] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)

[ https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5816: - Fix Version/s: (was: 1.9.0) > ClusterStartupRule fails to launch JMX manager (port already in use) >

[jira] [Commented] (GEODE-6372) DestroyIndexIfExistsTest > destroyIndexIfExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777430#comment-16777430 ] Dan Smith commented on GEODE-6372: -- It looks like all of the tests that use GfshRule but do not set

[jira] [Commented] (GEODE-5817) CI Failure: StopServerAcceptanceTest.canStopServerByNameWhenConnectedOverHttp

[ https://issues.apache.org/jira/browse/GEODE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777433#comment-16777433 ] Dan Smith commented on GEODE-5817: -- I think this test probably needs to be changed to not use default

[jira] [Commented] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777398#comment-16777398 ] Dan Smith commented on GEODE-5676: -- This test hung again. The test appears to be deadlocked between the

[jira] [Assigned] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-5676: Assignee: Bruce Schuchardt (was: Dan Smith) > ClusterConfigLocatorRestartDUnitTest hung in CI >

[jira] [Assigned] (GEODE-6436) CI Failure: RebalanceOperationDUnitTest. testRecoverRedundancyBalancing

[ https://issues.apache.org/jira/browse/GEODE-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6436: Assignee: Helena Bales (was: Dan Smith) > CI Failure: RebalanceOperationDUnitTest.

[jira] [Resolved] (GEODE-6436) CI Failure: RebalanceOperationDUnitTest. testRecoverRedundancyBalancing

[ https://issues.apache.org/jira/browse/GEODE-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6436. -- Resolution: Duplicate This issue is caused by the problem described in GEODE-6440. We are ending up

[jira] [Created] (GEODE-6380) Remove all mutable static state from Geode

Dan Smith created GEODE-6380: Summary: Remove all mutable static state from Geode Key: GEODE-6380 URL: https://issues.apache.org/jira/browse/GEODE-6380 Project: Geode Issue Type: Bug

[jira] [Resolved] (GEODE-6328) gfsh show missing-disk-stores lists duplicate disk stores

[ https://issues.apache.org/jira/browse/GEODE-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6328. -- Resolution: Fixed Fix Version/s: 1.9.0 > gfsh show missing-disk-stores lists duplicate disk

[jira] [Resolved] (GEODE-6329) gfsh show missing-disk-stores shows disk stores that aren't missing

[ https://issues.apache.org/jira/browse/GEODE-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6329. -- Resolution: Fixed Fix Version/s: 1.9.0 > gfsh show missing-disk-stores shows disk stores that

[jira] [Updated] (GEODE-6348) CI Failure: PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown

[ https://issues.apache.org/jira/browse/GEODE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6348: - Description: This test failed for me in a StressNewTest run: {noformat}

[jira] [Assigned] (GEODE-6348) CI Failure: PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown

[ https://issues.apache.org/jira/browse/GEODE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6348: Assignee: Dan Smith > CI Failure: >

[jira] [Created] (GEODE-6348) CI Failure: PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown

Dan Smith created GEODE-6348: Summary: CI Failure: PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown Key: GEODE-6348 URL:

[jira] [Created] (GEODE-6342) ThreadsMonitor prints many warnings in gateway sender logs if receiver is not running

Dan Smith created GEODE-6342: Summary: ThreadsMonitor prints many warnings in gateway sender logs if receiver is not running Key: GEODE-6342 URL: https://issues.apache.org/jira/browse/GEODE-6342 Project:

[jira] [Updated] (GEODE-6342) ThreadsMonitor prints many warnings in gateway sender logs if receiver is not running

[ https://issues.apache.org/jira/browse/GEODE-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6342: - Affects Version/s: 1.9.0 > ThreadsMonitor prints many warnings in gateway sender logs if receiver is not

[jira] [Assigned] (GEODE-6342) ThreadsMonitor prints many warnings in gateway sender logs if receiver is not running

[ https://issues.apache.org/jira/browse/GEODE-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6342: Assignee: Bruce Schuchardt > ThreadsMonitor prints many warnings in gateway sender logs if

[jira] [Created] (GEODE-6329) gfsh show missing-disk-stores shows disk stores that aren't missing

Dan Smith created GEODE-6329: Summary: gfsh show missing-disk-stores shows disk stores that aren't missing Key: GEODE-6329 URL: https://issues.apache.org/jira/browse/GEODE-6329 Project: Geode

[jira] [Assigned] (GEODE-6329) gfsh show missing-disk-stores shows disk stores that aren't missing

[ https://issues.apache.org/jira/browse/GEODE-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6329: Assignee: Dan Smith > gfsh show missing-disk-stores shows disk stores that aren't missing >

[jira] [Created] (GEODE-6328) gfsh show missing-disk-stores lists duplicate disk stores

Dan Smith created GEODE-6328: Summary: gfsh show missing-disk-stores lists duplicate disk stores Key: GEODE-6328 URL: https://issues.apache.org/jira/browse/GEODE-6328 Project: Geode Issue Type:

[jira] [Assigned] (GEODE-6328) gfsh show missing-disk-stores lists duplicate disk stores

[ https://issues.apache.org/jira/browse/GEODE-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6328: Assignee: Dan Smith > gfsh show missing-disk-stores lists duplicate disk stores >

[jira] [Commented] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750353#comment-16750353 ] Dan Smith commented on GEODE-5676: -- Looking at the logs, it looks like the ElderInitMessage was dropped

[jira] [Comment Edited] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750319#comment-16750319 ] Dan Smith edited comment on GEODE-5676 at 1/23/19 6:49 PM: --- Callstacks are

[jira] [Commented] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750319#comment-16750319 ] Dan Smith commented on GEODE-5676: -- Callstacks are working again, and we have a run with stack dumps

[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=16745407#comment-16745407 ] Dan Smith commented on GEODE-6284: -- The RMI exception means it couldn't talk to one of the dunit

[jira] [Resolved] (GEODE-5370) DistributedTest task on CI occasionally exceeds timeout

[ https://issues.apache.org/jira/browse/GEODE-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5370. -- Resolution: Won't Fix As Owen pointed out, if the CI times out, it's probably because a test hangs.

[jira] [Assigned] (GEODE-394) Casting FunctionContext to RegionFunctionContext is an ugly API

[ https://issues.apache.org/jira/browse/GEODE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-394: --- Assignee: (was: Dan Smith) > Casting FunctionContext to RegionFunctionContext is an ugly API >

[jira] [Assigned] (GEODE-5863) CqDataDUnitTest.testMultipleExecuteWithInitialResults ignores assertion failures

[ https://issues.apache.org/jira/browse/GEODE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-5863: Assignee: (was: Dan Smith) > CqDataDUnitTest.testMultipleExecuteWithInitialResults ignores

[jira] [Assigned] (GEODE-1762) FunctionService throws exceptions from different places for clients and peers

[ https://issues.apache.org/jira/browse/GEODE-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1762: Assignee: (was: Dan Smith) > FunctionService throws exceptions from different places for

[jira] [Assigned] (GEODE-729) Create new RegionFunction MemberFunction interfaces

[ https://issues.apache.org/jira/browse/GEODE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-729: --- Assignee: (was: Dan Smith) > Create new RegionFunction MemberFunction interfaces >

[jira] [Assigned] (GEODE-404) Using AttributesMutator.addAsyncEventQueueId in a system with concurrent operations will cause failures

[ https://issues.apache.org/jira/browse/GEODE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-404: --- Assignee: (was: Dan Smith) > Using AttributesMutator.addAsyncEventQueueId in a system with

[jira] [Assigned] (GEODE-498) Callback argument size is not reflected in bucket size for parallel queues

[ https://issues.apache.org/jira/browse/GEODE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-498: --- Assignee: (was: Dan Smith) > Callback argument size is not reflected in bucket size for parallel

[jira] [Assigned] (GEODE-625) A function's ResultCollector throws ClassCastException when ResultSender.sendException is invoked

[ https://issues.apache.org/jira/browse/GEODE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-625: --- Assignee: (was: Dan Smith) > A function's ResultCollector throws ClassCastException when >

[jira] [Assigned] (GEODE-727) Move isHA, isHA, hasResult, optimizeForWrite from the Function interface to the Execution interface

[ https://issues.apache.org/jira/browse/GEODE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-727: --- Assignee: (was: Dan Smith) > Move isHA, isHA, hasResult, optimizeForWrite from the Function

[jira] [Assigned] (GEODE-726) Add a getLocalDataSet to RegionFunctionContext and deprecate PartitionRegionHelper.getLocalData(RegionFunctionContext)

[ https://issues.apache.org/jira/browse/GEODE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-726: --- Assignee: (was: Dan Smith) > Add a getLocalDataSet to RegionFunctionContext and deprecate >

[jira] [Assigned] (GEODE-6082) Add tests of Memory Overhead

[ https://issues.apache.org/jira/browse/GEODE-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6082: Assignee: (was: Dan Smith) > Add tests of Memory Overhead > > >

[jira] [Resolved] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)

[ https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5816. -- Resolution: Duplicate Fix Version/s: 1.9.0 The locatorProperties method I mentioned in my

[jira] [Updated] (GEODE-6271) Unknown pdx type error occurs when a single client is connected to two separate clusters

[ https://issues.apache.org/jira/browse/GEODE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6271: - Description: If * A client is connected through two different pools to two different geode clusters *

[jira] [Updated] (GEODE-6271) Unknown pdx type error occurs when a single client is connected to two separate clusters

[ https://issues.apache.org/jira/browse/GEODE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6271: - Attachment: 0001-GEODE-6271-Test-of-client-connected-to-multiple-clus.patch > Unknown pdx type error

[jira] [Created] (GEODE-6271) Unknown pdx type error occurs when a single client is connected to two separate clusters

Dan Smith created GEODE-6271: Summary: Unknown pdx type error occurs when a single client is connected to two separate clusters Key: GEODE-6271 URL: https://issues.apache.org/jira/browse/GEODE-6271

[jira] [Assigned] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)

[ https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-5816: Assignee: Dan Smith (was: Brian Rowe) > ClusterStartupRule fails to launch JMX manager (port

[jira] [Resolved] (GEODE-5674) Stop picking ports randomly for tests

[ https://issues.apache.org/jira/browse/GEODE-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5674. -- Resolution: Fixed All changes for this issue have been merged to develop, closing. > Stop picking

[jira] [Assigned] (GEODE-6135) Add benchmarks to geode CI

[ https://issues.apache.org/jira/browse/GEODE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6135: Assignee: Helena Bales (was: Sean Goller) > Add benchmarks to geode CI >

[jira] [Assigned] (GEODE-6135) Add benchmarks to geode CI

[ https://issues.apache.org/jira/browse/GEODE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6135: Assignee: Sean Goller > Add benchmarks to geode CI > -- > >

[jira] [Resolved] (GEODE-6170) Create scripts for launching benchmarks in AWS

[ https://issues.apache.org/jira/browse/GEODE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6170. -- Resolution: Fixed Fix Version/s: 1.9.0 > Create scripts for launching benchmarks in AWS >

[jira] [Updated] (GEODE-6206) Improve the performance of PartitionedRegion Puts

[ https://issues.apache.org/jira/browse/GEODE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6206: - Issue Type: Improvement (was: Task) > Improve the performance of PartitionedRegion Puts >

[jira] [Updated] (GEODE-6192) Investigate the effect of GEODE-6166 on benchmarks

[ https://issues.apache.org/jira/browse/GEODE-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6192: - Sprint: Current Iteration 5, Current Iteration 6 (was: Current Iteration 5) > Investigate the effect of

[jira] [Updated] (GEODE-6191) Investigate scaleability of benchmarks for different numbers of threads

[ https://issues.apache.org/jira/browse/GEODE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6191: - Sprint: Current Iteration 5, Current Iteration 6 (was: Current Iteration 5) > Investigate scaleability

[jira] [Updated] (GEODE-6134) Generate summary of benchmarks result as part of running the benchmarks

[ https://issues.apache.org/jira/browse/GEODE-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6134: - Sprint: Current Iteration 4, Current Iteration 5, Current Iteration 6 (was: Current Iteration 4,

[jira] [Updated] (GEODE-6215) Session module does not create region on all servers

[ https://issues.apache.org/jira/browse/GEODE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6215: - Description: When session modules bootstrap, the region responsible for distributing the session region

[jira] [Assigned] (GEODE-6215) Session module does not create region on all servers

[ https://issues.apache.org/jira/browse/GEODE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-6215: Assignee: Jacob S. Barrett > Session module does not create region on all servers >

[jira] [Commented] (GEODE-6215) Session module does not create region on all servers

[ https://issues.apache.org/jira/browse/GEODE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723467#comment-16723467 ] Dan Smith commented on GEODE-6215: -- It looks like this has been broken since geode 1.0.0. The changes in

[jira] [Updated] (GEODE-6215) Session module does not create region on all servers

[ https://issues.apache.org/jira/browse/GEODE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6215: - Description: When session modules bootstrap, the region responsible for distributing the session region

[jira] [Updated] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5676: - Sprint: Current Iteration 6 (was: Current Iteration 5) > ClusterConfigLocatorRestartDUnitTest hung in

[jira] [Updated] (GEODE-6190) Investigate reproducability of ReplicatedPutBenchmark

[ https://issues.apache.org/jira/browse/GEODE-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6190: - Sprint: Current Iteration 6 > Investigate reproducability of ReplicatedPutBenchmark >

[jira] [Created] (GEODE-6206) Improve the performance of PartitionedRegion Puts

Dan Smith created GEODE-6206: Summary: Improve the performance of PartitionedRegion Puts Key: GEODE-6206 URL: https://issues.apache.org/jira/browse/GEODE-6206 Project: Geode Issue Type: Task

[jira] [Resolved] (GEODE-6146) Cleanup PortfolioPdx object in benchmarks

[ https://issues.apache.org/jira/browse/GEODE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-6146. -- Resolution: Fixed Fix Version/s: 1.9.0 > Cleanup PortfolioPdx object in benchmarks >

[jira] [Created] (GEODE-6207) Investigate reproducability of benchmark results with current infrastructure and tests

Dan Smith created GEODE-6207: Summary: Investigate reproducability of benchmark results with current infrastructure and tests Key: GEODE-6207 URL: https://issues.apache.org/jira/browse/GEODE-6207

[jira] [Updated] (GEODE-6147) Fail benchmark junit tests if their numbers deviate too far from a baseline

[ https://issues.apache.org/jira/browse/GEODE-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6147: - Sprint: Current Iteration 6 > Fail benchmark junit tests if their numbers deviate too far from a

[jira] [Updated] (GEODE-6206) Improve the performance of PartitionedRegion Puts

[ https://issues.apache.org/jira/browse/GEODE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6206: - Sprint: Current Iteration 6 > Improve the performance of PartitionedRegion Puts >

[jira] [Updated] (GEODE-6135) Add benchmarks to geode CI

[ https://issues.apache.org/jira/browse/GEODE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6135: - Sprint: Current Iteration 6 (was: Current Iteration 5) > Add benchmarks to geode CI >

[jira] [Updated] (GEODE-6203) Include uncertainity values to analyzeRun results

[ https://issues.apache.org/jira/browse/GEODE-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6203: - Sprint: Current Iteration 6 > Include uncertainity values to analyzeRun results >

[jira] [Updated] (GEODE-6203) Include uncertainity values to analyzeRun results

[ https://issues.apache.org/jira/browse/GEODE-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6203: - Summary: Include uncertainity values to analyzeRun results (was: Include uncertainity values to

[jira] [Created] (GEODE-6203) Include uncertainity values to anaylzeRun results

Dan Smith created GEODE-6203: Summary: Include uncertainity values to anaylzeRun results Key: GEODE-6203 URL: https://issues.apache.org/jira/browse/GEODE-6203 Project: Geode Issue Type: Task

[jira] [Updated] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5676: - Component/s: benchmarks > ClusterConfigLocatorRestartDUnitTest hung in CI >

[jira] [Updated] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI

[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5676: - Sprint: Current Iteration 5 > ClusterConfigLocatorRestartDUnitTest hung in CI >

[jira] [Updated] (GEODE-6192) Investigate the effect of GEODE-6166 on benchmarks

[ https://issues.apache.org/jira/browse/GEODE-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6192: - Summary: Investigate the effect of GEODE-6166 on benchmarks (was: Investigate the effect of perf

[jira] [Updated] (GEODE-6192) Investigate the effect of perf improvement from GEODE-6166 on benchmarks

[ https://issues.apache.org/jira/browse/GEODE-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6192: - Sprint: Current Iteration 5 > Investigate the effect of perf improvement from GEODE-6166 on benchmarks >

[jira] [Created] (GEODE-6193) Add unit tests that measure the size of performance critical Geode messages

Dan Smith created GEODE-6193: Summary: Add unit tests that measure the size of performance critical Geode messages Key: GEODE-6193 URL: https://issues.apache.org/jira/browse/GEODE-6193 Project: Geode

[jira] [Updated] (GEODE-6191) Investigate scaleability of benchmarks for different numbers of threads

[ https://issues.apache.org/jira/browse/GEODE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6191: - Sprint: Current Iteration 5 > Investigate scaleability of benchmarks for different numbers of threads >

[jira] [Updated] (GEODE-6148) Improve the efficiency of PrePopulateRegion and increase the key range

[ https://issues.apache.org/jira/browse/GEODE-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6148: - Sprint: Current Iteration 5 > Improve the efficiency of PrePopulateRegion and increase the key range >

[jira] [Created] (GEODE-6192) Investigate the effect of perf improvement from GEODE-6166 on benchmarks

Dan Smith created GEODE-6192: Summary: Investigate the effect of perf improvement from GEODE-6166 on benchmarks Key: GEODE-6192 URL: https://issues.apache.org/jira/browse/GEODE-6192 Project: Geode

[jira] [Commented] (GEODE-6191) Investigate scaleability of benchmarks for different numbers of threads

[ https://issues.apache.org/jira/browse/GEODE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718310#comment-16718310 ] Dan Smith commented on GEODE-6191: -- Here is the comparison between 48 threads vs 192 threads in google

[jira] [Created] (GEODE-6191) Investigate scaleability of benchmarks for different numbers of threads

Dan Smith created GEODE-6191: Summary: Investigate scaleability of benchmarks for different numbers of threads Key: GEODE-6191 URL: https://issues.apache.org/jira/browse/GEODE-6191 Project: Geode

[jira] [Updated] (GEODE-6191) Investigate scaleability of benchmarks for different numbers of threads

[ https://issues.apache.org/jira/browse/GEODE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-6191: - Component/s: benchmarks > Investigate scaleability of benchmarks for different numbers of threads >

[jira] [Commented] (GEODE-6190) Investigate reproducability of ReplicatedPutBenchmark

[ https://issues.apache.org/jira/browse/GEODE-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718291#comment-16718291 ] Dan Smith commented on GEODE-6190: -- Here is a chart of the throughput of two back to back runs of

<    1   2   3   4   5   6   7   8   9   10   >