Any updates on this issues? It seems that all HDFS jenkins builds are
still failing.
Regards,
Haohui
On Thu, Mar 12, 2015 at 12:53 AM, Vinayakumar B wrote:
> I think the problem started from here.
>
> https://builds.apache.org/job/PreCommit-HDFS-Build/9828/testReport/junit/org.apache.hadoop.hdfs
Just swept all the 2.7 blockers from the HDFS side. From the HDFS
prospective 2.7 should be good to go.
~Haohui
On Wed, Mar 25, 2015 at 11:47 AM, Konstantin Shvachko
wrote:
> Progress is good!
> What are the four blockers?
> Could you please mark them as such in the Jira.
>
> Thanks,
> --Konst
>
Hi Allen,
Thanks for driving this. Just some quick questions:
>>Removing changes.txt, relnotes.py, etc from branch-2 would be an
>> incompatible change. Pushing aside the questions of that document’s quality
>> (hint: lots of outright lying and missing several hundred jiras), it's
>>
+1. It has been a long delay for 2.7.0. It's a good time to push it out.
~Haohui
On Thu, Apr 9, 2015 at 12:56 PM, Steve Loughran wrote:
> There's a couple of S3a fixes coming along which could go into a 2.7.1;
> they've been held back to avoid rushing them in to 2.7.0 last-minute.
>
>> On 9 Apr
I believe this is not a regression -- I've seen some tests failed
miserably because the build artifacts are destroyed during the
execution of the unit tests.
~Haohui
On Wed, Apr 22, 2015 at 12:10 AM, Allen Wittenauer wrote:
>
> Some status:
>
> * So far, HADOOP-11627 was filed which is luckily a
In terms of the monitoring, we have put a lot of information into the
JMX output.
It's relatively easy to use python / ruby / node.js to write your own
tools to parse the information. In the longer term, it might also make
sense to move some of our tools to based on the JMX output instead of
makin
