If you restart a node and join it with same hostname and port it will
automatically Down previous incarnation of that member.

On Tue, Nov 8, 2016 at 10:56 AM, Javier Ferrer González <
javier.mailse...@gmail.com> wrote:

> Hi Patrik, thanks for your response :)
>
> Do I need to send the down and join notifications even if the node to be
> deployed will have the very same IP and port after the deploy?
>
> I've take a look to the HTTP API and it looks awesome :D
> Quite interesting to see how you test all this orchestration between nodes
> and so on :)
>
> On Monday, November 7, 2016 at 6:13:38 PM UTC+1, Patrik Nordwall wrote:
>>
>>
>>
>> On Fri, Nov 4, 2016 at 11:53 AM, Javier Ferrer González <
>> javier.m...@gmail.com> wrote:
>>
>>> Hi Patrik,
>>>
>>> 2 doubts:
>>>
>>> 1. As far as I understood by the Akka Cluster documentation about
>>> downing
>>> <http://doc.akka.io/docs/akka/current/scala/cluster-usage.html#Downing>, and
>>> your comments, the recommended approach while dealing with that process
>>> would be something like:
>>>
>>>    - Download the akka distribution as you said from
>>>    http://akka.io/downloads/
>>>    - Copy and paste the `akka-cluster` bash script together with the
>>>    `jmxsh-R5.jar` on a `resources/bin/` folder (for instance)
>>>    - Include that folder on the distributed package (I've added the
>>>    following lines on the `build.sbt`):
>>>
>>>    mappings in Universal ++=
>>>    (baseDirectory.value / "resources" / "bin" * "*" get) map
>>>    (bin => bin -> ("bin/" + bin.getName))
>>>
>>>    - While deploying, set the node to be deployed as down manually
>>>    calling the bash script like:
>>>       - Execute `bin/akka-cluster %node_to_be_deployed:port% down`
>>>       - Deploy the new code version
>>>       - Execute `bin/akka-cluster %deployed_node:port% join`
>>>
>>> Is it correct?
>>>
>>
>> Sound good
>>
>>
>>>
>>> 2. Referring to:
>>>
>>>> I know there is a problem using it on AWS between remote nodes, but it
>>>> should work on the local node, i.e. run the script on the same host as one
>>>> of the cluster nodes.
>>>
>>>
>>> What kind of errors could I have working with the script on AWS?
>>>
>>
>> I'm not sure what the problems were. Perhaps firewall issues.
>>
>> Note that there is a http based management api in the works:
>> https://github.com/akka/akka-stream-contrib/pull/76
>>
>> /Patrik
>>
>>
>>>
>>> Thanks!
>>>
>>> On Thursday, April 23, 2015 at 1:18:26 PM UTC+2, Patrik Nordwall wrote:
>>>>
>>>>
>>>> On Tue, Apr 21, 2015 at 10:44 PM, Joseph Elliott <joe.e...@joulebug.com
>>>> > wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I've got an application that uses an Akka cluster v2.3.9 (we are
>>>>> running several servers at Amazon EC2) and recently the cluster has been
>>>>> behaving badly.  The nodes aren't reconnecting to each other when one of
>>>>> them goes down.  We are running the cluster to take advantage of the
>>>>> Singleton (basically we have a cron job we want to only run on one node)
>>>>> and so we aren't using autodowning.
>>>>>
>>>>> I'd like to get some visibility into what's going on, but I'm having
>>>>> trouble getting the script mentioned here to work:
>>>>> http://doc.akka.io/docs/akka/snapshot/java/cluster-usa
>>>>> ge.html#cluster-command-line-java
>>>>>
>>>>> I've downloaded the script from this page:
>>>>> https://github.com/akka/apps/tree/master/akka-cluster-testapp/bin,
>>>>> but I'm not even sure that's the right script since it wasn't linked from
>>>>> the documentation.
>>>>>
>>>>
>>>> It is in the distribution that can be downloaded here:
>>>> http://akka.io/downloads/
>>>>
>>>> I think the script that you grabbed is alright. It only needs
>>>> the jmxsh-R5.jar.
>>>>
>>>>
>>>>> My command line settings for the remote application are:
>>>>>
>>>>> -Dcom.sun.management.jmxremote
>>>>> -Dcom.sun.management.jmxremote.ssl=false
>>>>> -Dcom.sun.management.jmxremote.authenticate=false
>>>>> -Dcom.sun.management.jmxremote.port=9999
>>>>> -Dcom.sun.management.jmxremote.local.only=false
>>>>> -Djava.rmi.server.hostname=localhost
>>>>>
>>>>>
>>>> I used
>>>>
>>>> JMX_OPTS="-Dcom.sun.management.jmxremote.port=9999
>>>> -Dcom.sun.management.jmxremote.authenticate=false
>>>> -Dcom.sun.management.jmxremote.ssl=false"
>>>>
>>>>
>>>>> I copied the /bin folder with the script in it to the remote server
>>>>> and am trying to run the script from there (through SSH).  I keep
>>>>> getting this error message:
>>>>>
>>>>> >bin/akka-cluster localhost 9999 cluster-status
>>>>>
>>>>> Akka cluster node is not available on localhost, due to false
>>>>>
>>>>> Does anyone have experience using this script successfully?
>>>>>
>>>> I think it should be
>>>> bin/akka-cluster localhost:9999 cluster-status
>>>> Note the : between the hostname and port.
>>>> If that is the problem the documentation has a bug.
>>>>
>>>> I know there is a problem using it on AWS between remote nodes, but it
>>>> should work on the local node, i.e. run the script on the same host as one
>>>> of the cluster nodes.
>>>>
>>>> /Patrik
>>>>
>>>>
>>>>
>>>>> --
>>>>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/c
>>>>> urrent/additional/faq.html
>>>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou
>>>>> p/akka-user
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Akka User List" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to akka-user+...@googlegroups.com.
>>>>> To post to this group, send email to akka...@googlegroups.com.
>>>>> Visit this group at http://groups.google.com/group/akka-user.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Patrik Nordwall
>>>> Typesafe <http://typesafe.com/> -  Reactive apps on the JVM
>>>> Twitter: @patriknw
>>>>
>>>> --
>>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>>> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/c
>>> urrent/additional/faq.html
>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou
>>> p/akka-user
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Akka User List" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to akka-user+...@googlegroups.com.
>>> To post to this group, send email to akka...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/akka-user.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Patrik Nordwall
>> Akka Tech Lead
>> Lightbend <http://www.lightbend.com/> -  Reactive apps on the JVM
>> Twitter: @patriknw
>>
>> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> -  Reactive apps on the JVM
Twitter: @patriknw

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to