[AMBARI-13647] Changes to mapred-site configuration does not force Hive restart

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.7.0, 2.1.0, 2.1.1
• Component/s: ambari-server
• Assignee: Unassigned
• Reporter: Tuong Truong
• Created: 30/Oct/15 02:40
• Updated: 30/Oct/15 21:42
• Resolved: 30/Oct/15 21:42

Description

Hive conf directory has a copy of mapred-site.xml that is generated when Hive is restarted. This copy is used by Hive to run MR jobs. When mapred-site configuration is change, Hive service is not flagged for restart since only after restarting of Hive that the mapred-site.xml in /etc/hive/conf is regenerated.

As a result, mapred-site configuration changes does not take effect for Hive until Hive is restarted.

The change that caused this issue was a deliberate change in JIRA-6482

Issue Links

• is duplicated by: AMBARI-12894 Changing mapreduce.application.classpath via Ambari doesn't prompt for Hive Restart