when executing $hadoop dfs -cat
/user/h_yanghao3/.slider/cluster/hbase1/app_conf.json
the result is as follows, it turns out that the jvm.opt has set right
{
"schema" : "http://example.org/specification/v2.0.0";,
"metadata" : { },
"global" : {
"site.dfs.namenode.kerberos.principal" : "hdfs_tst/[email protected]
",
"system_configs" : "core-site,hdfs-site,hbase-site",
"site.hbase-site.hbase.regionserver.global.memstore.upperLimit" : "0.3",
"site.hbase-site.hbase.coprocessor.region.classes" :
"org.apache.hadoop.hbase.security.token.TokenProvider,org.apache.hadoop.hbase.security.access.AccessController",
"site.hbase-site.hbase.coprocessor.master.classes" :
"org.apache.hadoop.hbase.security.access.AccessController",
"site.global.monitor_protocol" : "http",
"site.hbase-site.hbase.hregion.max.filesize" : "42949672960",
"jvm.opts" : "-Dpkg.version=0.94.11-mdh1.2.23-hadoop2.4
-Djava.security.krb5.conf=/home/work/app/yarn/lgtst-xiaomi2/nodemanager/krb5.conf
",
