Merged from trunk. HDFS-4221. Remove the format limitation point from BKJM documentation as HDFS-3810 closed. Contributed by Rakesh R.
git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1608777 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
5e22de1cf7
commit
50c7825d10
|
@ -532,6 +532,9 @@ Release 2.5.0 - UNRELEASED
|
||||||
HDFS-4286. Changes from BOOKKEEPER-203 broken capability of including
|
HDFS-4286. Changes from BOOKKEEPER-203 broken capability of including
|
||||||
bookkeeper-server jar in hidden package of BKJM (Rakesh R via umamahesh)
|
bookkeeper-server jar in hidden package of BKJM (Rakesh R via umamahesh)
|
||||||
|
|
||||||
|
HDFS-4221. Remove the format limitation point from BKJM documentation as HDFS-3810
|
||||||
|
closed. (Rakesh R via umamahesh)
|
||||||
|
|
||||||
BREAKDOWN OF HDFS-2006 SUBTASKS AND RELATED JIRAS
|
BREAKDOWN OF HDFS-2006 SUBTASKS AND RELATED JIRAS
|
||||||
|
|
||||||
HDFS-6299. Protobuf for XAttr and client-side implementation. (Yi Liu via umamahesh)
|
HDFS-6299. Protobuf for XAttr and client-side implementation. (Yi Liu via umamahesh)
|
||||||
|
|
|
@ -855,22 +855,5 @@ digest:hdfs-zkfcs:vlUvLnd8MlacsE80rDuu6ONESbM=:rwcda
|
||||||
|
|
||||||
*** <<Current limitations>>
|
*** <<Current limitations>>
|
||||||
|
|
||||||
1) NameNode format command will not format the BookKeeper data automatically.
|
1) Security in BookKeeper. BookKeeper does not support SASL nor SSL for
|
||||||
We have to clean the data manually from BookKeeper cluster
|
|
||||||
and create the /ledgers/available path in Zookeeper.
|
|
||||||
----
|
|
||||||
$ zkCli.sh create /ledgers 0
|
|
||||||
$ zkCli.sh create /ledgers/available 0
|
|
||||||
----
|
|
||||||
Note:
|
|
||||||
bookkeeper://zk1:2181;zk2:2181;zk3:2181/hdfsjournal
|
|
||||||
The final part /hdfsjournal specifies the znode in zookeeper where
|
|
||||||
ledger metadata will be stored. Administrators may set this to anything
|
|
||||||
they wish.
|
|
||||||
|
|
||||||
2) Security in BookKeeper. BookKeeper does not support SASL nor SSL for
|
|
||||||
connections between the NameNode and BookKeeper storage nodes.
|
connections between the NameNode and BookKeeper storage nodes.
|
||||||
|
|
||||||
3) Auto-Recovery of storage node failures. Work inprogress
|
|
||||||
{{{https://issues.apache.org/jira/browse/BOOKKEEPER-237 }BOOKKEEPER-237}}.
|
|
||||||
Currently we have the tools to manually recover the data from failed storage nodes.
|
|
||||||
|
|
Loading…
Reference in New Issue