To upgrade JDK across all HDP services on all nodes using Ambari, the following instructions have proven to be helpful. This requires downtime on ALL HDP components. a. Use the 'Stop all' from the Actions button off the main Ambari dashboard to shut down all HDP components. b. Using Clush/Pdsh/Cluster scripting tool of choice, confirm that ALL Java processes are fully stopped across ALL cluster nodes (excluding Ambari), killing any orphaned processes that Ambari was unable to stop. c. Run the following from Ambari master node (as root) to stop the Ambari-agent and Ambari-server processes. service ambari-agent stop service ambari-server stop d. Run the following from Ambari-server master node (as root): ambari-server setup (and follow the prompts, example provided below) e.g.: [root@sandbox conf]# ambari-server setup Using python /usr/bin/python2.6 Setup ambari-server Checking SELinux... SELinux status is 'disabled' Customize user account for ambari-server daemon [y/n] (n)? n Adjusting ambari-server permissions and ownership... Checking firewall status... Checking JDK... Do you want to change Oracle JDK [y/n] (n)? y [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8 [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7 [3] Custom JDK ============================================================================== Enter choice (1): 3 WARNING: JDK must be installed on all hosts and JAVA_HOME must be valid on all hosts. WARNING: JCE Policy files are required for configuring Kerberos security. If you plan to use Kerberos,please make sure JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts. Path to JAVA_HOME: {Enter your exact full path to JDK base location} Validating JDK on Ambari Server...done. Completing setup... Configuring database... Enter advanced database configuration [y/n] (n)? n Configuring database... Default properties detected. Using built-in database. Configuring ambari database... Checking PostgreSQL... Configuring local database... Connecting to local database...done. Configuring PostgreSQL... Backup for pg_hba found, reconfiguration not required Extracting system views... ........ Adjusting ambari-server permissions and ownership... Ambari Server 'setup' completed successfully. e. Start the Ambari-server and ambari-agent processes: service ambari-server start service ambari-agent start f. Using 'Start All' from Actions button on main Ambari Dashboard, start up all the HDP components. g. Confirm with 'ps -ef' that all the processes are using the new java location for all HDP components. e.g. ps -ef | grep HiveServer2 | grep -v grep hive 95143 1 0 15:26 ? 00:00:37 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64/bin/java ... ps -ef | grep ResourceManager | grep -v grep yarn 116722 1 1 15:48 ? 00:03:22 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64/bin/java... Due to Option #1 and Option #2 being hardcoded to older/problematic version of JDK on various Ambari versions, it is advised to use Option 3 only. https://hortonworks.jira.com/browse/BUG-44244 https://hortonworks.jira.com/browse/BUG-45794 ... View more

The current state of Hive ACID is as follows: Technical Alert sent out on 2015-09-10: Subject: Hortonworks Technical Alert: Hive ACID feature Dear HDP Customer, Hortonworks Technical Support would like to make you aware about a potential issue you may encounter. Below are the details: COMPONENT: Hive VERSION: HDP 2.2.*, HDP 2.3.0 PROBLEM: Hive ACID feature not ready for production deployment IMPACT: Hive ACID supports two primary use cases: Hive Streaming Ingest Inserts/Updates/Deletes at low concurrency As the first set of users are developing their ACID solutions and deploying them in their staging environments, they’ve run into a series of technical issues which are indicate insufficient test case coverage for this particular feature. Hortonworks is currently working closely with these customers to provide fixes for these issues and make them successful in production. In addition, we are going back to our engineering processes and identifying the missing test cases and increasing our test case coverage. While these issues are being addressed, we’d like to alert other customers of these issues. Currently, Hortonworks is recommending that users wait on the use of the Hive ACID features until these issues have been addressed. Subsequent maintenance release will include these fixes and as we have successfully assisted the early adopters with their production deployments, we will retire this technical alert. SYMPTOMS: N.A. WORKAROUND: N.A. SOLUTION: There are two options: Wait for maintenance releases to appear which contain the necessary fixes to address known issues — or — If you’d like to use Hive ACID, please contact Hortonworks support and we can look at the details of your use case and provide additional advice on a case-by-case basis If you have any questions or concerns, please feel free to open a support case with us at support.hortoworks.com Thank you, The Hortonworks Team In addition, for use in further discussions, the following powerpoint presentation is available to share externally: https://hortonworks.app.box.com/files/0/f/2070270300/1/f_37967540402 Last but not least, there is the pending RMP JIRA tracking the backport of the bulk of ACID changes to the HDP 2.2.x branch: https://hortonworks.jira.com/browse/RMP-4830 ... View more