You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by Michael Goltsman <Mi...@Amdocs.com> on 2017/05/28 08:31:25 UTC
Cache server port configuration
Hi All,
I need to understand how cache servers know each other ports. I have a collision between my application and cache server ports and cannot understand how to control it.
Best regards,
Michael Goltsman
Senior Technical Expert
+972.9.77.61366 (desk)
+972.9.77.61505 (fax)
[amdocs-a]
Did you know...?
Amdocs' new "Turbo Charging"<http://www.amdocs.com/Site/News/News+Articles/2008/Press+Releases/Turbo+Charging.htm> technology speeds real-time processing of hundreds of millions of events during peak hours over low-cost hardware (like blade servers), all with the comprehensive functionality of Amdocs CES - Billing
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: Cache server port configuration
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
Also, you can define the cache server port while starting the server from
gfsh like so:
gfsh>start server --name=serv1 --server-port=11211
On Sun, May 28, 2017 at 12:40 PM Mark Secrist <ms...@pivotal.io> wrote:
> Cache servers discover each other's ports via the locator. You can enable
> servers to know of the locator by the 'locators' property (--locators=host
> [port]).
>
> On May 28, 2017 2:31 AM, "Michael Goltsman" <Mi...@amdocs.com>
> wrote:
>
>> Hi All,
>>
>>
>>
>> I need to understand how cache servers know each other ports. I have a
>> collision between my application and cache server ports and cannot
>> understand how to control it.
>>
>>
>>
>> *Best regards,*
>>
>> *Michael Goltsman*
>> Senior Technical Expert
>> +972.9.77.61366 (desk)
>> +972.9.77.61505 (fax)
>>
>> [image: amdocs-a]
>>
>> *Did you know…?*
>> Amdocs’ new “Turbo Charging”
>> <http://www.amdocs.com/Site/News/News+Articles/2008/Press+Releases/Turbo+Charging.htm>
>> technology speeds real-time processing of hundreds of millions of events
>> during peak hours over low-cost hardware (like blade servers), all with the
>> comprehensive functionality of Amdocs CES – Billing
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement,
>> you may review at https://www.amdocs.com/about/email-disclaimer
>>
>
Re: Cache server port configuration
Posted by Mark Secrist <ms...@pivotal.io>.
Cache servers discover each other's ports via the locator. You can enable
servers to know of the locator by the 'locators' property (--locators=host
[port]).
On May 28, 2017 2:31 AM, "Michael Goltsman" <Mi...@amdocs.com> wrote:
> Hi All,
>
>
>
> I need to understand how cache servers know each other ports. I have a
> collision between my application and cache server ports and cannot
> understand how to control it.
>
>
>
> *Best regards,*
>
> *Michael Goltsman*
> Senior Technical Expert
> +972.9.77.61366 (desk)
> +972.9.77.61505 (fax)
>
> [image: amdocs-a]
>
> *Did you know…?*
> Amdocs’ new “Turbo Charging”
> <http://www.amdocs.com/Site/News/News+Articles/2008/Press+Releases/Turbo+Charging.htm>
> technology speeds real-time processing of hundreds of millions of events
> during peak hours over low-cost hardware (like blade servers), all with the
> comprehensive functionality of Amdocs CES – Billing
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
>