Sure. I have looked into it a bit. I'll paste my findings in the other
thread or rather in the JIRA itself
https://issues.apache.org/jira/browse/WHIRR-459.

Cheers,
Akash A

On Mon, Jan 9, 2012 at 4:54 PM, Andrei Savu <[email protected]> wrote:

> +1 It's a bit hard to replicate for me. Is this still happening for you?
> Can you take a look with Wireshark?
>
> -- Andrei Savu
>
> On Mon, Jan 9, 2012 at 1:20 PM, Akash Ashok <[email protected]>
> wrote:
>
> > Hi,
> >
> > I am kinda new here and not sure what the roadmap is but I feel this
> should
> > also be a part of 0.8.0  https://issues.apache.org/jira/browse/WHIRR-459.
> > When I first posted this on user list I heard that a lot of them actually
> > face this issue. I can't surely say what the issue is because of but if
> its
> > because of NAT configurations; but if it is then this would affect a
> large
> > number of users.
> >
> > What do u think ?
> >
> > Cheers,
> > Akash A
> >
> > On Mon, Jan 9, 2012 at 4:18 PM, Andrei Savu <[email protected]>
> wrote:
> >
> > > Hi Team,
> > >
> > > I was just taking a look over the roadmap for Whirr 0.8.0. I think the
> > top
> > > priority should addressing the lack of deterministic behaviour on
> cluster
> > > deployment - service start. A cluster should either start as expected
> or
> > > fail all the time.
> > >
> > > Some of the relevant issues are:
> > >
> > > * https://issues.apache.org/jira/browse/WHIRR-221
> > > * https://issues.apache.org/jira/browse/WHIRR-266
> > > * https://issues.apache.org/jira/browse/WHIRR-295
> > > * https://issues.apache.org/jira/browse/WHIRR-294
> > > * https://issues.apache.org/jira/browse/WHIRR-468
> > >
> > > One possible workaround the we should be able to implement pretty soon
> is
> > > to give Whirr the ability to restart a specific role.
> > >
> > > I am also thinking that as soon as we close the listed issues we can
> cut
> > a
> > > release.
> > >
> > > What do you think?
> > >
> > > -- Andrei Savu / andreisavu.ro
> > >
> >
>

Reply via email to