You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by Vinay Upadhya <vu...@pivotal.io> on 2015/10/01 23:10:55 UTC
Set maximum connections per client on the geode server side
Hello,
We have the max-connections property on the cache-server tag on a geode server which limits the incoming connections to that number. Is there a way however to assign a certain number of maximum connections per client connecting to a node?
Vinay Upadhya | Sr. Field Engineer
917-514-1842 | vupadhya@pivotal.io <ma...@pivotal.io> | Pivotal Software Inc. <http://www.pivotal.io/>
Re: Set maximum connections per client on the geode server side
Posted by Vincent Ford <vf...@pivotal.io>.
You can probably do what you want via the security API's but it is a bit
messy and more complicated. One alternative is to use server groups which a
client then must also configure to direct traffic/connections to specific
servers but also doesn't limit the number of connections a client can make
to any given server. A third external option is probably to use something
like iptables to prevent the connections in the first place but this can
be a pain to configure and inflexible for a cluster setup.
*Vince Ford*
GemFire Sustenance Engineering
Beaverton, OR USA
503-533-3726 (office)
http://www.pivotal.io
Open Source Project Geode https://geode.incubator.apache.org/
<https://network.pivotal.io/products/project-geode>
On Thu, Oct 1, 2015 at 2:34 PM, Vinay Upadhya <vu...@pivotal.io> wrote:
> Thanks Darrel. My question is more about trying to limit it from the
> server side in an attempt to stop rogue clients outside the jurisdiction of
> the Gemfire server owners.
>
> *Vinay Upadhya *| Sr. Field Engineer
>
> 917-514-1842 | vupadhya@pivotal.io | Pivotal Software Inc.
> <http://www.pivotal.io/>
>
> On Oct 1, 2015, at 5:29 PM, Darrel Schneider <ds...@pivotal.io>
> wrote:
>
> You can do this on the client side. It is part of the client pool
> configuration.
> We have a number of ways to configure this pool. You can do it with
> cache.xml or apis. You can probably do it with Spring.
>
> If you are using the ClientCacheFactory API then you would do it
> with com.gemstone.gemfire.cache.client.ClientCacheFactory.setPoolMaxConnections(int)
>
> Hope this answers your question.
>
>
> On Thu, Oct 1, 2015 at 2:10 PM, Vinay Upadhya <vu...@pivotal.io> wrote:
>
>> Hello,
>>
>> We have the max-connections property on the cache-server tag on a geode
>> server which limits the incoming connections to that number. Is there a way
>> however to assign a certain number of maximum connections per client
>> connecting to a node?
>>
>> *Vinay Upadhya *| Sr. Field Engineer
>>
>> 917-514-1842 | vupadhya@pivotal.io | Pivotal Software Inc.
>> <http://www.pivotal.io/>
>>
>>
>
>
Re: Set maximum connections per client on the geode server side
Posted by Vinay Upadhya <vu...@pivotal.io>.
Thanks Darrel. My question is more about trying to limit it from the server side in an attempt to stop rogue clients outside the jurisdiction of the Gemfire server owners.
Vinay Upadhya | Sr. Field Engineer
917-514-1842 | vupadhya@pivotal.io <ma...@pivotal.io> | Pivotal Software Inc. <http://www.pivotal.io/>
> On Oct 1, 2015, at 5:29 PM, Darrel Schneider <ds...@pivotal.io> wrote:
>
> You can do this on the client side. It is part of the client pool configuration.
> We have a number of ways to configure this pool. You can do it with cache.xml or apis. You can probably do it with Spring.
>
> If you are using the ClientCacheFactory API then you would do it with com.gemstone.gemfire.cache.client.ClientCacheFactory.setPoolMaxConnections(int)
>
> Hope this answers your question.
>
>
> On Thu, Oct 1, 2015 at 2:10 PM, Vinay Upadhya <vupadhya@pivotal.io <ma...@pivotal.io>> wrote:
> Hello,
>
> We have the max-connections property on the cache-server tag on a geode server which limits the incoming connections to that number. Is there a way however to assign a certain number of maximum connections per client connecting to a node?
> Vinay Upadhya | Sr. Field Engineer
>
> 917-514-1842 <tel:917-514-1842> | vupadhya@pivotal.io <ma...@pivotal.io> | Pivotal Software Inc. <http://www.pivotal.io/>
>
Re: Set maximum connections per client on the geode server side
Posted by Darrel Schneider <ds...@pivotal.io>.
You can do this on the client side. It is part of the client pool
configuration.
We have a number of ways to configure this pool. You can do it with
cache.xml or apis. You can probably do it with Spring.
If you are using the ClientCacheFactory API then you would do it
with com.gemstone.gemfire.cache.client.ClientCacheFactory.setPoolMaxConnections(int)
Hope this answers your question.
On Thu, Oct 1, 2015 at 2:10 PM, Vinay Upadhya <vu...@pivotal.io> wrote:
> Hello,
>
> We have the max-connections property on the cache-server tag on a geode
> server which limits the incoming connections to that number. Is there a way
> however to assign a certain number of maximum connections per client
> connecting to a node?
>
> *Vinay Upadhya *| Sr. Field Engineer
>
> 917-514-1842 | vupadhya@pivotal.io | Pivotal Software Inc.
> <http://www.pivotal.io/>
>
>