Hi devs,
I am trying to fix https://issues.apache.org/jira/browse/AMBARI-4930 since it
is becoming a blocking issue for us. I am taking a look at the code and I am
seeing this locking pattern in ClusterImpl.java:
clusterGlobalLock.writeLock().lock();
try {
writeLock.lock();
ing command to take a thread dump when the exception reoccurs.
>
>{JAVA_HOME}/bin/jstack -l
>
>Hope this helps.
>
>Best Regards,
>Sid
>
>
>On Tue, Mar 4, 2014 at 4:25 AM, JOAQUIN GUANTER GONZALBEZ
>wrote:
>
>> Hi Siddarth,
>>
>> I have opened
les and reclaim disk
space by using the VACUUM command.
Best Regards,
Sid
On Thu, Feb 27, 2014 at 10:06 PM, JOAQUIN GUANTER GONZALBEZ
mailto:x...@tid.es>> wrote:
Hello,
Since we upgraded to Ambari 1.4.1, we see the following initialization error
from time to time when trying to start ambar
Hi devs,
I reported and added a patch some time ago for
https://issues.apache.org/jira/browse/AMBARI-2475, but it was never picked up
by anybody. Is there anything I can do to speed up the review process?
Thanks!
Ximo
Este mensaje se dirige exclusivamente a su
