[jira] [Updated] (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:all-tabpanel ] ASF GitHub Bot updated GEODE-4647: -- Labels: pull-request-available (was: ) > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4401) Add a CloseConnection protobuf message
[ https://issues.apache.org/jira/browse/GEODE-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385736#comment-16385736 ] ASF subversion and git services commented on GEODE-4401: Commit b9d9b38e42686a1973cee51f89053eb8b2519ec4 in geode's branch refs/heads/feature/GEODE-4647 from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9d9b38 ] GEODE-4401: Add disconnect client message to server and driver. (#1525) * GEODE-4401: Add disconnect client message to server and driver. * GEODE-4401: Address review comments. * GEODE-4401: Update the driver to use the channel instead of a socket. > Add a CloseConnection protobuf message > -- > > Key: GEODE-4401 > URL: https://issues.apache.org/jira/browse/GEODE-4401 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h > Remaining Estimate: 0h > > The current API has no way for the client to inform a server of its intent to > close its connection. The server is left thinking the client crashed. It > would be nice to have a graceful shutdown message & have the server log > something if the client abnormally closes the connection without sending a > Close message. > See also GEODE-4300 where we added supression of log messages when client > connections are found to be closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=16385742#comment-16385742 ] ASF subversion and git services commented on GEODE-4647: Commit 140c83e006ba8b604a2c2df0f6e7502260e03ab9 in geode's branch refs/heads/feature/GEODE-4647 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=140c83e ] GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary gateway sender queue > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: xiaojian zhou >Priority: Major > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4672) Geode fails to start with JDK 9 if validate-serializable-objects is set
[
https://issues.apache.org/jira/browse/GEODE-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385733#comment-16385733
]
ASF subversion and git services commented on GEODE-4672:
Commit 94ded7f3561a9ec4848843e3841d593fcd4d77d9 in geode's branch
refs/heads/feature/GEODE-4647 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=94ded7f ]
GEODE-4672 Geode fails to start with JDK 9 if validate-serializable-objects is
set
The ObjectInputFilter wrapper now uses reflection and a dynamic
proxy to interact with the serialization filter classes. A dynamic
proxy is needed since we have to implement a method specified in
a class whose package has changed in the JDK. The logic of the filter
has not been changed.
I also replaced a couple of recently added white-list wildcards with specific
classes and added a javadoc for the whitelist in InternalDataSerializer.
I opened a new JIRA ticket concerning another wildcard that was recently
added for the JDBC connector and left a TODO in place for this.
This closes #1526
> Geode fails to start with JDK 9 if validate-serializable-objects is set
>
>
> Key: GEODE-4672
> URL: https://issues.apache.org/jira/browse/GEODE-4672
> Project: Geode
> Issue Type: Sub-task
> Components: serialization
>Reporter: Dan Smith
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> If the validate-serializable-objects property is set, Geode fails to start
> with the below exception. This is problematic for running the geode tests
> with JDK 9 because our tests set this property
> {noformat}
> java.lang.RuntimeException: Unable to launch dunit VMs
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:162)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.initializeDistributedTestCase(JUnit4DistributedTestCase.java:128)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.RuntimeException: Failed to start locator
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.startLocator(DUnitLauncher.java:331)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.launch(DUnitLauncher.java:241)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:160)
> ... 15 more
> Caused by: org.apache.geode.GemFireConfigException: A serialization filter
> has been specified but this version of Java does not support serialization
> filters - sun.misc.ObjectInputFilter is not available
> at
> org.apache.geode.internal.InternalDataSerializer.initialize(InternalDataSerializer.java:235)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:691)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:320)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:634)
> at
>
[jira] [Commented] (GEODE-4401) Add a CloseConnection protobuf message
[ https://issues.apache.org/jira/browse/GEODE-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385734#comment-16385734 ] ASF subversion and git services commented on GEODE-4401: Commit b9d9b38e42686a1973cee51f89053eb8b2519ec4 in geode's branch refs/heads/feature/GEODE-4647 from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9d9b38 ] GEODE-4401: Add disconnect client message to server and driver. (#1525) * GEODE-4401: Add disconnect client message to server and driver. * GEODE-4401: Address review comments. * GEODE-4401: Update the driver to use the channel instead of a socket. > Add a CloseConnection protobuf message > -- > > Key: GEODE-4401 > URL: https://issues.apache.org/jira/browse/GEODE-4401 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h > Remaining Estimate: 0h > > The current API has no way for the client to inform a server of its intent to > close its connection. The server is left thinking the client crashed. It > would be nice to have a graceful shutdown message & have the server log > something if the client abnormally closes the connection without sending a > Close message. > See also GEODE-4300 where we added supression of log messages when client > connections are found to be closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4661) Protobuf: add GetAllKeys message
[ https://issues.apache.org/jira/browse/GEODE-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385731#comment-16385731 ] ASF subversion and git services commented on GEODE-4661: Commit 808d273294d6b7e7723c111204df6be7009cb2b8 in geode's branch refs/heads/feature/GEODE-4647 from [~WireBaron] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=808d273 ] GEODE-4661: Implement KeySet protobuf message and handler (#1538) > Protobuf: add GetAllKeys message > > > Key: GEODE-4661 > URL: https://issues.apache.org/jira/browse/GEODE-4661 > Project: Geode > Issue Type: New Feature > Components: client/server >Reporter: Brian Baynes >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1h > Remaining Estimate: 0h > > As a dev using the new protocol, I need to be able to get all keys from a > region. > Add GetAllKeys message, returning collection of all keys for named region and > an error if the region does not exist. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4401) Add a CloseConnection protobuf message
[ https://issues.apache.org/jira/browse/GEODE-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385735#comment-16385735 ] ASF subversion and git services commented on GEODE-4401: Commit b9d9b38e42686a1973cee51f89053eb8b2519ec4 in geode's branch refs/heads/feature/GEODE-4647 from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9d9b38 ] GEODE-4401: Add disconnect client message to server and driver. (#1525) * GEODE-4401: Add disconnect client message to server and driver. * GEODE-4401: Address review comments. * GEODE-4401: Update the driver to use the channel instead of a socket. > Add a CloseConnection protobuf message > -- > > Key: GEODE-4401 > URL: https://issues.apache.org/jira/browse/GEODE-4401 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h > Remaining Estimate: 0h > > The current API has no way for the client to inform a server of its intent to > close its connection. The server is left thinking the client crashed. It > would be nice to have a graceful shutdown message & have the server log > something if the client abnormally closes the connection without sending a > Close message. > See also GEODE-4300 where we added supression of log messages when client > connections are found to be closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3465) GetServerRequest on Locator accepts group
[ https://issues.apache.org/jira/browse/GEODE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385738#comment-16385738 ] ASF subversion and git services commented on GEODE-3465: Commit 5380ed5998ebe7ef6dea7c4a6c15d8f878f951b9 in geode's branch refs/heads/feature/GEODE-4647 from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5380ed5 ] GEODE-3465: Enhance error message and add tests for when group is specified. (#1527) > GetServerRequest on Locator accepts group > - > > Key: GEODE-3465 > URL: https://issues.apache.org/jira/browse/GEODE-3465 > Project: Geode > Issue Type: New Feature > Components: client/server >Reporter: Alexander Murmann >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The user should be able to specify a group for which they want to receive a > server from the locator. > Acceptance Criteria: > When making a ProtoBuf request to the locator I can pass a group to the > available server method, receiving back a server from that group or an error > if none exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385739#comment-16385739
]
ASF subversion and git services commented on GEODE-4721:
Commit 81ae44d3d70283753168ba27ce76daad47824ba2 in geode's branch
refs/heads/feature/GEODE-4647 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=81ae44d ]
GEODE-4721: Fix a case that client proxy region returns empty set if … (#1532)
* GEODE-4721: Fix a case that client proxy region returns empty set if it is a
first operation in the transaction.
Add additional test cases on set operation with JTA.
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385740#comment-16385740
]
ASF subversion and git services commented on GEODE-4721:
Commit 81ae44d3d70283753168ba27ce76daad47824ba2 in geode's branch
refs/heads/feature/GEODE-4647 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=81ae44d ]
GEODE-4721: Fix a case that client proxy region returns empty set if … (#1532)
* GEODE-4721: Fix a case that client proxy region returns empty set if it is a
first operation in the transaction.
Add additional test cases on set operation with JTA.
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4762) Code Cleanup: Remove dead code from o.a.g.admin, *.cache, and *.distributed.internal
[ https://issues.apache.org/jira/browse/GEODE-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385730#comment-16385730 ] ASF subversion and git services commented on GEODE-4762: Commit db63cf3264d132e44ab2dbf817daf59144861736 in geode's branch refs/heads/feature/GEODE-4647 from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=db63cf3 ] GEODE-4762: Remove dead code. > Code Cleanup: Remove dead code from o.a.g.admin, *.cache, and > *.distributed.internal > > > Key: GEODE-4762 > URL: https://issues.apache.org/jira/browse/GEODE-4762 > Project: Geode > Issue Type: Improvement >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4672) Geode fails to start with JDK 9 if validate-serializable-objects is set
[
https://issues.apache.org/jira/browse/GEODE-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385741#comment-16385741
]
ASF subversion and git services commented on GEODE-4672:
Commit a636cb0c23c82cfb85e9f410e009ef63ef1fa360 in geode's branch
refs/heads/feature/GEODE-4647 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a636cb0 ]
GEODE-4672 Geode fails to start with JDK 9 if validate-serializable-objects is
set
fixing a merge problem
> Geode fails to start with JDK 9 if validate-serializable-objects is set
>
>
> Key: GEODE-4672
> URL: https://issues.apache.org/jira/browse/GEODE-4672
> Project: Geode
> Issue Type: Sub-task
> Components: serialization
>Reporter: Dan Smith
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> If the validate-serializable-objects property is set, Geode fails to start
> with the below exception. This is problematic for running the geode tests
> with JDK 9 because our tests set this property
> {noformat}
> java.lang.RuntimeException: Unable to launch dunit VMs
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:162)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.initializeDistributedTestCase(JUnit4DistributedTestCase.java:128)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.RuntimeException: Failed to start locator
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.startLocator(DUnitLauncher.java:331)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.launch(DUnitLauncher.java:241)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:160)
> ... 15 more
> Caused by: org.apache.geode.GemFireConfigException: A serialization filter
> has been specified but this version of Java does not support serialization
> filters - sun.misc.ObjectInputFilter is not available
> at
> org.apache.geode.internal.InternalDataSerializer.initialize(InternalDataSerializer.java:235)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:691)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:320)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:634)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher$2.call(DUnitLauncher.java:320)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4401) Add a CloseConnection protobuf message
[ https://issues.apache.org/jira/browse/GEODE-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385737#comment-16385737 ] ASF subversion and git services commented on GEODE-4401: Commit b9d9b38e42686a1973cee51f89053eb8b2519ec4 in geode's branch refs/heads/feature/GEODE-4647 from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9d9b38 ] GEODE-4401: Add disconnect client message to server and driver. (#1525) * GEODE-4401: Add disconnect client message to server and driver. * GEODE-4401: Address review comments. * GEODE-4401: Update the driver to use the channel instead of a socket. > Add a CloseConnection protobuf message > -- > > Key: GEODE-4401 > URL: https://issues.apache.org/jira/browse/GEODE-4401 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h > Remaining Estimate: 0h > > The current API has no way for the client to inform a server of its intent to > close its connection. The server is left thinking the client crashed. It > would be nice to have a graceful shutdown message & have the server log > something if the client abnormally closes the connection without sending a > Close message. > See also GEODE-4300 where we added supression of log messages when client > connections are found to be closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4394) gfsh put command: change option --skip-if-exists to --if-not-exists
[ https://issues.apache.org/jira/browse/GEODE-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385732#comment-16385732 ] ASF subversion and git services commented on GEODE-4394: Commit c35aba207cd4876efb65bbf8607b34d3b1355669 in geode's branch refs/heads/feature/GEODE-4647 from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c35aba2 ] GEODE-4394 gfsh put command: change option --skip-if-exists to --if-not-exists (update user guide) > gfsh put command: change option --skip-if-exists to --if-not-exists > --- > > Key: GEODE-4394 > URL: https://issues.apache.org/jira/browse/GEODE-4394 > Project: Geode > Issue Type: Improvement > Components: docs, gfsh >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Change the gfsh put command `--skip-if-exists` option to `--if-not-exists` > for consistency with other gfsh commands, most notably create region (see > GEODE-4354). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
