[jira] [Commented] (GEODE-3170) Geode keeps logging org.apache.geode.protocol.exception.InvalidProtocolMessageException

[ https://issues.apache.org/jira/browse/GEODE-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078285#comment-16078285 ] Alexander Murmann commented on GEODE-3170: -- Hitesh came up with the very likely theory that this

[jira] [Updated] (GEODE-3192) PutAll on new protocol informs client which keys couldn't be inserted

[ https://issues.apache.org/jira/browse/GEODE-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3192: - Description: When a putAll request fails to insert a given key/value pair the

[jira] [Updated] (GEODE-3192) PutAll on new protocol informs client which keys couldn't be inserted

[ https://issues.apache.org/jira/browse/GEODE-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3192: - Description: When a putAll request fails to insert a given key/value pair the

[jira] [Created] (GEODE-3170) Geode keeps logging org.apache.geode.protocol.exception.InvalidProtocolMessageException

Alexander Murmann created GEODE-3170: Summary: Geode keeps logging org.apache.geode.protocol.exception.InvalidProtocolMessageException Key: GEODE-3170 URL: https://issues.apache.org/jira/browse/GEODE-3170

[jira] [Created] (GEODE-3192) PutAll on new protocol informs client which keys couldn't be inserted

Alexander Murmann created GEODE-3192: Summary: PutAll on new protocol informs client which keys couldn't be inserted Key: GEODE-3192 URL: https://issues.apache.org/jira/browse/GEODE-3192 Project:

[jira] [Updated] (GEODE-3192) PutAll on new protocol informs client which keys couldn't be inserted

[ https://issues.apache.org/jira/browse/GEODE-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3192: - Description: When a putAll request fails to insert a given key/value pair the

[jira] [Created] (GEODE-3464) If multiple MessageHandlers are found user should see exception

Alexander Murmann created GEODE-3464: Summary: If multiple MessageHandlers are found user should see exception Key: GEODE-3464 URL: https://issues.apache.org/jira/browse/GEODE-3464 Project: Geode

[jira] [Created] (GEODE-3463) Ensure ProtoBuf requests are tracked propery

Alexander Murmann created GEODE-3463: Summary: Ensure ProtoBuf requests are tracked propery Key: GEODE-3463 URL: https://issues.apache.org/jira/browse/GEODE-3463 Project: Geode Issue

[jira] [Created] (GEODE-3465) GetAvailableServerRequest on Locator accepts group

Alexander Murmann created GEODE-3465: Summary: GetAvailableServerRequest on Locator accepts group Key: GEODE-3465 URL: https://issues.apache.org/jira/browse/GEODE-3465 Project: Geode

[jira] [Created] (GEODE-3459) Remove feature toggle for new client protocl

Alexander Murmann created GEODE-3459: Summary: Remove feature toggle for new client protocl Key: GEODE-3459 URL: https://issues.apache.org/jira/browse/GEODE-3459 Project: Geode Issue

[jira] [Assigned] (GEODE-3400) GetAvailableServers on locators

[ https://issues.apache.org/jira/browse/GEODE-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3400: Assignee: Alexander Murmann > GetAvailableServers on locators >

[jira] [Assigned] (GEODE-3406) Enable new flow for protocol on locators

[ https://issues.apache.org/jira/browse/GEODE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3406: Assignee: Alexander Murmann > Enable new flow for protocol on locators >

[jira] [Assigned] (GEODE-3399) Enable protocol feature toggle on locators

[ https://issues.apache.org/jira/browse/GEODE-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3399: Assignee: Alexander Murmann > Enable protocol feature toggle on locators >

[jira] [Commented] (GEODE-3617) replace gemfire with geode in config parameter

[ https://issues.apache.org/jira/browse/GEODE-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173884#comment-16173884 ] Alexander Murmann commented on GEODE-3617: -- We shouldn't replace these, but instead support both

[jira] [Updated] (GEODE-3616) Clean up ClientHealthMontiorJUnitTest

[ https://issues.apache.org/jira/browse/GEODE-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3616: - Component/s: client/server > Clean up ClientHealthMontiorJUnitTest >

[jira] [Created] (GEODE-3616) Clean up ClientHealthMontiorJUnitTest

Alexander Murmann created GEODE-3616: Summary: Clean up ClientHealthMontiorJUnitTest Key: GEODE-3616 URL: https://issues.apache.org/jira/browse/GEODE-3616 Project: Geode Issue Type: Task

[jira] [Resolved] (GEODE-3082) Client Health Monitor should be able to manage new protocol client connections

[ https://issues.apache.org/jira/browse/GEODE-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann resolved GEODE-3082. -- Resolution: Fixed Assignee: Alexander Murmann > Client Health Monitor should be

[jira] [Created] (GEODE-3623) Resolve messed up merges into develop

Alexander Murmann created GEODE-3623: Summary: Resolve messed up merges into develop Key: GEODE-3623 URL: https://issues.apache.org/jira/browse/GEODE-3623 Project: Geode Issue Type: Task

[jira] [Resolved] (GEODE-3079) Ensure new protocol shuts down cleanly

[ https://issues.apache.org/jira/browse/GEODE-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann resolved GEODE-3079. -- Resolution: Fixed Assignee: Alexander Murmann (was: Galen O'Sullivan) > Ensure

[jira] [Created] (GEODE-3535) New Locator endpoint supports TLS

Alexander Murmann created GEODE-3535: Summary: New Locator endpoint supports TLS Key: GEODE-3535 URL: https://issues.apache.org/jira/browse/GEODE-3535 Project: Geode Issue Type:

[jira] [Created] (GEODE-3537) New Locator endpoint does not respond to `echo` requests

Alexander Murmann created GEODE-3537: Summary: New Locator endpoint does not respond to `echo` requests Key: GEODE-3537 URL: https://issues.apache.org/jira/browse/GEODE-3537 Project: Geode

[jira] [Updated] (GEODE-3537) New Locator endpoint does not respond to `echo` requests

[ https://issues.apache.org/jira/browse/GEODE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3537: - Component/s: client/server > New Locator endpoint does not respond to `echo` requests >

[jira] [Created] (GEODE-3532) New Locator endpoint responds to ListAllAvailableServers

Alexander Murmann created GEODE-3532: Summary: New Locator endpoint responds to ListAllAvailableServers Key: GEODE-3532 URL: https://issues.apache.org/jira/browse/GEODE-3532 Project: Geode

[jira] [Created] (GEODE-3533) Connections to new Locator endpoint get timed out after n seconds of inactivity

Alexander Murmann created GEODE-3533: Summary: Connections to new Locator endpoint get timed out after n seconds of inactivity Key: GEODE-3533 URL: https://issues.apache.org/jira/browse/GEODE-3533

[jira] [Created] (GEODE-3531) Locator accepts echo request on new endpoint

Alexander Murmann created GEODE-3531: Summary: Locator accepts echo request on new endpoint Key: GEODE-3531 URL: https://issues.apache.org/jira/browse/GEODE-3531 Project: Geode Issue

[jira] [Created] (GEODE-3536) New Locator endpoint exposes statistics

Alexander Murmann created GEODE-3536: Summary: New Locator endpoint exposes statistics Key: GEODE-3536 URL: https://issues.apache.org/jira/browse/GEODE-3536 Project: Geode Issue Type:

[jira] [Assigned] (GEODE-3078) NewClientServerConnection can run on a thread in AcceptorImpl's thread pool

[ https://issues.apache.org/jira/browse/GEODE-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3078: Assignee: Alexander Murmann > NewClientServerConnection can run on a thread in

[jira] [Resolved] (GEODE-3514) Clean up locator code related new protocol

[ https://issues.apache.org/jira/browse/GEODE-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann resolved GEODE-3514. -- Resolution: Fixed > Clean up locator code related new protocol >

[jira] [Assigned] (GEODE-3078) NewClientServerConnection can run on a thread in AcceptorImpl's thread pool

[ https://issues.apache.org/jira/browse/GEODE-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3078: Assignee: (was: Alexander Murmann) > NewClientServerConnection can run on a

[jira] [Commented] (GEODE-3561) GetAllServers should return public IPs

[ https://issues.apache.org/jira/browse/GEODE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157381#comment-16157381 ] Alexander Murmann commented on GEODE-3561: -- Here is the script that's being used on AWS to start

[jira] [Created] (GEODE-3610) RoundTripCacheConnectionTest should not use test name to run with SSL

Alexander Murmann created GEODE-3610: Summary: RoundTripCacheConnectionTest should not use test name to run with SSL Key: GEODE-3610 URL: https://issues.apache.org/jira/browse/GEODE-3610 Project:

[jira] [Created] (GEODE-3603) Refactor exception handling in ProtoBuf operation handlers

Alexander Murmann created GEODE-3603: Summary: Refactor exception handling in ProtoBuf operation handlers Key: GEODE-3603 URL: https://issues.apache.org/jira/browse/GEODE-3603 Project: Geode

[jira] [Created] (GEODE-3514) Clean up locator code related new protocol

Alexander Murmann created GEODE-3514: Summary: Clean up locator code related new protocol Key: GEODE-3514 URL: https://issues.apache.org/jira/browse/GEODE-3514 Project: Geode Issue Type:

[jira] [Updated] (GEODE-3518) Refactor ServerLocator

[ https://issues.apache.org/jira/browse/GEODE-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3518: - Description: The `ServerLocator` currently knows how to use the transport layer as well

[jira] [Updated] (GEODE-3518) Refactor ServerLocator

[ https://issues.apache.org/jira/browse/GEODE-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3518: - Component/s: client/server > Refactor ServerLocator > -- > >

[jira] [Updated] (GEODE-4784) Categorize Security tests

[ https://issues.apache.org/jira/browse/GEODE-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4784: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize Security tests

[jira] [Updated] (GEODE-4780) Categorize CQ tests

[ https://issues.apache.org/jira/browse/GEODE-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4780: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize CQ tests >

[jira] [Updated] (GEODE-4779) Categorize OQL Query and Index Tests

[ https://issues.apache.org/jira/browse/GEODE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4779: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize OQL Query and

[jira] [Updated] (GEODE-4783) Categorize Management tests

[ https://issues.apache.org/jira/browse/GEODE-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4783: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize Management

[jira] [Updated] (GEODE-4813) Categorize register interest tests

[ https://issues.apache.org/jira/browse/GEODE-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4813: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize register

[jira] [Assigned] (GEODE-5201) Categorize all DUnit and integration tests by component

[ https://issues.apache.org/jira/browse/GEODE-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-5201: Assignee: Alexander Murmann > Categorize all DUnit and integration tests by

[jira] [Updated] (GEODE-4814) Categorize FunctionService Tests

[ https://issues.apache.org/jira/browse/GEODE-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4814: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize FunctionService

[jira] [Updated] (GEODE-4940) Categorize REST admin tests

[ https://issues.apache.org/jira/browse/GEODE-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4940: - Issue Type: Sub-task (was: Task) Parent: GEODE-5201 > Categorize REST admin

[jira] [Updated] (GEODE-5297) When command tries to execute a function on a group of members, if one member's function execution failed, we should consider the command failed.

[ https://issues.apache.org/jira/browse/GEODE-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5297: - Labels: geode2 (was: ) > When command tries to execute a function on a group of

[jira] [Commented] (GEODE-5297) When command tries to execute a function on a group of members, if one member's function execution failed, we should consider the command failed.

[ https://issues.apache.org/jira/browse/GEODE-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505191#comment-16505191 ] Alexander Murmann commented on GEODE-5297: -- While this sound like a good change, it seems to me

[jira] [Comment Edited] (GEODE-5297) When command tries to execute a function on a group of members, if one member's function execution failed, we should consider the command failed.

[ https://issues.apache.org/jira/browse/GEODE-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505191#comment-16505191 ] Alexander Murmann edited comment on GEODE-5297 at 6/7/18 8:11 PM: -- While

[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511768#comment-16511768 ] Alexander Murmann commented on GEODE-4647: -- I am curious why this is considered a bug fix. >

[jira] [Commented] (GEODE-5138) rename a stats for gateway sender with meaningful name

[ https://issues.apache.org/jira/browse/GEODE-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511777#comment-16511777 ] Alexander Murmann commented on GEODE-5138: -- [~zhouxj] This stat was originally introduced in

[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry

[ https://issues.apache.org/jira/browse/GEODE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511859#comment-16511859 ] Alexander Murmann commented on GEODE-4957: -- [~dschneider] This shows up as closed, however when

[jira] [Updated] (GEODE-5371) Ensure all tests marked as Flaky have not been resolved and still are accurately tagged

[ https://issues.apache.org/jira/browse/GEODE-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5371: - Labels: swat (was: ) > Ensure all tests marked as Flaky have not been resolved and

[jira] [Created] (GEODE-5371) Ensure all tests marked as Flaky have not been resolved and still are accurately tagged

Alexander Murmann created GEODE-5371: Summary: Ensure all tests marked as Flaky have not been resolved and still are accurately tagged Key: GEODE-5371 URL: https://issues.apache.org/jira/browse/GEODE-5371

[jira] [Resolved] (GEODE-1719) CI Failure: com.gemstone.gemfire.security.PDXPostProcessorDUnitTest.testGfshCommand

[ https://issues.apache.org/jira/browse/GEODE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann resolved GEODE-1719. -- Resolution: Fixed > CI Failure: >

[jira] [Commented] (GEODE-1719) CI Failure: com.gemstone.gemfire.security.PDXPostProcessorDUnitTest.testGfshCommand

[ https://issues.apache.org/jira/browse/GEODE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530624#comment-16530624 ] Alexander Murmann commented on GEODE-1719: -- Looks like the most recent failure was due to a

[jira] [Updated] (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 ] Alexander Murmann updated GEODE-5370: - Labels: ci concourse flaky (was: ) > DistributedTest task on CI occasionally exceeds

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

Alexander Murmann created GEODE-5370: Summary: DistributedTest task on CI occasionally exceeds timeout Key: GEODE-5370 URL: https://issues.apache.org/jira/browse/GEODE-5370 Project: Geode

[jira] [Reopened] (GEODE-1719) CI Failure: com.gemstone.gemfire.security.PDXPostProcessorDUnitTest.testGfshCommand

[ https://issues.apache.org/jira/browse/GEODE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reopened GEODE-1719: -- Assignee: Alexander Murmann > CI Failure: >

[jira] [Commented] (GEODE-1719) CI Failure: com.gemstone.gemfire.security.PDXPostProcessorDUnitTest.testGfshCommand

[ https://issues.apache.org/jira/browse/GEODE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528947#comment-16528947 ] Alexander Murmann commented on GEODE-1719: -- This happened again two weeks ago: 

[jira] [Commented] (GEODE-5288) Execute function on region should not iterate through all the servers hosting the region.

[ https://issues.apache.org/jira/browse/GEODE-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528945#comment-16528945 ] Alexander Murmann commented on GEODE-5288: -- Looks like a fix has been merged. Can we close this?

[jira] [Assigned] (GEODE-1719) CI Failure: com.gemstone.gemfire.security.PDXPostProcessorDUnitTest.testGfshCommand

[ https://issues.apache.org/jira/browse/GEODE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-1719: Assignee: (was: Alexander Murmann) > CI Failure: >

[jira] [Updated] (GEODE-5369) CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest

[ https://issues.apache.org/jira/browse/GEODE-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5369: - Labels: ci flaky (was: ) > CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest >

[jira] [Created] (GEODE-5369) CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest

Alexander Murmann created GEODE-5369: Summary: CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest Key: GEODE-5369 URL: https://issues.apache.org/jira/browse/GEODE-5369 Project: Geode

[jira] [Updated] (GEODE-1719) CI Failure: com.gemstone.gemfire.security.PDXPostProcessorDUnitTest.testGfshCommand

[ https://issues.apache.org/jira/browse/GEODE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-1719: - Labels: CI Flaky swat (was: CI Flaky) > CI Failure: >

[jira] [Updated] (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 ] Alexander Murmann updated GEODE-5370: - Labels: ci concourse flaky swat (was: ci concourse flaky) > DistributedTest task on CI

[jira] [Updated] (GEODE-5369) CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest

[ https://issues.apache.org/jira/browse/GEODE-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5369: - Labels: ci flaky swat (was: ci flaky) > CI Failure:

[jira] [Commented] (GEODE-4308) Should be able to create two caches in the same JVM

[ https://issues.apache.org/jira/browse/GEODE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347655#comment-16347655 ] Alexander Murmann commented on GEODE-4308: -- Many of the issues we will run into making it

[jira] [Updated] (GEODE-2685) request that ParitionedRegion getStatistics be a supported operation

[ https://issues.apache.org/jira/browse/GEODE-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-2685: - Labels: starter storage_2 (was: storage_2) > request that ParitionedRegion getStatistics

[jira] [Updated] (GEODE-3137) Replace all time values internally with std::chrono types

[ https://issues.apache.org/jira/browse/GEODE-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3137: - Labels: starter (was: ) > Replace all time values internally with std::chrono types >

[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file

[ https://issues.apache.org/jira/browse/GEODE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-1383: - Labels: LogBanner starter (was: LogBanner) > Please add gemfire,heap, xml configuration

[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file

[ https://issues.apache.org/jira/browse/GEODE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-1383: - Description: We often have situations where we have difficulty establishing the

[jira] [Updated] (GEODE-3835) DistributedSystemBridgeJUnitTest should use TemporaryFolder

[ https://issues.apache.org/jira/browse/GEODE-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3835: - Labels: starter (was: ) > DistributedSystemBridgeJUnitTest should use TemporaryFolder >

[jira] [Updated] (GEODE-3137) Replace all time values internally with std::chrono types

[ https://issues.apache.org/jira/browse/GEODE-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3137: - Labels: (was: starter) > Replace all time values internally with std::chrono types >

[jira] [Updated] (GEODE-4658) Expose how much time it takes to write to disk and what is the disk store size

[ https://issues.apache.org/jira/browse/GEODE-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4658: - Labels: Starter (was: ) > Expose how much time it takes to write to disk and what is the

[jira] [Updated] (GEODE-2727) optimize new 1.8 ConcurrentMap default methods on Region

[ https://issues.apache.org/jira/browse/GEODE-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-2727: - Labels: Starter region_interface storage_2 (was: region_interface storage_2) > optimize

[jira] [Updated] (GEODE-2727) optimize new 1.8 ConcurrentMap default methods on Region

[ https://issues.apache.org/jira/browse/GEODE-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-2727: - Description: In JDK 1.8 ConcurrentMap added the following default methods to the

[jira] [Updated] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate

[ https://issues.apache.org/jira/browse/GEODE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-4887: - Labels: swat (was: ) > ci Failure:

[jira] [Commented] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate

[ https://issues.apache.org/jira/browse/GEODE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558695#comment-16558695 ] Alexander Murmann commented on GEODE-4887: -- Ran into this again when running tests against my

[jira] [Updated] (GEODE-5479) Fix sloppy getRandomAvailableTCPPort() usage

[ https://issues.apache.org/jira/browse/GEODE-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5479: - Priority: Minor (was: Major) > Fix sloppy getRandomAvailableTCPPort() usage >

[jira] [Assigned] (GEODE-5479) Fix sloppy getRandomAvailableTCPPort() usage

[ https://issues.apache.org/jira/browse/GEODE-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-5479: Assignee: Alexander Murmann > Fix sloppy getRandomAvailableTCPPort() usage >

[jira] [Created] (GEODE-5479) Fix sloppy getRandomAvailableTCPPort() usage

Alexander Murmann created GEODE-5479: Summary: Fix sloppy getRandomAvailableTCPPort() usage Key: GEODE-5479 URL: https://issues.apache.org/jira/browse/GEODE-5479 Project: Geode Issue

[jira] [Updated] (GEODE-5433) Certain indexes are not properly updated during gii with stale persistent data

[ https://issues.apache.org/jira/browse/GEODE-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5433: - Fix Version/s: 1.7.0 > Certain indexes are not properly updated during gii with stale

[jira] [Commented] (GEODE-5433) Certain indexes are not properly updated during gii with stale persistent data

[ https://issues.apache.org/jira/browse/GEODE-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594249#comment-16594249 ] Alexander Murmann commented on GEODE-5433: -- [~huynhja] Since we are having a discussion on the

[jira] [Updated] (GEODE-5402) Disk recovery sometimes hangs when no member is recognized as having the most recent data

[ https://issues.apache.org/jira/browse/GEODE-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5402: - Fix Version/s: 1.7.0 > Disk recovery sometimes hangs when no member is recognized as

[jira] [Commented] (GEODE-5359) Infinite loop when a thread is interrupting during messaging

[ https://issues.apache.org/jira/browse/GEODE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594255#comment-16594255 ] Alexander Murmann commented on GEODE-5359: -- [~upthewaterspout] Since we are having a discussion

[jira] [Commented] (GEODE-5402) Disk recovery sometimes hangs when no member is recognized as having the most recent data

[ https://issues.apache.org/jira/browse/GEODE-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594253#comment-16594253 ] Alexander Murmann commented on GEODE-5402: -- [~lgallinat] Since we are having a discussion on the

[jira] [Updated] (GEODE-5359) Infinite loop when a thread is interrupting during messaging

[ https://issues.apache.org/jira/browse/GEODE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5359: - Fix Version/s: 1.7.0 > Infinite loop when a thread is interrupting during messaging >

[jira] [Updated] (GEODE-5472) PersistentPartitionedRegionRegressionTest recoversAfterBucketCreationCrashes hangs

[ https://issues.apache.org/jira/browse/GEODE-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5472: - Fix Version/s: 1.7.0 > PersistentPartitionedRegionRegressionTest

[jira] [Commented] (GEODE-5472) PersistentPartitionedRegionRegressionTest recoversAfterBucketCreationCrashes hangs

[ https://issues.apache.org/jira/browse/GEODE-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594243#comment-16594243 ] Alexander Murmann commented on GEODE-5472: -- [~jinmeiliao] Since we are ramping up for 1.7

[jira] [Assigned] (GEODE-517) multi-tenant memcached server

[ https://issues.apache.org/jira/browse/GEODE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-517: --- Assignee: (was: Alyssa Kim) > multi-tenant memcached server >

[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands

[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607688#comment-16607688 ] Alexander Murmann commented on GEODE-5070: -- [~sboorlagadda] This is reopened, but marked as 1.7.

[jira] [Commented] (GEODE-5374) CqResultSetUsingPoolDUnitTest.testCqResultsWithCompactRangeIndexOnPR failed and might have hung CI

[ https://issues.apache.org/jira/browse/GEODE-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534156#comment-16534156 ] Alexander Murmann commented on GEODE-5374: -- The current Concourse issue was due to filled up

[jira] [Updated] (GEODE-5374) CqResultSetUsingPoolDUnitTest.testCqResultsWithCompactRangeIndexOnPR failed and might have hung CI

[ https://issues.apache.org/jira/browse/GEODE-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5374: - Labels: swat (was: ) >

[jira] [Updated] (GEODE-5378) AcceptanceTests fail because they cannot start service db

[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5378: - Labels: swat (was: ) > AcceptanceTests fail because they cannot start service db >

[jira] [Created] (GEODE-5378) AcceptanceTests fail because they cannot start service db

Alexander Murmann created GEODE-5378: Summary: AcceptanceTests fail because they cannot start service db Key: GEODE-5378 URL: https://issues.apache.org/jira/browse/GEODE-5378 Project: Geode

[jira] [Updated] (GEODE-5378) AcceptanceTests fail because they cannot start service db

[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-5378: - Priority: Critical (was: Major) > AcceptanceTests fail because they cannot start

[jira] [Created] (GEODE-5374) CqResultSetUsingPoolDUnitTest.testCqResultsWithCompactRangeIndexOnPR failed and might have hung CI

Alexander Murmann created GEODE-5374: Summary: CqResultSetUsingPoolDUnitTest.testCqResultsWithCompactRangeIndexOnPR failed and might have hung CI Key: GEODE-5374 URL:

[jira] [Assigned] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles

[ https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3205: Assignee: Barbara Pruijn (was: Alexander Murmann) > CI failure: >

[jira] [Assigned] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles

[ https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-3205: Assignee: Alexander Murmann > CI failure: >

[jira] [Updated] (GEODE-3911) Authentication failures produce exception stacktraces in log files.

[ https://issues.apache.org/jira/browse/GEODE-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3911: - Labels: starter (was: newbie) > Authentication failures produce exception stacktraces in

[jira] [Updated] (GEODE-3456) "null" node showing up in Pulse UI

[ https://issues.apache.org/jira/browse/GEODE-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3456: - Labels: starter (was: newbie) > "null" node showing up in Pulse UI >

[jira] [Updated] (GEODE-3183) Pulse shows more members than in the cluster

[ https://issues.apache.org/jira/browse/GEODE-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-3183: - Labels: starter (was: newbie) > Pulse shows more members than in the cluster >

  1   2   3   4   5   6   7   8   9   >