Hi Charlie, Thank you very much. This is perfectly matching my scenario. I will give this a try and let you know how things come along. Thanks again for the help.
Marcus On Fri, Oct 19, 2018 at 12:02 PM Charlie Black <[email protected]> wrote: > I made a video a while back in an effort to show how Geode handles this > use case. I walk through: > > - Starting up geode with 3 locators 4 servers > - Create a region > - Load some data with spring boot > - kill -9 a data node > - See what happens > - restart the down node > - rebalance the load > - See what happens > > > It might be worth it to check out the video: > https://www.youtube.com/watch?v=yachT1xoQww > > Charlie > > On Fri, Oct 19, 2018 at 8:38 AM Marcus Dushshantha Chandradasa < > [email protected]> wrote: > >> Thanks, Juan for the response. >> >> I am starting the servers as follows. >> >> gfsh> start server --name=server1 --server-port=40411 >> --locators='10.0.75.1[10334], 10.0.75.1[10335]' >> >> I see the below warning in the log for the server >> >> [warning 2018/10/19 11:33:10.972 EDT server1 <main> tid=0x1] Unknown >> locator host: 10.0.75.1 >> >> I, then shut down the Locator1 and connected to locator2 from gfsh. >> Trying to see whether * I can run a query but, It does not return any. * >> >> >> *Marcus* >> >> On Fri, Oct 19, 2018 at 10:26 AM Juan José Ramos <[email protected]> >> wrote: >> >>> Hello Marcus!. >>> >>> You need to make sure that all members of the cluster have the same list >>> of locators configured, so if any of the configured locators is brought >>> down then every member will still know which other locators to use [1]. >>> Regarding the PULSE web application, it's internally deployed within the >>> locator itself [2], so you'll need to access the app on the second locator >>> after bringing down the first one. As an example, if both your locators are >>> configured to use the default http port (7070), and assuming that they are >>> accessible through the hostnames *locator1* and *locator2*, after >>> stopping the first locator you'll need to access PULSE through >>> *http://locator2:7070/pulse >>> <http://locator2:7070/pulse>*. >>> Hope I didn't miss anything. >>> Best regards. >>> >>> [1]: >>> https://geode.apache.org/docs/guide/17/configuring/running/running_the_locator.html >>> [2]: >>> https://geode.apache.org/docs/guide/17/tools_modules/pulse/pulse-embedded.html >>> >>> >>> On Fri, Oct 19, 2018 at 3:15 PM Marcus Dushshantha Chandradasa < >>> [email protected]> wrote: >>> >>>> Hi All, >>>> >>>> I am trying to use Geode for one of my projects and I am trying to find >>>> out how to run multiple Locators clustered together so If one locator >>>> fails, another will take over. I believe this possible, but I cant seem to >>>> figure out how to do it. I created 2 locators. First one being the main >>>> locator. Then I started the 2nd one with the option >>>> --locators='locator1[<port>]' >>>> >>>> I can see the 2nd locator in the cluster diagram on Pulse but when I >>>> kill the first locator, the whole cluster dies. Am I doing something wrong? >>>> Any help would be appreciated. >>>> >>>> Thanks >>>> Marcus >>>> >>> >>> >>> -- >>> Juan José Ramos Cassella >>> Senior Technical Support Engineer >>> Email: [email protected] >>> Office#: +353 21 4238611 <+353%2021%20423%208611> >>> Mobile#: +353 87 2074066 <+353%2087%20207%204066> >>> After Hours Contact#: +1 877 477 2269 <(877)%20477-2269> >>> Office Hours: Mon - Thu 08:30 - 17:00 GMT. Fri 08:30 - 16:00 GMT >>> How to upload artifacts: >>> https://support.pivotal.io/hc/en-us/articles/204369073 >>> How to escalate a ticket: >>> https://support.pivotal.io/hc/en-us/articles/203809556 >>> >>> [image: support] <https://support.pivotal.io/> [image: twitter] >>> <https://twitter.com/pivotal> [image: linkedin] >>> <https://www.linkedin.com/company/3048967> [image: facebook] >>> <https://www.facebook.com/pivotalsoftware> [image: google plus] >>> <https://plus.google.com/+Pivotal> [image: youtube] >>> <https://www.youtube.com/playlist?list=PLAdzTan_eSPScpj2J50ErtzR9ANSzv3kl> >>> >> -- > [email protected] | +1.858.480.9722 > Principal Realtime Data Engineer >
