[
https://issues.apache.org/jira/browse/HAWQ-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247322#comment-15247322
]
ASF GitHub Bot commented on HAWQ-668:
-------------------------------------
Github user radarwave commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/622#discussion_r60184658
--- Diff: src/backend/utils/misc/etc/gpcheck.cnf ---
@@ -54,5 +54,60 @@ dfs.namenode.handler.count = 60
ipc.server.handler.queue.size = 3300
dfs.datanode.handler.count = 60
ipc.client.connection.maxidletime = 3600000
-dfs.namenode.accesstime.precision = -1
+dfs.namenode.accesstime.precision = 0
+dfs.client.read.shortcircuit = true
+[hdfs.non]
+hdfs.non = none
+dfs.block.access.token.enable = FALSE
+
+[hdfs.ha]
+hdfs.ha = none
+dfs.block.access.token.enable = FALSE
+
+[hdfs.kerberos]
+hdfs.kerberos = none
+dfs.block.access.token.enable = TRUE
+dfs.datanode.data.dir.perm = 750
--- End diff --
Since 700 is default values and user might have something like '755', we do
not check for non-kerberos mode.
> hawq check should able to check yarn settings
> ---------------------------------------------
>
> Key: HAWQ-668
> URL: https://issues.apache.org/jira/browse/HAWQ-668
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Command Line Tools
> Reporter: Radar Lei
> Assignee: Radar Lei
>
> Since hawq now use yarn for resource manager, so we'd better to use 'hawq
> check' to validate yarn configurations.
> BTW, we should update some os, hdfs, hawq-site.xml expected values with
> latest best practice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
