@raouia "HDFS Storage Capacity Usage" : This service-level alert is triggered if the increase in storage capacity usage deviation has grown beyond the specified threshold within a given period. This alert will monitor Daily and Weekly periods. There are tow types of this script "HDFS Storage Capacity Usage (Daily)" and "HDFS Storage Capacity Usage (Weekely)" In your screenshot we see it it "HDFS Storage Capacity Usage (Weekely)" 625604664B means almost 625 MB 2992430585B means almost 3000 MB 598486117B which is almost 598 MB This is average. By default the "HDFS Storage Capacity Usage (Weekly)" has the following limits set: Growth Rate CRITICAL: 20% Growth Rate WARNING: 10% 20% of 3000 MB is = 600 MB (Where as your HDFS growth in a week is 625 which is slightly more than 20% .. about 21%) Hence you see this CRITICAL message. . This alert does not have to do anything with the Total Storage Size Or Available Storage Size. This alert is mainly concerned about the Weekely Usage Growth Rate of the Storage. You can increase the default "Growth Rate CRITICAL: 20%" if you see that 20% weekely growth in Storage Usage Weekely is normal in your scenario. ... View more

@Anton P If you a re using Non Default Postgres (here we see that you are using Postgres 9.5) in that case while doing the ambari-server setup you MUST choose the Option [4] PostgreSQL Instead of Option 1 (Embedded) Enter advanced database configuration [y/n] (n)? y Configuring database... ============================================================================== Choose one of the following options: [1] - PostgreSQL (Embedded) [2] - Oracle [3] - MySQL [4] - PostgreSQL [5] - Microsoft SQL Server (Tech Preview) [6] - SQL Anywhere . Also if you want to use Non Default Postgres then you should configre it prior to setup ambari as : https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.2.0/bk_ambari-administration/content/using_ambari_with_postgresql.html ... View more

@ A P Looks like the problem is that you have installed "ambari-server" but not the ambari-agent. So can you please try the following and see if it works: 1. Reinstall ambari-server # yum reinstall ambari-server -y 2. Install ambari-agent # yum install ambari-agent -y 3. Now try to run the ambari-server setup # ambari-server setup . ... View more

@Prakash Punj Looks like recently you have migrated some "Saved Queries" from Hive View 1.0 to Hive View 1.5 If we do the migration twice then we might see the same error when we next time try to run any query: Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "ds_jobimpl_206_pkey" Detail: Key (ds_id)=(52) already exists. at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161) . As a workaround you can try the following: 1. Take a DB dump of your Ambari Database. 2. Find the Max Sequence ID in the "ambari_sequences" table of ambari Databse. # psql -U ambari ambari Password for user ambari: psql (9.2.18) Type "help" for help. ambari=> select * from ambari_sequences; . You will find a sequence ID as "ds_jobimpl_206_id_seq" you will need to increase it's value to a high value to avoid the "duplicate key value violates unique constraint" issue. So update the value for this as following: (setting a very high value 12000 intentionally) UPDATE ambari_sequences set sequence_value=12000 WHERE sequence_name='ds_jobimpl_206_id_seq'; Then restart ambari server . It looks related to the BUG: https://issues.apache.org/jira/browse/AMBARI-21977 (not resolved yet so we should try the workaround for now) ... View more