urday, June 27, 2015 at 3:16 AM
To: "user@ambari.apache.org<mailto:user@ambari.apache.org>"
mailto:user@ambari.apache.org>>
Subject: Re: Ambari data corruption/recovery process
Is removing that directory necessary for agents that registered without ssh?
On Jun 26, 2015 5:5
he.org"
> Date: Friday, June 26, 2015 5:22 PM
> To: "user@ambari.apache.org"
> Subject: Re: Ambari data corruption/recovery process
>
> Thanks Yusaku for the quick response.
>
> For our production systems, we're planning on using Postgres replication
> to
org<mailto:user@ambari.apache.org>"
mailto:user@ambari.apache.org>>
Subject: Re: Ambari data corruption/recovery process
Thanks Yusaku for the quick response.
For our production systems, we're planning on using Postgres replication to
ensure backups, though that doesn't defend
ent.ini to point to the new Ambari
> Server hostname and restart the agent.
>
> Yusaku
>
> From: Clark Breyman
> Reply-To: "user@ambari.apache.org"
> Date: Friday, June 26, 2015 5:10 PM
> To: "user@ambari.apache.org"
> Subject: Ambari data corruption/
ari.apache.org>"
mailto:user@ambari.apache.org>>
Date: Friday, June 26, 2015 5:10 PM
To: "user@ambari.apache.org<mailto:user@ambari.apache.org>"
mailto:user@ambari.apache.org>>
Subject: Ambari data corruption/recovery process
I'm wondering if anyone can
I'm wondering if anyone can share pointers/procedures/best practices to
handle the scenarios where:
a) The sql database becomes corrupt. (Bugs, ...)
b) The Ambari service host is lost (e.g. EC2 instance termination, physical
hardware loss, ...)
