I looked at article published by Hortonworks support, named How to encrypt column family in HBase? At the bottom of the article it shows these versions: Version: 2-6-1, 2-6, 2-6-3, 2-6-4, H3-0-0, 2-6-5, HDP2-6-2 Does this mean you recommend using Hbase encryption only in those versions? Also, is there a prefered way of encrypting Hbase? Using hdfs encryption zones or hbase server encryption? Thanks ... View more

Hi, I try to stop ambari server and the command runs fine, tells me it stopped. But I can still login to UI and I still see new processes created at the time I issued the command, 21:38. # ambari-server stop Using python /usr/bin/python Stopping ambari-server Waiting for server stop... Ambari Server stopped # ps -ef|grep ambar tladmin 23536 1 41 21:04 ? 00:14:11 /usr/java/default/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar org.apache.ambari.server.controller.AmbariServer postgres 23563 1969 0 21:04 ? 00:00:00 postgres: ambari ambari 127.0.0.1(45338) idle postgres 23565 1969 0 21:04 ? 00:00:02 postgres: ambari ambari 127.0.0.1(45350) idle postgres 23662 1969 0 21:05 ? 00:00:02 postgres: ambari ambari 127.0.0.1(45412) idle postgres 23674 1969 0 21:05 ? 00:00:00 postgres: ambari ambari 127.0.0.1(45414) idle postgres 23829 1969 0 21:07 ? 00:00:00 postgres: ambari ambari 127.0.0.1(45544) idle postgres 23830 1969 0 21:07 ? 00:00:00 postgres: ambari ambari 127.0.0.1(45546) idle postgres 23831 1969 0 21:07 ? 00:00:00 postgres: ambari ambari 127.0.0.1(45548) idle postgres 24382 1969 0 21:10 ? 00:00:02 postgres: ambari ambari 127.0.0.1(45702) idle root 29277 1 0 21:38 ? 00:00:00 bash /etc/init.d/ambari-server start root 29293 29277 25 21:38 ? 00:00:01 /usr/bin/python /usr/sbin/ambari-server.py start root 29357 29293 0 21:38 ? 00:00:00 /bin/sh -c ulimit -n 10000 ; /bin/su tladmin -s /bin/sh -c '. /var/lib/ambari-server/ambari-env.sh && /usr/java/default/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' org.apache.ambari.server.controller.AmbariServer > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > /var/run/ambari-server/ambari-server.exitcode' root 29358 29357 0 21:38 ? 00:00:00 /bin/su tladmin -s /bin/sh -c . /var/lib/ambari-server/ambari-env.sh && /usr/java/default/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar org.apache.ambari.server.controller.AmbariServer > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > /var/run/ambari-server/ambari-server.exitcode tladmin 29359 29358 0 21:38 ? 00:00:00 sh -c . /var/lib/ambari-server/ambari-env.sh && /usr/java/default/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar org.apache.ambari.server.controller.AmbariServer > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > /var/run/ambari-server/ambari-server.exitcode tladmin 29360 29359 99 21:38 ? 00:00:04 /usr/java/default/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar org.apache.ambari.server.controller.AmbariServer Auto-start services is disabled. This is Ambari 2.5.2. Why are there so many AmbariServer processes? If I login on another ambari server (same setup/versions, just different cluster), I see only one AmbariServer process. Thanks ... View more

Hello, I have a strange issue and can't figure out why it's happening. I upgraded our ambari cluster from 2.1.2 to 2.5.2. It all went well, but now when I login to ambari UI, I do not see my Metrics charts, it says "No Data". Ambari server log shows errors like these: 05 Jul 2018 08:08:55,516 ERROR [ambari-client-thread-111684] MetricsRequestHelper:115 - Error getting timeline metrics : Read timed out 05 Jul 2018 08:08:55,518 ERROR [ambari-client-thread-111684] MetricsRequestHelper:122 - Cannot connect to collector: SocketTimeoutException for hbmaster03.pod04.dal09.tealeaf.ibmcloud.com. Collector service hasn't moved, ports hasn't changed, it's all the same as it was before the upgrade. From the same ambari server, I can see the data with curl command, for example region count report: curl -H "Accept: application/json" "http://hbmaster03.pod04.dal09.tealeaf.ibmcloud.com:6188/ws/v1/timeline/metrics?metricNames=regionserver.Server.regionCount._avg&hostname=%&appId=hbase" I have tried setting these but didn't help: server.timeline.metrics.cache.connect.timeout.millis=60000 server.timeline.metrics.cache.disabled=true server.timeline.metrics.cache.interval.read.timeout.millis=60000 server.timeline.metrics.cache.read.timeout.millis=60000 Any advice what to try next? Many thanks! Marjana ... View more