About hvj

hvj · ‎05-12-2016

Thanks @Pradeep kumar. I have implemented the solution of adding non root volume. Do i need to verify anything post change. Let me know.

hvj · ‎05-12-2016

Hi @Ravi Mutyala Thanks for your reply.

hvj · ‎05-12-2016

Hi @Scott Shaw Thanks for your quick reply.

hvj · ‎05-11-2016

Hi All, My Ambari root partition is running out of space due to Hbase ambari-metrices[PATH is /var/lib/ambari-metrics-collector/hbase/data/default] Below folders are taking space. METRIC_AGGREGATE METRIC_RECORD_MINUTE METRIC_RECORD_HOURLY METRIC_RECORD Can I delete older files directly here ? What can be the other option ? Can I add big volume and redirect logs to new volume. what all parameter do i need to change in UI / commandLine OR Can I shift from embedded mode to distributed mode. what all steps/precaution needed to shift to this mode. Any help is appreciated. Thanks in advance.

hvj · ‎03-11-2016

Hi @Geoffrey Shelton Okot, I have reboot it after the issue. cluster was already down. On host localhost.localdomain role HIVE_METASTORE in invalid state. Invalid transition. Invalid event: HOST_SVCCOMP_OP_IN_PROGRESS at UNKNOWN also getting above error for all componant

hvj · ‎03-11-2016

Hi @vpoornalingam agent is up and running also matching PID. Cluster is single node cluster I am also getting for all component On host localhost.localdomain role HIVE_METASTORE in invalid state. Invalid transition. Invalid event: HOST_SVCCOMP_OP_IN_PROGRESS at UNKNOWN

hvj · ‎03-11-2016

Hi @Artem Ervits ambari agent is up and running. Also getting above error at restart for each ambari component On host localhost.localdomain role HIVE_METASTORE in invalid state. Invalid transition. Invalid event: HOST_SVCCOMP_OP_IN_PROGRESS at UNKNOWN

hvj · ‎03-10-2016

Hi All, We are using hdp 2.3. Today morning when i stepped in office. I saw that services are in UNKNOWN state. this is QA cluster sp even after restart and reboot, killing ambari-agent, ambari-server, postgresql restart is not helping me. Here is the screenshot and logs. ambari.jpg Logs are here ====================================================== WARN [ambari-hearbeat-monitor] HeartbeatMonitor:154 - Heartbeat lost from host localhost.localdomain WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component METRICS_MONITOR on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component METRICS_COLLECTOR on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HBASE_MASTER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HBASE_REGIONSERVER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component PHOENIX_QUERY_SERVER WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component SECONDARY_NAMENODE on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component DATANODE on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component NAMENODE on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HIVE_SERVER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component MYSQL_SERVER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HIVE_METASTORE on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component WEBHCAT_SERVER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component KAFKA_BROKER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HISTORYSERVER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component SPARK_JOBHISTORYSERVE WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component NODEMANAGER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component APP_TIMELINE_SERVER o WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component RESOURCEMANAGER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component ZEPPELIN_MASTER on WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component ZOOKEEPER_SERVER on ======================================================= Kindly suggest. I am not sure if state changed by ambari-api ? If so, How can I track/check the same. Thanks in advance. Harshal

hvj · ‎02-19-2016

@Randy Gelhausen thanks for the input. phoenix with spark is next stage of our roadmap. your input is valuable.

hvj · ‎02-19-2016

Thanks @asinghal it also improves performance.

Online	Offline
Last Visited	‎05-08-2017 05:09 AM

Member Since	‎03-21-2017 12:24 AM
Last Visited	‎05-08-2017 05:09 AM
Posts	19
Kudos received	9

Cloudera Community

Cloudera Community

Re: Ambari hbase metrices filling up ambari-server...

Re: Ambari hbase metrices filling up ambari-server...

Re: Ambari hbase metrices filling up ambari-server...

Ambari hbase metrices filling up ambari-server spa...

Re: HeartBeat Lost loss for all services

Re: HeartBeat Lost loss for all services

Re: HeartBeat Lost loss for all services

HeartBeat Lost loss for all services

Re: Phoenix and hbase timeouts or lack of resource...

Re: Phoenix and hbase timeouts or lack of resource...