hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iwasak...@apache.org
Subject hadoop git commit: HADOOP-14702. Fix formatting issue and regression caused by conversion from APT to Markdown. Contributed by Doris Gu.
Date Wed, 02 Aug 2017 06:21:58 GMT
Repository: hadoop
Updated Branches:
  refs/heads/branch-2 b0330c15d -> d9a07b390


HADOOP-14702. Fix formatting issue and regression caused by conversion from APT to Markdown.
Contributed by Doris Gu.


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/d9a07b39
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/d9a07b39
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/d9a07b39

Branch: refs/heads/branch-2
Commit: d9a07b39046c323d430b98eff6603eaf58e18372
Parents: b0330c1
Author: Masatake Iwasaki <iwasakims@apache.org>
Authored: Wed Aug 2 06:19:21 2017 +0000
Committer: Masatake Iwasaki <iwasakims@apache.org>
Committed: Wed Aug 2 06:21:37 2017 +0000

----------------------------------------------------------------------
 .../hadoop-common/src/site/markdown/Metrics.md  |  7 ++++-
 .../src/site/markdown/ServiceLevelAuth.md       | 32 +++++++++++---------
 2 files changed, 24 insertions(+), 15 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/d9a07b39/hadoop-common-project/hadoop-common/src/site/markdown/Metrics.md
----------------------------------------------------------------------
diff --git a/hadoop-common-project/hadoop-common/src/site/markdown/Metrics.md b/hadoop-common-project/hadoop-common/src/site/markdown/Metrics.md
index 26721d1..e744f76 100644
--- a/hadoop-common-project/hadoop-common/src/site/markdown/Metrics.md
+++ b/hadoop-common-project/hadoop-common/src/site/markdown/Metrics.md
@@ -170,6 +170,7 @@ Each metrics record contains tags such as ProcessName, SessionId, and
Hostname a
 | `GetImageAvgTime` | Average fsimage download time in milliseconds |
 | `PutImageNumOps` | Total number of fsimage uploads to SecondaryNameNode |
 | `PutImageAvgTime` | Average fsimage upload time in milliseconds |
+| `TotalFileOps` | Total number of file operations performed |
 | `NNStarted`| Deprecated: Use NNStartedTimeInMillis instead  |
 | `NNStartedTimeInMillis`| NameNode start time in milliseconds |
 | `GenerateEDEKTimeNumOps` | Total number of generating EDEK |
@@ -334,6 +335,10 @@ Each metrics record contains tags such as SessionId and Hostname as additional
i
 | `SendDataPacketBlockedOnNetworkNanosAvgTime` | Average waiting time of sending packets
in nanoseconds |
 | `SendDataPacketTransferNanosNumOps` | Total number of sending packets |
 | `SendDataPacketTransferNanosAvgTime` | Average transfer time of sending packets in nanoseconds
|
+| `TotalWriteTime` | Total number of milliseconds spent on write operation |
+| `TotalReadTime` | Total number of milliseconds spent on read operation |
+| `RemoteBytesRead` | Number of bytes read by remote clients |
+| `RemoteBytesWritten` | Number of bytes written by remote clients |
 | `BPServiceActorInfo` | The information about a block pool service actor |
 | `BlocksInPendingIBR` | Number of blocks in pending incremental block report (IBR) |
 | `BlocksReceivingInPendingIBR` | Number of blocks at receiving status in pending incremental
block report (IBR) |
@@ -565,7 +570,7 @@ MetricsSystem shows the statistics for metrics snapshots and publishes.
Each met
 | `Sink_`*instance*`NumOps` | Total number of sink operations for the *instance* |
 | `Sink_`*instance*`AvgTime` | Average time in milliseconds of sink operations for the *instance*
|
 | `Sink_`*instance*`Dropped` | Total number of dropped sink operations for the *instance*
|
-| `Sink_`*instance*`Qsize` | Current queue length of sink operations  (BUT always set to
0 because nothing to increment this metrics, see [HADOOP-9941](https://issues.apache.org/jira/browse/HADOOP-9941))
|
+| `Sink_`*instance*`Qsize` | Current queue length of the sink |
 
 default context
 ===============

http://git-wip-us.apache.org/repos/asf/hadoop/blob/d9a07b39/hadoop-common-project/hadoop-common/src/site/markdown/ServiceLevelAuth.md
----------------------------------------------------------------------
diff --git a/hadoop-common-project/hadoop-common/src/site/markdown/ServiceLevelAuth.md b/hadoop-common-project/hadoop-common/src/site/markdown/ServiceLevelAuth.md
index 22bd25b..eb3b122 100644
--- a/hadoop-common-project/hadoop-common/src/site/markdown/ServiceLevelAuth.md
+++ b/hadoop-common-project/hadoop-common/src/site/markdown/ServiceLevelAuth.md
@@ -78,13 +78,27 @@ A special value of `*` implies that all users are allowed to access the
service.
 
 If access control list is not defined for a service, the value of `security.service.authorization.default.acl`
is applied. If `security.service.authorization.default.acl` is not defined, `*` is applied.
 
-* Blocked Access Control ListsIn some cases, it is required to specify blocked access control
list for a service. This specifies the list of users and groups who are not authorized to
access the service. The format of the blocked access control list is same as that of access
control list. The blocked access control list can be specified via `$HADOOP_CONF_DIR/hadoop-policy.xml`.
The property name is derived by suffixing with ".blocked".
+### Blocked Access Control Lists
 
-    Example: The property name of blocked access control list for `security.client.protocol.acl>>
will be <<<security.client.protocol.acl.blocked`
+In some cases, it is required to specify blocked access control list for a service. This
specifies the list of users and groups who are not authorized to access the service. The format
of the blocked access control list is same as that of access control list. The blocked access
control list can be specified via `$HADOOP_CONF_DIR/hadoop-policy.xml`. The property name
is derived by suffixing with ".blocked".
 
-    For a service, it is possible to specify both an access control list and a blocked control
list. A user is authorized to access the service if the user is in the access control and
not in the blocked access control list.
+Example: The property name of blocked access control list for `security.client.protocol.acl`
will be `security.client.protocol.acl.blocked`
 
-    If blocked access control list is not defined for a service, the value of `security.service.authorization.default.acl.blocked`
is applied. If `security.service.authorization.default.acl.blocked` is not defined, empty
blocked access control list is applied.
+For a service, it is possible to specify both an access control list and a blocked control
list. A user is authorized to access the service if the user is in the access control and
not in the blocked access control list.
+
+If blocked access control list is not defined for a service, the value of `security.service.authorization.default.acl.blocked`
is applied. If `security.service.authorization.default.acl.blocked` is not defined, empty
blocked access control list is applied.
+
+### Access Control using Lists of IP Addresses, Host Names and IP Ranges
+
+Access to a service can be controlled based on the ip address of the client accessing the
service. It is possible to restrict access to a service from a set of machines by specifying
a list of ip addresses, host names and ip ranges. The property name for each service is derived
from the corresponding acl's property name. If the property name of acl is security.client.protocol.acl,
property name for the hosts list will be security.client.protocol.hosts.
+
+If hosts list is not defined for a service, the value of `security.service.authorization.default.hosts`
is applied. If `security.service.authorization.default.hosts` is not defined, `*` is applied.
+
+It is possible to specify a blocked list of hosts. Only those machines which are in the hosts
list, but not in the blocked hosts list will be granted access to the service. The property
name is derived by suffixing with ".blocked".
+
+Example: The property name of blocked hosts list for `security.client.protocol.hosts` will
be `security.client.protocol.hosts.blocked`
+
+If blocked hosts list is not defined for a service, the value of `security.service.authorization.default.hosts.blocked`
is applied. If `security.service.authorization.default.hosts.blocked` is not defined, empty
blocked hosts list is applied.
 
 ### Refreshing Service Level Authorization Configuration
 
@@ -100,16 +114,6 @@ Refresh the service-level authorization configuration for the ResourceManager:
 
 Of course, one can use the `security.refresh.policy.protocol.acl` property in `$HADOOP_CONF_DIR/hadoop-policy.xml`
to restrict access to the ability to refresh the service-level authorization configuration
to certain users/groups.
 
-* Access Control using list of ip addresses, host names and ip rangesAccess to a service
can be controlled based on the ip address of the client accessing the service. It is possible
to restrict access to a service from a set of machines by specifying a list of ip addresses,
host names and ip ranges. The property name for each service is derived from the corresponding
acl's property name. If the property name of acl is security.client.protocol.acl, property
name for the hosts list will be security.client.protocol.hosts.
-
-    If hosts list is not defined for a service, the value of `security.service.authorization.default.hosts`
is applied. If `security.service.authorization.default.hosts` is not defined, `*` is applied.
-
-    It is possible to specify a blocked list of hosts. Only those machines which are in the
hosts list, but not in the blocked hosts list will be granted access to the service. The property
name is derived by suffixing with ".blocked".
-
-    Example: The property name of blocked hosts list for `security.client.protocol.hosts`
will be `security.client.protocol.hosts.blocked`
-
-    If blocked hosts list is not defined for a service, the value of `security.service.authorization.default.hosts.blocked`
is applied. If `security.service.authorization.default.hosts.blocked` is not defined, empty
blocked hosts list is applied.
-
 ### Examples
 
 Allow only users `alice`, `bob` and users in the `mapreduce` group to submit jobs to the
MapReduce cluster:


---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org


Mime
View raw message