lars hofhansl 2012-10-19, 05:39
Jean-Daniel Cryans 2012-10-19, 15:50
Here is some more background information from
hadoop 1.1 release annoucement:
The thinking behind new recommendation is that future patches for reducing
MTTR may depend on the improvement unique to hadoop 1.1 (absent from hadoop
For reference, here is list of incompatible changes between hadoop 1.0 and
HDFS-2617 <https://issues.apache.org/jira/browse/HDFS-2617>. Replaced
Kerberized SSL for image transfer and fsck with
SPNEGO-based solution. (Jakob Homan, Owen O'Malley, Alejandro Abdelnur and
Aaron T. Myers via atm)
HDFS-3044 <https://issues.apache.org/jira/browse/HDFS-3044>. fsck move
should be non-destructive by default.
(Colin Patrick McCabe via eli)
HADOOP-8230 <https://issues.apache.org/jira/browse/HADOOP-8230>. Enable
sync by default and disable append. (eli)
HADOOP-8365 <https://issues.apache.org/jira/browse/HADOOP-8365>. Provide
ability to disable working sync. (eli)
HADOOP-8552 <https://issues.apache.org/jira/browse/HADOOP-8552>. Conflict:
Same security.log.file for multiple users.
(kkambatl via tucu)
On Fri, Oct 19, 2012 at 8:50 AM, Jean-Daniel Cryans <[EMAIL PROTECTED]>wrote:
> Pardon my lack of knowledge, is 1.1 wire compatible with 1.0? If can
> just drop a 1.1 client on top of 1.0 (any 1.0), and it's tested, then
> I would be +1.
> On Thu, Oct 18, 2012 at 10:39 PM, lars hofhansl <[EMAIL PROTECTED]>
> > Hadoop 1.1 was released and has some important correctness and
> performance fixes.
> > Should we default HBase 0.94 to Hadoop 1.1?
> > (HBase 0.96 was already switched... I think)
> > -- Lars
lars hofhansl 2012-10-20, 01:21