[
https://issues.apache.org/jira/browse/GEODE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705480#comment-16705480
]
ASF subversion and git services commented on GEODE-6121:
--------------------------------------------------------
Commit 3aa2a894802c50db276d9c87f00432cd1908291d in geode's branch
refs/heads/feature/GEODE-6121 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3aa2a89 ]
GEODE-6121 Port SnappyData DirectChannel comms changes to Geode
Not ready for review!
Initial port of SnappyData peer-to-peer communication changes to Geode.
See
https://github.com/SnappyDataInc/snappy-store/commit/49222766a35c99f4853b7b6661457f37b3c39349
The current changes have connection-streaming and conserve-sockets=false
as the default for testing but I will be changing this. The
connection-streaming
feature will be an opt-in thing at first and probably be marked experimental.
> Port SnappyData DirectChannel comms changes to Geode
> ----------------------------------------------------
>
> Key: GEODE-6121
> URL: https://issues.apache.org/jira/browse/GEODE-6121
> Project: Geode
> Issue Type: New Feature
> Components: membership
> Reporter: Bruce Schuchardt
> Priority: Major
>
> SnappyData is using an old snapshot of pre-Geode GemFire for one of its data
> stores. They have implemented connection pooling to eliminate the
> connection-explosion problem we have with conserve-sockets=false (which
> pretty much everyone uses). We should port those changes to Geode and
> evaluate their effectiveness.
> https://github.com/SnappyDataInc/snappy-store/commit/49222766a35c99f4853b7b6661457f37b3c39349
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
