Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Sender: Brett Porter <brett@porterclan.net>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: Re: What should happen when a distributed agent dies?
From: Brett Porter <brett@apache.org>
In-Reply-To: <adba96190909281003q159545c4na8038dec4fd7fb06@mail.gmail.com>
Date: Wed, 30 Sep 2009 17:35:29 +1000
Content-Transfer-Encoding: 7bit
Message-Id: <C12C73DC-F885-4F84-9A15-DF71B3D0E76E@apache.org>
References: <adba96190909281003q159545c4na8038dec4fd7fb06@mail.gmail.com>
To: dev@continuum.apache.org

So I went through the cluster of issues you opened and put them in  
1.3.5, then realised that we had already kind of settled on the list  
of things for 1.3.5 :)

Should we:
1) keep them where they are?
2) push them to 1.3.6?
3) push them to 1.4.0?
4) or are they already addressed by Marica's other fix?

Cheers,
Brett

On 29/09/2009, at 3:03 AM, Wendy Smoak wrote:

> I've been working with Distributed Builds lately, and I've found that
> it works if everything is perfect, but if something goes wrong it has
> a hard time coping with the problem, and it doesn't recover.
>
> For example, it's a given that at some point, an agent is going to die
> without being properly removed first.
>
> Currently if this happens, the Queues page breaks (error/stack trace)
> and you can't edit or delete the offending agent to disable or get rid
> of it.
>
> The agent is also still shown as 'enabled' on the Distributed Agents
> page even though it's not responding.
>
> What should happen in this case?
>
> I'm all for having the system automatically disable any agent that is
> not behaving properly.  At first, the admin may have to manually
> re-enable it.  In the future we might come up with a way for it to
> auto-recover.
>
> Thoughts?
>
> -- 
> Wendy