[
https://issues.apache.org/jira/browse/GEODE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293653#comment-15293653
]
ASF subversion and git services commented on GEODE-1102:
--------------------------------------------------------
Commit 8266f6b9b944adddeea449743f8da611f76d9852 in incubator-geode's branch
refs/heads/feature/GEODE-835-test from zhouxh
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8266f6b ]
GEODE-1344: fix the testcase to remove the durable client part
The test case for durable client with 2 cache servers on the same JVM is not
mature. Since we did not change any logic in durable client, remove the test
code for now. This senario will be followed up in GEODE-1102.
> Refactor API related with client-subscription and cache-server
> --------------------------------------------------------------
>
> Key: GEODE-1102
> URL: https://issues.apache.org/jira/browse/GEODE-1102
> Project: Geode
> Issue Type: New Feature
> Components: client queues
> Reporter: xiaojian zhou
>
> Currently, client-subscription belongs to cache-server.
> client-subscription defines the overflow attributes for the HAContainer.
> We allow to create multiple cache servers and each gateway receiver will
> create a cache server.
> CacheClientNotifier and HAContainer are singletons.
> Above design caused the client-subscription definition in first cache-server
> (including gateway receiver's) will override that in other cache-servers.
> Since HAContainer is better to be kept as singleton for better performance,
> the CacheClientNotifier should be moved to cache level. And disallow creating
> multiple cache-servers explicitly (it does not make sense to customers)
> On the other hand, CacheClientNotifier should not be a singleton. It can be
> an instance object of AcceptorImpl and will not keep the client-subscription
> definition for HAContainer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
