[jira] [Updated] (AMBARI-18633) Mapreduce 'Config group' changes YARN Config Group overrides and vice versa.
[ https://issues.apache.org/jira/browse/AMBARI-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18633: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Mapreduce 'Config group' changes YARN Config Group overrides and vice versa. > > > Key: AMBARI-18633 > URL: https://issues.apache.org/jira/browse/AMBARI-18633 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Attachments: AMBARI-18633_branch-2.2.2.patch > > > *STR:* > # Change a config (Memory allocated for all YARN containers on a node) from > non-default service group in YARN service and save. > # Navigate to MapReduce service and choose a non-default service group to > make config changes (Map Memory) and save > *Expected Result:* MapReduce config for non-default service group should get > successfully saved > *Actual Result:* Along wth the MapReduce config changes, non-default service > group of YARN that was previously tweaked gets reset to empty bag of > properties. > It is noticed that while saving configs of non-default group of MapReduce > service, two PUT API calls are made: one for MapReduce which is expected but > one more for YARN non-default service group with empty array for desired > configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-18633) Mapreduce 'Config group' changes YARN Config Group overrides and vice versa.
[ https://issues.apache.org/jira/browse/AMBARI-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18633: -- Status: Patch Available (was: Open) > Mapreduce 'Config group' changes YARN Config Group overrides and vice versa. > > > Key: AMBARI-18633 > URL: https://issues.apache.org/jira/browse/AMBARI-18633 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Attachments: AMBARI-18633_branch-2.2.2.patch > > > *STR:* > # Change a config (Memory allocated for all YARN containers on a node) from > non-default service group in YARN service and save. > # Navigate to MapReduce service and choose a non-default service group to > make config changes (Map Memory) and save > *Expected Result:* MapReduce config for non-default service group should get > successfully saved > *Actual Result:* Along wth the MapReduce config changes, non-default service > group of YARN that was previously tweaked gets reset to empty bag of > properties. > It is noticed that while saving configs of non-default group of MapReduce > service, two PUT API calls are made: one for MapReduce which is expected but > one more for YARN non-default service group with empty array for desired > configs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18633) Mapreduce 'Config group' changes YARN Config Group overrides and vice versa.
[ https://issues.apache.org/jira/browse/AMBARI-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18633: -- Attachment: AMBARI-18633_branch-2.2.2.patch > Mapreduce 'Config group' changes YARN Config Group overrides and vice versa. > > > Key: AMBARI-18633 > URL: https://issues.apache.org/jira/browse/AMBARI-18633 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Attachments: AMBARI-18633_branch-2.2.2.patch > > > *STR:* > # Change a config (Memory allocated for all YARN containers on a node) from > non-default service group in YARN service and save. > # Navigate to MapReduce service and choose a non-default service group to > make config changes (Map Memory) and save > *Expected Result:* MapReduce config for non-default service group should get > successfully saved > *Actual Result:* Along wth the MapReduce config changes, non-default service > group of YARN that was previously tweaked gets reset to empty bag of > properties. > It is noticed that while saving configs of non-default group of MapReduce > service, two PUT API calls are made: one for MapReduce which is expected but > one more for YARN non-default service group with empty array for desired > configs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
