date:20160609


[ 
https://issues.apache.org/jira/browse/AMBARI-17156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323799#comment-15323799
 ] 

Hudson commented on AMBARI-17156:
-

FAILURE: Integrated in Ambari-trunk-Commit #5048 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5048/])
AMBARI-17156: Ambari Agent: TestActionQueue and TestRecoveryManager 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b233c4314f1405118e79fe78c9e15cc36416f57c])
* ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py
* ambari-agent/src/test/python/ambari_agent/TestActionQueue.py


> Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests 
> failures
> 
>
> Key: AMBARI-17156
> URL: https://issues.apache.org/jira/browse/AMBARI-17156
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: rb48526.patch
>
>
> Unit Test failures in TestActionQueue.py and TestRecoveryManager.py:
> {code}
> ==
> ERROR: test_auto_execute_command (TestActionQueue.TestActionQueue)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", line 
> 407, in test_auto_execute_command
> dummy_controller.recovery_manager.update_config(5, 5, 1, 11, True, False, 
> "", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_execute_retryable_command_with_time_lapse 
> (TestActionQueue.TestActionQueue)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", line 
> 1002, in test_execute_retryable_command_with_time_lapse
> actionQueue.execute_command(command)
>   File "~/ambari/ambari-agent/src/main/python/ambari_agent/ActionQueue.py", 
> line 436, in execute_command
> self.controller.recovery_manager.get_current_status(command['role']))
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1165, in info
> self._log(INFO, msg, args, **kwargs)
> Revert "AMBARI-16935: Retry and recover from component install failures"
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1283, in _log
> record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, 
> func, extra)
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1257, in makeRecord
> rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 248, in __init__
> ct = time.time()
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 953, in 
> __call__
> return _mock_self._mock_call(*args, **kwargs)
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1011, in 
> _mock_call
> result = next(effect)
> StopIteration
> ==
> ERROR: test_process_commands (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
> line 144, in test_process_commands
> rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_recovery_required (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
> line 245, in test_recovery_required
> rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
>

[jira] [Commented] (AMBARI-17154) Typo in SmartSense Warning Dialog


[ 
https://issues.apache.org/jira/browse/AMBARI-17154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323798#comment-15323798
 ] 

Hudson commented on AMBARI-17154:
-

FAILURE: Integrated in Ambari-trunk-Commit #5048 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5048/])
AMBARI-17154 - Typo in SmartSense Warning Dialog (rzang) (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8a4d7c0c8e3b90f83744f57847a85815a245d62e])
* ambari-web/app/messages.js


> Typo in SmartSense Warning Dialog
> -
>
> Key: AMBARI-17154
> URL: https://issues.apache.org/jira/browse/AMBARI-17154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17154.patch
>
>
> Change suggestion text to:
> SmartSense securely collects cluster diagnostics in order to send you 
> recommendations and automate analysis for troubleshooting support cases. If 
> you choose not to install SmartSense, you will not receive any 
> recommendations, and you will need to collect configuration and logs manually 
> for troubleshooting support cases. Are you sure you want to proceed without 
> SmartSense?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17156) Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures


[ 
https://issues.apache.org/jira/browse/AMBARI-17156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323771#comment-15323771
 ] 

Hadoop QA commented on AMBARI-17156:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809327/rb48526.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7286//console

This message is automatically generated.

> Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests 
> failures
> 
>
> Key: AMBARI-17156
> URL: https://issues.apache.org/jira/browse/AMBARI-17156
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: rb48526.patch
>
>
> Unit Test failures in TestActionQueue.py and TestRecoveryManager.py:
> {code}
> ==
> ERROR: test_auto_execute_command (TestActionQueue.TestActionQueue)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", line 
> 407, in test_auto_execute_command
> dummy_controller.recovery_manager.update_config(5, 5, 1, 11, True, False, 
> "", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_execute_retryable_command_with_time_lapse 
> (TestActionQueue.TestActionQueue)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", line 
> 1002, in test_execute_retryable_command_with_time_lapse
> actionQueue.execute_command(command)
>   File "~/ambari/ambari-agent/src/main/python/ambari_agent/ActionQueue.py", 
> line 436, in execute_command
> self.controller.recovery_manager.get_current_status(command['role']))
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1165, in info
> self._log(INFO, msg, args, **kwargs)
> Revert "AMBARI-16935: Retry and recover from component install failures"
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1283, in _log
> record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, 
> func, extra)
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1257, in makeRecord
> rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 248, in __init__
> ct = time.time()
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 953, in 
> __call__
> return _mock_self._mock_call(*args, **kwargs)
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1011, in 
> _mock_call
> result = next(effect)
> StopIteration
> ==
> ERROR: test_process_commands (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
> line 144, in test_process_commands
> rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_recovery_required (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
> line 245, in test_recovery_required
> rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
> TypeError: update_config() takes exactly 10

[jira] [Commented] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired


[ 
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323769#comment-15323769
 ] 

Hadoop QA commented on AMBARI-17129:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12809321/AMBARI-17129.002.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.agent.TestHeartbeatHandler

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7285//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7285//console

This message is automatically generated.

> Set necessary HBase configuration to enable SPNEGO authentication if desired
> 
>
> Key: AMBARI-17129
> URL: https://issues.apache.org/jira/browse/AMBARI-17129
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch
>
>
> Over in HBASE-5291, I implemented support to enable SPNEGO authentication of 
> the HBase web UIs.
> We should update the HBase configuration when Kerberos is enabled such that, 
> if the user chooses to enable the SPNEGO auth, the principal and keytab 
> information is already present in the configuration. If the SPNEGO auth is 
> not enabled, then these properties won't affect anything if they are set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17157) Storm 1.0 log4j config update

2016-06-09 Thread Sriharsha Chintalapani (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sriharsha Chintalapani updated AMBARI-17157:

Attachment: AMBARI-17157.patch

> Storm 1.0 log4j config update
> -
>
> Key: AMBARI-17157
> URL: https://issues.apache.org/jira/browse/AMBARI-17157
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
> Fix For: 2.4.0
>
> Attachments: AMBARI-17157.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17157) Storm 1.0 log4j config update

2016-06-09 Thread Sriharsha Chintalapani (JIRA)

Sriharsha Chintalapani created AMBARI-17157:
---

 Summary: Storm 1.0 log4j config update
 Key: AMBARI-17157
 URL: https://issues.apache.org/jira/browse/AMBARI-17157
 Project: Ambari
  Issue Type: Bug
Reporter: Sriharsha Chintalapani
Assignee: Sriharsha Chintalapani
 Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16715) Wrong memory conf in spark-env.xml


[ 
https://issues.apache.org/jira/browse/AMBARI-16715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323694#comment-15323694
 ] 

Hudson commented on AMBARI-16715:
-

FAILURE: Integrated in Ambari-trunk-Commit #5047 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5047/])
AMBARI-16715. Wrong memory conf in spark-env.xml (Weiqing Yang via (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b116fb28db774bb30a2d0c8e2f070e3b7c6d55d])
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/configuration/spark-env.xml
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-env.xml


> Wrong memory conf in spark-env.xml
> --
>
> Key: AMBARI-16715
> URL: https://issues.apache.org/jira/browse/AMBARI-16715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
> Environment: spark_2_2_4_15_9-master-1.2.1.2.2.4.15-9.el6.noarch
> spark_2_2_4_15_9-python-1.2.1.2.2.4.15-9.el6.noarch
> spark_2_2_4_15_9-worker-1.2.1.2.2.4.15-9.el6.noarch
> spark_2_2_4_15_9-1.2.1.2.2.4.15-9.el6.noarch
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
>Priority: Minor
> Fix For: trunk, ambari-2.4.0
>
> Attachments: 
> 0001-AMBARI-16715-Wrong-memory-conf-in-spark-env.xml.patch, 
> AMBARI-16715_v2.patch
>
>
> In spark-env.xml, the memory value should not have space and a extra "b" 
> character. "SPARK_DRIVER_MEMORY="512 Mb" #Memory for Master (e.g. 1000M, 2G) 
> (Default: 512 Mb)", by default this line is commented but in case user 
> uncommented it to change the memory settings then it will show a below error, 
> so it's better to change it in the default template.
> Error:
> ./bin/spark-shell
> Error: Could not find or load main class Mb



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16949) Metrics Collector API shows NPE if we use wildcard (%25 for '%') for metric name

2016-06-09 Thread Jungtaek Lim (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323688#comment-15323688
 ] 

Jungtaek Lim commented on AMBARI-16949:
---

[~avijayan]
Thanks for merging this!

> Metrics Collector API shows NPE if we use wildcard (%25 for '%') for metric 
> name
> 
>
> Key: AMBARI-16949
> URL: https://issues.apache.org/jira/browse/AMBARI-16949
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
> Attachments: AMBARI-16949-trunk-v1.patch
>
>
> When we request '/ws/v1/timeline/metrics' with metric name which contains %25 
> (escaped '%'), response for the API is json describing there's NPE.
> And NPE is logged for ambari-metrics-collector log file.
> {code}
> 2016-05-30 09:15:05,061 WARN 
> org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR
> java.lang.NullPointerException
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.appendAggregateMetricFromResultSet(PhoenixHBaseAccessor.java:810)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.getAggregateMetricRecords(PhoenixHBaseAccessor.java:772)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.getTimelineMetrics(HBaseTimelineMetricStore.java:178)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:372)
>   at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
> {code}
> Reason of NPE: 
> Metrics are properly fetched with wildcard. But when applying functions to 
> result set, actual metric name is not exist from map of metric name to list 
> of function.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-17133) Replace underscore character from Storm metrics sink

2016-06-09 Thread Jungtaek Lim (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jungtaek Lim resolved AMBARI-17133.
---
   Resolution: Fixed
Fix Version/s: 2.4.0

Closing this as 'Fixed' since AMBARI-16946 is merged.

> Replace underscore character from Storm metrics sink
> 
>
> Key: AMBARI-17133
> URL: https://issues.apache.org/jira/browse/AMBARI-17133
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
>
> Since Ambari Metric Service uses "._" as separator for splitting metric and 
> functions, metric name shouldn't contain "._".
> Storm built-in metrics have metric names starting on '__' and with 
> AMBARI-16946 metric name is placed after '.' which finally makes '._' which 
> makes parsing messed up.
> We should remove '_' characters from metric name or replace them with '-' or 
> alike.
> (Replacing is more safer way if we replace them with special character.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16946) Storm Metrics Sink has high chance to discard some datapoints

2016-06-09 Thread Jungtaek Lim (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323685#comment-15323685
 ] 

Jungtaek Lim commented on AMBARI-16946:
---

[~avijayan] 
Thanks for merging this!
Btw, How can I assign issue to myself or be assigned to issue? I guess project 
permission for Ambari prevents me to be assigned issue. 
Could you help me to be registered as contributor group? Or should I write a 
request mail to dev@ list?

> Storm Metrics Sink has high chance to discard some datapoints
> -
>
> Key: AMBARI-16946
> URL: https://issues.apache.org/jira/browse/AMBARI-16946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
> Attachments: AMBARI-16946-trunk-v2.patch, AMBARI-16946-trunk-v3.patch
>
>
> There's a mismatch between TimelineMetricsCache and Storm metrics unit, while 
> TimelineMetricsCache considers "metric name + timestamp" to be unique but 
> Storm is not.
> For example, assume that bolt B has task T1, T2 and B has registered metrics 
> M1. It's possible for metrics sink to receive (T1, M1) and (T2, M1) with same 
> timestamp TS1 (in TaskInfo, not current time), and received later will be 
> discarded from TimelineMetricsCache.
> If we want to have unique metric point of Storm, we should use "topology name 
> + component name + task id + metric name" to metric name so that "metric name 
> + timestamp" will be unique.
> There're other issues I would like to address, too.
> - Currently, hostname is written to hostname of the machine which runs 
> metrics sink. Since TaskInfo has hostname of the machine which runs task, 
> we're better to use this.
> - Unit of timestamp of TaskInfo is second, while Storm Metrics Sink uses this 
> as millisecond, resulting in timestamp flaw, and malfunction of cache 
> eviction. It should be multiplied by 1000.
> - 'component name' is not unique across the cluster, so it's not fit for app 
> id. 'topology name' is unique so proper value of app id is topology name. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired


[ 
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323660#comment-15323660
 ] 

Hadoop QA commented on AMBARI-17129:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12809303/AMBARI-17129.001.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.upgrade.UpgradeCatalog240Test

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7284//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7284//console

This message is automatically generated.

> Set necessary HBase configuration to enable SPNEGO authentication if desired
> 
>
> Key: AMBARI-17129
> URL: https://issues.apache.org/jira/browse/AMBARI-17129
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch
>
>
> Over in HBASE-5291, I implemented support to enable SPNEGO authentication of 
> the HBase web UIs.
> We should update the HBase configuration when Kerberos is enabled such that, 
> if the user chooses to enable the SPNEGO auth, the principal and keytab 
> information is already present in the configuration. If the SPNEGO auth is 
> not enabled, then these properties won't affect anything if they are set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17074) Expose Spark daemon memory in Spark2

2016-06-09 Thread Weiqing Yang (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiqing Yang updated AMBARI-17074:
--
Priority: Major  (was: Minor)

> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Fix For: trunk, ambari-2.4.0
>
> Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17156) Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures

2016-06-09 Thread Nahappan Somasundaram (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-17156:
---
Status: Patch Available  (was: Open)

> Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests 
> failures
> 
>
> Key: AMBARI-17156
> URL: https://issues.apache.org/jira/browse/AMBARI-17156
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: rb48526.patch
>
>
> Unit Test failures in TestActionQueue.py and TestRecoveryManager.py:
> {code}
> ==
> ERROR: test_auto_execute_command (TestActionQueue.TestActionQueue)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", line 
> 407, in test_auto_execute_command
> dummy_controller.recovery_manager.update_config(5, 5, 1, 11, True, False, 
> "", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_execute_retryable_command_with_time_lapse 
> (TestActionQueue.TestActionQueue)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", line 
> 1002, in test_execute_retryable_command_with_time_lapse
> actionQueue.execute_command(command)
>   File "~/ambari/ambari-agent/src/main/python/ambari_agent/ActionQueue.py", 
> line 436, in execute_command
> self.controller.recovery_manager.get_current_status(command['role']))
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1165, in info
> self._log(INFO, msg, args, **kwargs)
> Revert "AMBARI-16935: Retry and recover from component install failures"
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1283, in _log
> record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, 
> func, extra)
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 1257, in makeRecord
> rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)
>   File 
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
>  line 248, in __init__
> ct = time.time()
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 953, in 
> __call__
> return _mock_self._mock_call(*args, **kwargs)
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1011, in 
> _mock_call
> result = next(effect)
> StopIteration
> ==
> ERROR: test_process_commands (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
> patched
> return func(*args, **keywargs)
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
> line 144, in test_process_commands
> rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_recovery_required (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
> line 245, in test_recovery_required
> rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
> TypeError: update_config() takes exactly 10 arguments (9 given)
> ==
> ERROR: test_recovery_required2 (TestRecoveryManager._TestRecoveryManager)
> --
> Traceback (most recent call last):
>   File 
> "~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py",

[jira] [Created] (AMBARI-17156) Ambari Agent: TestActionQueue and TestRecoveryManager python unit tests failures

2016-06-09 Thread Nahappan Somasundaram (JIRA)

Nahappan Somasundaram created AMBARI-17156:
--

 Summary: Ambari Agent: TestActionQueue and TestRecoveryManager 
python unit tests failures
 Key: AMBARI-17156
 URL: https://issues.apache.org/jira/browse/AMBARI-17156
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: 2.4.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Priority: Critical
 Fix For: 2.4.0


Unit Test failures in TestActionQueue.py and TestRecoveryManager.py:

{code}
==
ERROR: test_auto_execute_command (TestActionQueue.TestActionQueue)
--
Traceback (most recent call last):
  File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
patched
return func(*args, **keywargs)
  File "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", 
line 407, in test_auto_execute_command
dummy_controller.recovery_manager.update_config(5, 5, 1, 11, True, False, 
"", -1)
TypeError: update_config() takes exactly 10 arguments (9 given)

==
ERROR: test_execute_retryable_command_with_time_lapse 
(TestActionQueue.TestActionQueue)
--
Traceback (most recent call last):
  File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
patched
return func(*args, **keywargs)
  File "~/ambari/ambari-agent/src/test/python/ambari_agent/TestActionQueue.py", 
line 1002, in test_execute_retryable_command_with_time_lapse
actionQueue.execute_command(command)
  File "~/ambari/ambari-agent/src/main/python/ambari_agent/ActionQueue.py", 
line 436, in execute_command
self.controller.recovery_manager.get_current_status(command['role']))
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
 line 1165, in info
self._log(INFO, msg, args, **kwargs)
Revert "AMBARI-16935: Retry and recover from component install failures"
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
 line 1283, in _log
record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, 
func, extra)
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
 line 1257, in makeRecord
rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py",
 line 248, in __init__
ct = time.time()
  File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 953, in 
__call__
return _mock_self._mock_call(*args, **kwargs)
  File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1011, in 
_mock_call
result = next(effect)
StopIteration

==
ERROR: test_process_commands (TestRecoveryManager._TestRecoveryManager)
--
Traceback (most recent call last):
  File "~/ambari/ambari-common/src/test/python/mock/mock.py", line 1199, in 
patched
return func(*args, **keywargs)
  File 
"~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
line 144, in test_process_commands
rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
TypeError: update_config() takes exactly 10 arguments (9 given)

==
ERROR: test_recovery_required (TestRecoveryManager._TestRecoveryManager)
--
Traceback (most recent call last):
  File 
"~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
line 245, in test_recovery_required
rm.update_config(12, 5, 1, 15, True, False, "NODEMANAGER", -1)
TypeError: update_config() takes exactly 10 arguments (9 given)

==
ERROR: test_recovery_required2 (TestRecoveryManager._TestRecoveryManager)
--
Traceback (most recent call last):
  File 
"~/ambari/ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py", 
line 293, in test_recovery_required2
rm.update_config(15, 5, 1, 16, True, False, "NODEMANAGER", -1)
TypeError: update_config() takes exactly 10 arguments (9 given)

==
ERROR: test_sliding_window (TestRecoveryManager._TestRecoveryManager)
--
Traceback (most recent call last):
  File

[jira] [Commented] (AMBARI-17039) Takes long time to start or fail to start service after enabling SSL due to "dfs.https.enable"


[ 
https://issues.apache.org/jira/browse/AMBARI-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323627#comment-15323627
 ] 

Richard Zang commented on AMBARI-17039:
---

Thank you, Matt.

> Takes long time to start or fail to start service after enabling SSL due to 
> "dfs.https.enable"
> --
>
> Key: AMBARI-17039
> URL: https://issues.apache.org/jira/browse/AMBARI-17039
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17039.patch
>
>
> *SYMPTOM:*
> After enabling SSL on HDFS, starting services, such as YARN takes long time 
> because Ambari keeps checking http:// , not https://
> {noformat}
> 2016-06-02 23:07:22,221 - Getting jmx metrics from NN failed. URL: 
> http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
>  line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s 
> 'http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
>  1>/tmp/tmpOGkdi9 2>/tmp/tmpCUfr6B' returned 7. 
> 2016-06-02 23:07:24,506 - Getting jmx metrics from NN failed. URL: 
> http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
>  line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s 
> 'http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
>  1>/tmp/tmpDF9Kqb 2>/tmp/tmpBgbC4P' returned 7.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17134) Add support flag for user type 'JWT'


[ 
https://issues.apache.org/jira/browse/AMBARI-17134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323581#comment-15323581
 ] 

Hudson commented on AMBARI-17134:
-

FAILURE: Integrated in Ambari-trunk-Commit #5046 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5046/])
AMBARI-17134 - Add support flag for user type 'JWT' (rzang) (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4e2043de5e8f0661d9fda54e5fb16cd62d744cea])
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/app.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/remoteClusters/RemoteClustersListCtrl.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersListCtrl.js


> Add support flag for user type 'JWT'
> 
>
> Key: AMBARI-17134
> URL: https://issues.apache.org/jira/browse/AMBARI-17134
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17134.patch
>
>
> Add support flag for user type 'JWT'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.x


[ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323583#comment-15323583
 ] 

Hudson commented on AMBARI-17103:
-

FAILURE: Integrated in Ambari-trunk-Commit #5046 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5046/])
AMBARI-17103. Incorporating the inheritance logic for (sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=66decdeb25e0ca8666ba85a541c8a85b71fe4147])
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml
* 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_interactive.py


> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17117) Fix misnamed Zookeeper connect strings in Log Search

2016-06-09 Thread Miklos Gergely (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Miklos Gergely updated AMBARI-17117:

Summary: Fix misnamed Zookeeper connect strings in Log Search  (was: Fix 
misnamed Zookeeper connect strings)

> Fix misnamed Zookeeper connect strings in Log Search
> 
>
> Key: AMBARI-17117
> URL: https://issues.apache.org/jira/browse/AMBARI-17117
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
>
> Variables/properties holding zookeeper connect strings are misnamed as 
> zk_host, or zk_hosts, which may be misleading. Variable / property names 
> fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired

2016-06-09 Thread Josh Elser (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Elser updated AMBARI-17129:

Attachment: AMBARI-17129.002.patch

> Set necessary HBase configuration to enable SPNEGO authentication if desired
> 
>
> Key: AMBARI-17129
> URL: https://issues.apache.org/jira/browse/AMBARI-17129
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch
>
>
> Over in HBASE-5291, I implemented support to enable SPNEGO authentication of 
> the HBase web UIs.
> We should update the HBase configuration when Kerberos is enabled such that, 
> if the user chooses to enable the SPNEGO auth, the principal and keytab 
> information is already present in the configuration. If the SPNEGO auth is 
> not enabled, then these properties won't affect anything if they are set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17155) Accumulo Tracer principal causes OneFS permissions conflict

2016-06-09 Thread Robert Ketcherside (JIRA)

Robert Ketcherside created AMBARI-17155:
---

Summary: Accumulo Tracer principal causes OneFS permissions
conflict
Key: AMBARI-17155
URL: https://issues.apache.org/jira/browse/AMBARI-17155
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Environment: Ambari 2.2.2, HDP 2.4.2, OneFS 8.0.0.1
Reporter: Robert Ketcherside
Priority: Minor

The default principal for trace.user (tracer-${cluster-name}@${realm}) causes
Accumulo Tracer to be unable to start once Kerberos is enabled in an
environment where the NameNode and DataNode are an EMC/Isilon OneFS cluster.

Unlike the Apache NameNode, OneFS doesn't have a user-defined auto_to_local
mapping for principals to local users. It just takes the root of the principal
and looks for a local user of the same name.

Tracer uses its upn in order to auth to hdfs and read the value of the file
within the "instance_id" directory, and the name of the directory within
"version" under apps/accumulo/data. If these steps fail, the component dies.

Currently Isilon is advising customers to switch the principal name to
${accumulo-env/accumulo_user}@${realm}. The Accumulo user already has read
access to the contents of the data directory. (Hence, this issue is filed as
minor; there is a work around.)

An admin could also resolve the permissions issue for the tracer principal by
giving o+r permissions recursively to the accumulo directory; or by creating a
tracer user, adding it to a group like hadoop, and changing group ownership of
the apps/accumulo direcotry to o+r recursively.

I'm filing this JIRA to ask for a resolution to be investigated on the Apache
side. Here are a few ideas, though they might not be valid courses of action:
- Use an Accumulo upn or spn for kerberized trace.user. SPN is indicated as
default in the Accumulo manual,
https://accumulo.apache.org/1.7/accumulo_user_manual#_kerberos .
- Have Accumulo Tracer check hdfs as a different principal.
- Remove Accumulo Tracer's requirement to read information from the file system
as a prerequisite to service start.

See
https://community.emc.com/community/products/isilon/blog/2016/06/03/onefs-ambari-and-accumulo-tracer
for more details.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-16715) Wrong memory conf in spark-env.xml

2016-06-09 Thread Alejandro Fernandez (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-16715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez resolved AMBARI-16715.
--
Resolution: Fixed

Pushed to trunk, commit 9b116fb28db774bb30a2d0c8e2f070e3b7c6d55d
branch-2.4, commit 078833a360bd32c26349ba11b684f8344d173b84

> Wrong memory conf in spark-env.xml
> --
>
> Key: AMBARI-16715
> URL: https://issues.apache.org/jira/browse/AMBARI-16715
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
> Environment: spark_2_2_4_15_9-master-1.2.1.2.2.4.15-9.el6.noarch
> spark_2_2_4_15_9-python-1.2.1.2.2.4.15-9.el6.noarch
> spark_2_2_4_15_9-worker-1.2.1.2.2.4.15-9.el6.noarch
> spark_2_2_4_15_9-1.2.1.2.2.4.15-9.el6.noarch
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
>Priority: Minor
> Fix For: trunk, ambari-2.4.0
>
> Attachments: 
> 0001-AMBARI-16715-Wrong-memory-conf-in-spark-env.xml.patch, 
> AMBARI-16715_v2.patch
>
>
> In spark-env.xml, the memory value should not have space and a extra "b" 
> character. "SPARK_DRIVER_MEMORY="512 Mb" #Memory for Master (e.g. 1000M, 2G) 
> (Default: 512 Mb)", by default this line is commented but in case user 
> uncommented it to change the memory settings then it will show a below error, 
> so it's better to change it in the default template.
> Error:
> ./bin/spark-shell
> Error: Could not find or load main class Mb



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17149) HadoopTimelineMetricsSink from AMS prevents process shutdown


[ 
https://issues.apache.org/jira/browse/AMBARI-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323493#comment-15323493
 ] 

Hadoop QA commented on AMBARI-17149:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809286/AMBARI-17149.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-metrics/ambari-metrics-hadoop-sink.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7282//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7282//console

This message is automatically generated.

> HadoopTimelineMetricsSink from AMS prevents process shutdown
> 
>
> Key: AMBARI-17149
> URL: https://issues.apache.org/jira/browse/AMBARI-17149
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17149.patch
>
>
> HadoopTimelineMetricsSink has and ExecutorService thread which is not a 
> daemon thread. The executor is not shutdown, and thread is not interrupted 
> while the sink stops. This causes region server process to hang although the 
> rest of the threads have all exited.
> The new thread should be marked as a daemon thread, and also call shutdown() 
> or shutdownNow() on the executor in sink close.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17154) Typo in SmartSense Warning Dialog


 [ 
https://issues.apache.org/jira/browse/AMBARI-17154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zang updated AMBARI-17154:
--
Attachment: AMBARI-17154.patch

> Typo in SmartSense Warning Dialog
> -
>
> Key: AMBARI-17154
> URL: https://issues.apache.org/jira/browse/AMBARI-17154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17154.patch
>
>
> Change suggestion text to:
> SmartSense securely collects cluster diagnostics in order to send you 
> recommendations and automate analysis for troubleshooting support cases. If 
> you choose not to install SmartSense, you will not receive any 
> recommendations, and you will need to collect configuration and logs manually 
> for troubleshooting support cases. Are you sure you want to proceed without 
> SmartSense?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17054) Configure Atlas Ranger Plugin


[ 
https://issues.apache.org/jira/browse/AMBARI-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323465#comment-15323465
 ] 

Hadoop QA commented on AMBARI-17054:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809215/AMBARI-17054.3.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7281//console

This message is automatically generated.

> Configure Atlas Ranger Plugin
> -
>
> Key: AMBARI-17054
> URL: https://issues.apache.org/jira/browse/AMBARI-17054
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-17054.1.patch, AMBARI-17054.2.patch, 
> AMBARI-17054.3.patch, AMBARI-17054_trunk.1.patch, AMBARI-17054_trunk.patch
>
>
> Need to do following changes to support Ranger Atlas Plugin from Ambari: 
> 1) Check stack support  and provide smart config section to Enable / disable 
> ranger atlas plugin
> 2) Stack advisor changes to suggest recommended configs on enable / disable 
> plugin actions. 
> 3) Ranger service creation on Enable plugin action from Ambari. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17154) Typo in SmartSense Warning Dialog

Richard Zang created AMBARI-17154:
-

 Summary: Typo in SmartSense Warning Dialog
 Key: AMBARI-17154
 URL: https://issues.apache.org/jira/browse/AMBARI-17154
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Richard Zang
Assignee: Richard Zang
 Fix For: 2.4.0


Change suggestion text to:

SmartSense securely collects cluster diagnostics in order to send you 
recommendations and automate analysis for troubleshooting support cases. If you 
choose not to install SmartSense, you will not receive any recommendations, and 
you will need to collect configuration and logs manually for troubleshooting 
support cases. Are you sure you want to proceed without SmartSense?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17153) org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost fails intermittently on trunk.


 [ 
https://issues.apache.org/jira/browse/AMBARI-17153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-17153:
---
Affects Version/s: (was: 2.4.0)

> org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost
>  fails intermittently on trunk.
> -
>
> Key: AMBARI-17153
> URL: https://issues.apache.org/jira/browse/AMBARI-17153
> Project: Ambari
>  Issue Type: Bug
>Reporter: Aravindan Vijayan
>Priority: Critical
>
> Error Message
> expected:<1> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<2>
>   at 
> org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost(ClusterTest.java:2375)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17153) org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost fails intermittently on trunk.


 [ 
https://issues.apache.org/jira/browse/AMBARI-17153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-17153:
---
Fix Version/s: (was: 2.4.0)

> org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost
>  fails intermittently on trunk.
> -
>
> Key: AMBARI-17153
> URL: https://issues.apache.org/jira/browse/AMBARI-17153
> Project: Ambari
>  Issue Type: Bug
>Reporter: Aravindan Vijayan
>Priority: Critical
>
> Error Message
> expected:<1> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<2>
>   at 
> org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost(ClusterTest.java:2375)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17153) org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost fails intermittently on trunk.

Aravindan Vijayan created AMBARI-17153:
--

 Summary: 
org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost
 fails intermittently on trunk.
 Key: AMBARI-17153
 URL: https://issues.apache.org/jira/browse/AMBARI-17153
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Aravindan Vijayan
Assignee: Mahadev konar
Priority: Critical
 Fix For: 2.4.0


Error Message

expected:<1> but was:<2>
Stacktrace

java.lang.AssertionError: expected:<1> but was:<2>
at 
org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost(ClusterTest.java:2375)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17153) org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost fails intermittently on trunk.


 [ 
https://issues.apache.org/jira/browse/AMBARI-17153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-17153:
---
Assignee: (was: Mahadev konar)

> org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost
>  fails intermittently on trunk.
> -
>
> Key: AMBARI-17153
> URL: https://issues.apache.org/jira/browse/AMBARI-17153
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
>
> Error Message
> expected:<1> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<2>
>   at 
> org.apache.ambari.server.state.cluster.ClusterTest.testTransitionNonReportableHost(ClusterTest.java:2375)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired

2016-06-09 Thread Josh Elser (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Elser updated AMBARI-17129:

Status: Patch Available  (was: Open)

> Set necessary HBase configuration to enable SPNEGO authentication if desired
> 
>
> Key: AMBARI-17129
> URL: https://issues.apache.org/jira/browse/AMBARI-17129
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17129.001.patch
>
>
> Over in HBASE-5291, I implemented support to enable SPNEGO authentication of 
> the HBase web UIs.
> We should update the HBase configuration when Kerberos is enabled such that, 
> if the user chooses to enable the SPNEGO auth, the principal and keytab 
> information is already present in the configuration. If the SPNEGO auth is 
> not enabled, then these properties won't affect anything if they are set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17130) Duplicate key in database exception during version registration


[ 
https://issues.apache.org/jira/browse/AMBARI-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323423#comment-15323423
 ] 

Hadoop QA commented on AMBARI-17130:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809216/AMBARI-17130.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7280//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7280//console

This message is automatically generated.

> Duplicate key in database exception during version registration
> ---
>
> Key: AMBARI-17130
> URL: https://issues.apache.org/jira/browse/AMBARI-17130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17130.patch
>
>
> Need the ability to set the display name on VDF creation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-16101) clean up import * at common-services level

2016-06-09 Thread Juanjo Marron (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Juanjo Marron resolved AMBARI-16101.

Resolution: Fixed

> clean up import * at common-services level
> --
>
> Key: AMBARI-16101
> URL: https://issues.apache.org/jira/browse/AMBARI-16101
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.2.1
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 3.0.0
>
>
> Python code at  at common-services level used generic imports  form   
> resource_management (from resource_management import *)
> Ideally, for easier code tracking and performance, these import should be 
> more specific, such as: 
> from resource_management.libraries.script.script import Script
> from resource_management.core.resources.system import Directory
> This JIRA and subtasks will clean up import * from resource_management and 
> replace it for specific imports



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17144) Atlas Integration : Required changes for atlas-application.properties


[ 
https://issues.apache.org/jira/browse/AMBARI-17144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323400#comment-15323400
 ] 

Hudson commented on AMBARI-17144:
-

FAILURE: Integrated in Ambari-trunk-Commit #5045 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5045/])
AMBARI-17144 - Atlas Integration : Required changes for (tbeerbower: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f42b258042dd51b030dcb7d21815234c37da9474])
* ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/kerberos.json
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml


> Atlas Integration : Required changes for atlas-application.properties
> -
>
> Key: AMBARI-17144
> URL: https://issues.apache.org/jira/browse/AMBARI-17144
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Changes in ATLAS-820 require following configurations to be present in 
> atlas-application.properties:
> {code}
> atlas.authentication.method.kerberos=false
> atlas.authentication.method.file=true
> atlas.authentication.method.ldap=false
> atlas.authentication.method.file.filename={{atlas_login_credentials_file}}
> atlas.authentication.method.ldap.type=ldap|ad
> atlas.authentication.method.ldap.url=
> {code}
>  
> When Kerberos is enabled, following configurations need to be set/added:
> {code}
> atlas.authentication.method.kerberos=true
> atlas.authentication.method.kerberos.keytab=/etc/security/keytabs/spnego.service.keytab
> atlas.authentication.method.kerberos.principal=HTTP/_h...@example.com
> atlas.authentication.method.kerberos.name.rules=
> atlas.kafka.sasl.kerberos.service.name=kafka
> atlas.kafka.security.protocol=SASL_PLAINTEXT
> atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
> atlas.jaas.KafkaClient.loginModuleControlFlag=required
> atlas.jaas.KafkaClient.option.useKeyTab=true
> atlas.jaas.KafkaClient.option.storeKey=true
> atlas.jaas.KafkaClient.option.serviceName=kafka
> atlas.jaas.KafkaClient.option.keyTab={{atlas_keytab_path}}
> atlas.jaas.KafkaClient.option.principal={{atlas_jaas_principal}}
> {code} 
> Following properties are no more used and need to be removed:
> {code}
> atlas.http.authentication.enabled
> atlas.http.authentication.kerberos.keytab
> atlas.http.authentication.type
> atlas.http.authentication.kerberos.principal
> atlas.http.authentication.kerberos.name.rules
> atlas.login.method=
> atlas.login.credentials.file=
> {code} 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml


 [ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-17103:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-s


[ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323387#comment-15323387
 ] 

Swapan Shridhar edited comment on AMBARI-17103 at 6/9/16 9:24 PM:
--

commits :

trunk:

{code}
commit 66decdeb25e0ca8666ba85a541c8a85b71fe4147
Author: Swapan Shridhar 
Date:   Thu Jun 9 12:32:48 2016 -0700

AMBARI-17103. Incorporating the inheritance logic for 
tez_hive2/tez-interactive-site.xml using tez/tez-site.xml. Also, removing 
'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via 
inheritance from hive/hive-site.xml.
{code}


branch-2.4:

{code}
commit 7e0efa8e1f87d4b0ad59ddaf9b0c7e1eacbef71b
Author: Swapan Shridhar 
Date:   Thu Jun 9 14:08:15 2016 -0700

AMBARI-17103. Incorporating the inheritance logic for 
tez_hive2/tez-interactive-site.xml using tez/tez-site.xml. Also, removing 
'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via 
inheritance from hive/hive-site.xml.
{code}



was (Author: swapanshridhar):
commits :

trunk:

{code}
commit 66decdeb25e0ca8666ba85a541c8a85b71fe4147
Author: Swapan Shridhar 
Date:   Thu Jun 9 12:32:48 2016 -0700

AMBARI-17103. Incorporating the inheritance logic for 
tez_hive2/tez-interactive-site.xml using tez/tez-site.xml. Also, removing 
'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via 
inheritance from hive/hive-site.xml.
{code}


branch-2.4:

{code}
commit 7e0efa8e1f87d4b0ad59ddaf9b0c7e1eacbef71b
Author: Swapan Shridhar 
Date:   Thu Jun 9 14:08:15 2016 -0700

AMBARI-17103. Incorporating the inheritance logic for 
tez_hive2/tez-interactive-site.xml using tez/tez-site.xml. Also, removing 
'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via 
inheritance from hive/hive-site.xml.
{code}


> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.x


[ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323387#comment-15323387
 ] 

Swapan Shridhar commented on AMBARI-17103:
--

commits :

trunk:

{code}
commit 66decdeb25e0ca8666ba85a541c8a85b71fe4147
Author: Swapan Shridhar 
Date:   Thu Jun 9 12:32:48 2016 -0700

AMBARI-17103. Incorporating the inheritance logic for 
tez_hive2/tez-interactive-site.xml using tez/tez-site.xml. Also, removing 
'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via 
inheritance from hive/hive-site.xml.
{code}


branch-2.4:

{code}
commit 7e0efa8e1f87d4b0ad59ddaf9b0c7e1eacbef71b
Author: Swapan Shridhar 
Date:   Thu Jun 9 14:08:15 2016 -0700

AMBARI-17103. Incorporating the inheritance logic for 
tez_hive2/tez-interactive-site.xml using tez/tez-site.xml. Also, removing 
'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via 
inheritance from hive/hive-site.xml.
{code}


> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17130) Duplicate key in database exception during version registration


 [ 
https://issues.apache.org/jira/browse/AMBARI-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-17130:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Duplicate key in database exception during version registration
> ---
>
> Key: AMBARI-17130
> URL: https://issues.apache.org/jira/browse/AMBARI-17130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17130.patch
>
>
> Need the ability to set the display name on VDF creation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17152) Cannot remove default alerts from Critical Alerts

2016-06-09 Thread Vivek Madani (JIRA)

Vivek Madani created AMBARI-17152:
-

 Summary: Cannot remove default alerts from Critical Alerts 
 Key: AMBARI-17152
 URL: https://issues.apache.org/jira/browse/AMBARI-17152
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.1.1
Reporter: Vivek Madani


While trying to remove Smartsense and ambari-metrics alerts from the critical 
alerts group, ambari-server throws 500 Internal Server error with following 
exception being seen in the logs:

09 Jun 2016 21:04:45,062  WARN [qtp-client-131636] ServletHandler:563 - 
/api/v1/alert_targets/1
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429)
at java.util.HashMap$KeyIterator.next(HashMap.java:1453)
at 
org.apache.ambari.server.orm.entities.AlertTargetEntity.setAlertGroups(AlertTargetEntity.java:275)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider.updateAlertTargets(AlertTargetResourceProvider.java:412)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider.access$100(AlertTargetResourceProvider.java:65)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider$2.invoke(AlertTargetResourceProvider.java:194)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider$2.invoke(AlertTargetResourceProvider.java:181)
at 
org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:330)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider.updateResources(AlertTargetResourceProvider.java:181)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:310)
at 
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:104)
at 
org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:42)
at 
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
at 
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:105)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
at 
org.apache.ambari.server.api.services.AlertTargetService.updateGroup(AlertTargetService.java:76)
at sun.reflect.GeneratedMethodAccessor16393.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at

[jira] [Created] (AMBARI-17151) Blueprint deployments fail when services manually removed from stack definitions

2016-06-09 Thread Robert Nettleton (JIRA)

Robert Nettleton created AMBARI-17151:
-

 Summary: Blueprint deployments fail when services manually removed 
from stack definitions
 Key: AMBARI-17151
 URL: https://issues.apache.org/jira/browse/AMBARI-17151
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
Priority: Critical
 Fix For: 2.4.0


In certain custom use cases, an Ambari user may choose to customize the Ambari 
stack definitions by manually removing services.  

This can cause some failures during a Blueprint deployment, particularly in the 
area of "excluded" configurations.  

When an "excluded" configuration type is found, the Blueprint processor 
attempts to add this configuration, and queries the Stack APIs to determine the 
service associated with this configuration type. 

If this particular service has been manually deleted from the stacks, the Stack 
APIs will throw a runtime exception, which causes the entire Blueprint 
deployment to fail. 

Example: 

If Ambari Metrics is included in a Blueprint, the "storm-site" configuration 
type is considered an "excluded-configuration" by the stack definitions.  In 
this case, if the "STORM" service definitions have been removed, then the 
following exception will result when a cluster deployment based on a Blueprint 
is attempted:

java.lang.IllegalArgumentException: Specified configuration type is not 
associated with any service: storm-site
at 
org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:485)
at 
org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.addExcludedConfigProperties(BlueprintConfigurationProcessor.java:2781)
at 
org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.setMissingConfigurations(BlueprintConfigurationProcessor.java:2751)
at 
org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:335)
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:153)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:780)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:754)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
...



In these custom deployments, the Blueprints processor should be more lenient 
with respect to error handling.  

If a matching service is not found for a given "excluded" configuration type, 
the Blueprint processor should log this as a WARNING, indicating that the 
stacks have likely been modified outside of Ambari.  

I'm working on a fix for this, and will be submitting a patch soon.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17149) HadoopTimelineMetricsSink from AMS prevents process shutdown


 [ 
https://issues.apache.org/jira/browse/AMBARI-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-17149:
---
Status: Patch Available  (was: Open)

> HadoopTimelineMetricsSink from AMS prevents process shutdown
> 
>
> Key: AMBARI-17149
> URL: https://issues.apache.org/jira/browse/AMBARI-17149
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17149.patch
>
>
> HadoopTimelineMetricsSink has and ExecutorService thread which is not a 
> daemon thread. The executor is not shutdown, and thread is not interrupted 
> while the sink stops. This causes region server process to hang although the 
> rest of the threads have all exited.
> The new thread should be marked as a daemon thread, and also call shutdown() 
> or shutdownNow() on the executor in sink close.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17149) HadoopTimelineMetricsSink from AMS prevents process shutdown


 [ 
https://issues.apache.org/jira/browse/AMBARI-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-17149:
---
Attachment: AMBARI-17149.patch

> HadoopTimelineMetricsSink from AMS prevents process shutdown
> 
>
> Key: AMBARI-17149
> URL: https://issues.apache.org/jira/browse/AMBARI-17149
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17149.patch
>
>
> HadoopTimelineMetricsSink has and ExecutorService thread which is not a 
> daemon thread. The executor is not shutdown, and thread is not interrupted 
> while the sink stops. This causes region server process to hang although the 
> rest of the threads have all exited.
> The new thread should be marked as a daemon thread, and also call shutdown() 
> or shutdownNow() on the executor in sink close.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17150) Ambari Metrics components packages do not have vendor before upgrade, but for new versions it appears [Upgrade]

Aravindan Vijayan created AMBARI-17150:
--

 Summary: Ambari Metrics components packages do not have vendor 
before upgrade, but for new versions it appears [Upgrade]
 Key: AMBARI-17150
 URL: https://issues.apache.org/jira/browse/AMBARI-17150
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.4.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
 Fix For: 2.4.0


In 2.3.0 (i.e 2.4.0), changes were made to ambari-metrics project's pom.xml 
such that it's parent project is Ambari. AMS pom.xml did not have any Vendor 
(organization) information, and hence it inherited from Ambari project ('Apache 
Software Foundation'). Hence, the released AMS packages have no Vendor and the 
new ones will have it thus causing upgrade command to fail

{code}
suse1101:~ # zypper up ambari-metrics-hadoop-sink
Loading repository data...
Reading installed packages...
There is an update candidate for 'ambari-metrics-hadoop-sink', but it is from 
different vendor. Use 'zypper install 
ambari-metrics-hadoop-sink-2.4.0.0-569.x86_64' to install this candidate.
Resolving package dependencies...

Nothing to do.
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17134) Add support flag for user type 'JWT'


 [ 
https://issues.apache.org/jira/browse/AMBARI-17134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zang updated AMBARI-17134:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk 4e2043de5e8f0661d9fda54e5fb16cd62d744cea

> Add support flag for user type 'JWT'
> 
>
> Key: AMBARI-17134
> URL: https://issues.apache.org/jira/browse/AMBARI-17134
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17134.patch
>
>
> Add support flag for user type 'JWT'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17149) HadoopTimelineMetricsSink from AMS prevents process shutdown

Aravindan Vijayan created AMBARI-17149:
--

 Summary: HadoopTimelineMetricsSink from AMS prevents process 
shutdown
 Key: AMBARI-17149
 URL: https://issues.apache.org/jira/browse/AMBARI-17149
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.4.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
 Fix For: 2.4.0


HadoopTimelineMetricsSink has and ExecutorService thread which is not a daemon 
thread. The executor is not shutdown, and thread is not interrupted while the 
sink stops. This causes region server process to hang although the rest of the 
threads have all exited.

The new thread should be marked as a daemon thread, and also call shutdown() or 
shutdownNow() on the executor in sink close.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-17033) Metrics call from applications deployed by Ambari Slider View return exception


 [ 
https://issues.apache.org/jira/browse/AMBARI-17033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan resolved AMBARI-17033.

Resolution: Not A Bug

> Metrics call from applications deployed by Ambari Slider View return exception
> --
>
> Key: AMBARI-17033
> URL: https://issues.apache.org/jira/browse/AMBARI-17033
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: thomas liu
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
>
> Thanks for your attention.
> Currently, I deployed an application through  Ambari Slider View with metrics 
> enabled.
> However, the metric graphs are not showing up on the page.
> Using Chrome network tab to debug the metrics API calls, the response looks 
> like:
> {
>   "href" : 
> "http://[ambari-server-host]:8080/api/v1/views/SLIDER/versions/2.0.0/instances/test/apps/1463...;,
>   "id" : "1463003744042_207",
>   "instance_name" : "test",
>   "version" : "2.0.0",
>   "view_name" : "SLIDER"
> }
> So I read the ambari-server.log, and found those related exceptions:
> {noformat}
> 03 Jun 2016 10:35:37,006  WARN [qtp-ambari-client-8928] ServletHandler:563 - 
> /api/v1/views/SLIDER/versions/2.0.0/instances/test/apps/1464907776624_19
> java.lang.RuntimeException: Unable to serialize to json: 
> org.codehaus.jackson.JsonGenerationException: Can not write a field name, 
> expecting a value
> at 
> org.apache.ambari.server.api.services.serializers.JsonSerializer.serialize(JsonSerializer.java:71)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:114)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at 
> org.apache.ambari.server.api.services.ViewSubResourceService.handleRequest(ViewSubResourceService.java:85)
> at 
> org.apache.ambari.view.slider.rest.SliderAppsResource.getApp(SliderAppsResource.java:94)
> at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
>

[jira] [Updated] (AMBARI-17074) Expose Spark daemon memory in Spark2

2016-06-09 Thread Weiqing Yang (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiqing Yang updated AMBARI-17074:
--
Attachment: AMBARI-17074_v2.patch

> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
>Priority: Minor
> Fix For: trunk, ambari-2.4.0
>
> Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml


 [ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-17103:
-
Attachment: (was: AMBARI-17103.patch)

> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml


 [ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-17103:
-
Status: Open  (was: Patch Available)

> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml


 [ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-17103:
-
Attachment: AMBARI-17103.patch

> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml


 [ 
https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-17103:
-
Status: Patch Available  (was: Open)

> Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" 
> using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from 
> hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml
> ---
>
> Key: AMBARI-17103
> URL: https://issues.apache.org/jira/browse/AMBARI-17103
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17103.patch
>
>
> - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we 
> will do the inheritance for other Tez properties from tez/tez-site.xml.
> - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it 
> would be got via inheritance from hive/hive-site.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17146) Implement config values trimming for deployment via blueprint


[ 
https://issues.apache.org/jira/browse/AMBARI-17146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323185#comment-15323185
 ] 

Hadoop QA commented on AMBARI-17146:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809203/AMBARI-17146_1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.controller.internal.StackTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7279//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7279//console

This message is automatically generated.

> Implement config values trimming for deployment via blueprint
> -
>
> Key: AMBARI-17146
> URL: https://issues.apache.org/jira/browse/AMBARI-17146
> Project: Ambari
>  Issue Type: Task
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17146_1.patch
>
>
> Implement config values trimming for deployment via blueprint as we do in UI
> {code}
>   trimProperty: function (property) {
> var displayType = Em.get(property, 'displayType');
> var value = Em.get(property, 'value');
> var name = Em.get(property, 'name');
> var rez;
> switch (displayType) {
>   case 'directories':
>   case 'directory':
> rez = value.replace(/,/g, ' ').trim().split(/\s+/g).join(',');
> break;
>   case 'host':
> rez = value.trim();
> break;
>   case 'password':
> break;
>   default:
> if (name == 'javax.jdo.option.ConnectionURL' || name == 
> 'oozie.service.JPAService.jdbc.url') {
>   rez = value.trim();
> }
> rez = (typeof value == 'string') ? value.replace(/(\s+$)/g, '') : 
> value;
> }
> return ((rez == '') || (rez == undefined)) ? value : rez;
>   },
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17127) Ambari Stale Alert Triggers For Server-Side Performance Alert


[ 
https://issues.apache.org/jira/browse/AMBARI-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323171#comment-15323171
 ] 

Hudson commented on AMBARI-17127:
-

FAILURE: Integrated in Ambari-trunk-Commit #5044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5044/])
AMBARI-17127 - Ambari Stale Alert Triggers For Server-Side Performance 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4aa1639b4892b0faeedb4b9df4c6c7ac2b20d299])
* 
ambari-server/src/test/java/org/apache/ambari/server/alerts/StaleAlertRunnableTest.java
* ambari-server/src/main/resources/alerts.json
* 
ambari-server/src/main/java/org/apache/ambari/server/alerts/AmbariPerformanceRunnable.java
* ambari-server/src/main/java/org/apache/ambari/server/alerts/AlertRunnable.java
* 
ambari-server/src/main/java/org/apache/ambari/server/alerts/StaleAlertRunnable.java


> Ambari Stale Alert Triggers For Server-Side Performance Alert
> -
>
> Key: AMBARI-17127
> URL: https://issues.apache.org/jira/browse/AMBARI-17127
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.4.0
>
> Attachments: AMBARI-17127.patch, AMBARI-17127.patch
>
>
> If the Ambari Server is restarted after being down for several minutes, the 
> "Ambari Server Performance" alert will trigger as being stale. This is 
> because the {{StaleAlertRunnable}} is not checking to ensure that Ambari has 
> been up and running long enough to have run the alert.
> The {{StaleAlertRunnable}} should verify that the uptime of Ambari is greater 
> than staleness interval.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16949) Metrics Collector API shows NPE if we use wildcard (%25 for '%') for metric name


[ 
https://issues.apache.org/jira/browse/AMBARI-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323172#comment-15323172
 ] 

Hudson commented on AMBARI-16949:
-

FAILURE: Integrated in Ambari-trunk-Commit #5044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5044/])
AMBARI-16949 Metrics Collector API shows NPE if we use wildcard (%25 for 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=316a1811fe6b1374f7a7b2aa9d721f2366484b55])
* 
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java


> Metrics Collector API shows NPE if we use wildcard (%25 for '%') for metric 
> name
> 
>
> Key: AMBARI-16949
> URL: https://issues.apache.org/jira/browse/AMBARI-16949
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
> Attachments: AMBARI-16949-trunk-v1.patch
>
>
> When we request '/ws/v1/timeline/metrics' with metric name which contains %25 
> (escaped '%'), response for the API is json describing there's NPE.
> And NPE is logged for ambari-metrics-collector log file.
> {code}
> 2016-05-30 09:15:05,061 WARN 
> org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR
> java.lang.NullPointerException
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.appendAggregateMetricFromResultSet(PhoenixHBaseAccessor.java:810)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.getAggregateMetricRecords(PhoenixHBaseAccessor.java:772)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.getTimelineMetrics(HBaseTimelineMetricStore.java:178)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:372)
>   at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
> {code}
> Reason of NPE: 
> Metrics are properly fetched with wildcard. But when applying functions to 
> result set, actual metric name is not exist from map of metric name to list 
> of function.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16946) Storm Metrics Sink has high chance to discard some datapoints


[ 
https://issues.apache.org/jira/browse/AMBARI-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323170#comment-15323170
 ] 

Hudson commented on AMBARI-16946:
-

FAILURE: Integrated in Ambari-trunk-Commit #5044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5044/])
AMBARI-16946 Storm Metrics Sink has high chance to discard some (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=95426f795444df20fb4ee9ce087f9191f0a4868e])
* 
ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java
* 
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java


> Storm Metrics Sink has high chance to discard some datapoints
> -
>
> Key: AMBARI-16946
> URL: https://issues.apache.org/jira/browse/AMBARI-16946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
> Attachments: AMBARI-16946-trunk-v2.patch, AMBARI-16946-trunk-v3.patch
>
>
> There's a mismatch between TimelineMetricsCache and Storm metrics unit, while 
> TimelineMetricsCache considers "metric name + timestamp" to be unique but 
> Storm is not.
> For example, assume that bolt B has task T1, T2 and B has registered metrics 
> M1. It's possible for metrics sink to receive (T1, M1) and (T2, M1) with same 
> timestamp TS1 (in TaskInfo, not current time), and received later will be 
> discarded from TimelineMetricsCache.
> If we want to have unique metric point of Storm, we should use "topology name 
> + component name + task id + metric name" to metric name so that "metric name 
> + timestamp" will be unique.
> There're other issues I would like to address, too.
> - Currently, hostname is written to hostname of the machine which runs 
> metrics sink. Since TaskInfo has hostname of the machine which runs task, 
> we're better to use this.
> - Unit of timestamp of TaskInfo is second, while Storm Metrics Sink uses this 
> as millisecond, resulting in timestamp flaw, and malfunction of cache 
> eviction. It should be multiplied by 1000.
> - 'component name' is not unique across the cluster, so it's not fit for app 
> id. 'topology name' is unique so proper value of app id is topology name. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16916) clean up import * for SPARK2 service


[ 
https://issues.apache.org/jira/browse/AMBARI-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323173#comment-15323173
 ] 

Hudson commented on AMBARI-16916:
-

FAILURE: Integrated in Ambari-trunk-Commit #5044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5044/])
AMBARI-16916: clean up import * for SPARK2 service scripts in (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f4fbab1353a739622dd89f6a4275b9dffcad9e9c])
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/job_history_server.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/spark_client.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/service_check.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/status_params.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/spark_service.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/spark_thrift_server.py
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py


>  clean up import * for SPARK2 service
> -
>
> Key: AMBARI-16916
> URL: https://issues.apache.org/jira/browse/AMBARI-16916
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 3.0.0
>
> Attachments: AMBARI-16916.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17144) Atlas Integration : Required changes for atlas-application.properties

2016-06-09 Thread Tom Beerbower (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Beerbower updated AMBARI-17144:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Atlas Integration : Required changes for atlas-application.properties
> -
>
> Key: AMBARI-17144
> URL: https://issues.apache.org/jira/browse/AMBARI-17144
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Changes in ATLAS-820 require following configurations to be present in 
> atlas-application.properties:
> {code}
> atlas.authentication.method.kerberos=false
> atlas.authentication.method.file=true
> atlas.authentication.method.ldap=false
> atlas.authentication.method.file.filename={{atlas_login_credentials_file}}
> atlas.authentication.method.ldap.type=ldap|ad
> atlas.authentication.method.ldap.url=
> {code}
>  
> When Kerberos is enabled, following configurations need to be set/added:
> {code}
> atlas.authentication.method.kerberos=true
> atlas.authentication.method.kerberos.keytab=/etc/security/keytabs/spnego.service.keytab
> atlas.authentication.method.kerberos.principal=HTTP/_h...@example.com
> atlas.authentication.method.kerberos.name.rules=
> atlas.kafka.sasl.kerberos.service.name=kafka
> atlas.kafka.security.protocol=SASL_PLAINTEXT
> atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
> atlas.jaas.KafkaClient.loginModuleControlFlag=required
> atlas.jaas.KafkaClient.option.useKeyTab=true
> atlas.jaas.KafkaClient.option.storeKey=true
> atlas.jaas.KafkaClient.option.serviceName=kafka
> atlas.jaas.KafkaClient.option.keyTab={{atlas_keytab_path}}
> atlas.jaas.KafkaClient.option.principal={{atlas_jaas_principal}}
> {code} 
> Following properties are no more used and need to be removed:
> {code}
> atlas.http.authentication.enabled
> atlas.http.authentication.kerberos.keytab
> atlas.http.authentication.type
> atlas.http.authentication.kerberos.principal
> atlas.http.authentication.kerberos.name.rules
> atlas.login.method=
> atlas.login.credentials.file=
> {code} 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17148) Fix rm.audit.logger and nm.audit.logger configuration setting for Yarn

2016-06-09 Thread Yesha Vora (JIRA)

Yesha Vora created AMBARI-17148:
---

 Summary: Fix rm.audit.logger and nm.audit.logger configuration 
setting for Yarn
 Key: AMBARI-17148
 URL: https://issues.apache.org/jira/browse/AMBARI-17148
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Yesha Vora
Priority: Critical


Ambari sets RMAUDIT and NMAUDIT loggers by default for YARN. 
{code}rm.audit.logger=INFO,RMAUDIT
..
nm.audit.logger=INFO,NMAUDIT
..{code}

This config leads to log4j errors while running yarn-cli command. 
{code}
 yarn application -list
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /xx/nm-audit.log (No such file or directory)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:133)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:223)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
at 
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
at 
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
at 
org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672){code}

In YARN's case, rm.audit.logger should be set when starting RM only and 
nm.audit.logger when starting NMs only. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16916) clean up import * for SPARK2 service


 [ 
https://issues.apache.org/jira/browse/AMBARI-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-16916:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

>  clean up import * for SPARK2 service
> -
>
> Key: AMBARI-16916
> URL: https://issues.apache.org/jira/browse/AMBARI-16916
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 3.0.0
>
> Attachments: AMBARI-16916.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16916) clean up import * for SPARK2 service


[ 
https://issues.apache.org/jira/browse/AMBARI-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323116#comment-15323116
 ] 

Jayush Luniya commented on AMBARI-16916:


commit f4fbab1353a739622dd89f6a4275b9dffcad9e9c
Author: Jayush Luniya 
Date:   Thu Jun 9 10:45:49 2016 -0700

AMBARI-16916: clean up import * for SPARK2 service scripts in 
common-services (Juanjo Marron via jluniya)

>  clean up import * for SPARK2 service
> -
>
> Key: AMBARI-16916
> URL: https://issues.apache.org/jira/browse/AMBARI-16916
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 3.0.0
>
> Attachments: AMBARI-16916.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17147) LogSearch: solr_cloud_util.py: OSError: [Errno 1] Operation not permitted with non-root ambari agent user

2016-06-09 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/AMBARI-17147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivér Szabó updated AMBARI-17147:
--
Attachment: AMBARI-17147.patch

> LogSearch: solr_cloud_util.py: OSError: [Errno 1] Operation not permitted 
> with non-root ambari agent user
> -
>
> Key: AMBARI-17147
> URL: https://issues.apache.org/jira/browse/AMBARI-17147
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-17147.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17147) LogSearch: solr_cloud_util.py: OSError: [Errno 1] Operation not permitted with non-root ambari agent user

2016-06-09 Thread JIRA

Olivér Szabó created AMBARI-17147:
-

 Summary: LogSearch: solr_cloud_util.py: OSError: [Errno 1] 
Operation not permitted with non-root ambari agent user
 Key: AMBARI-17147
 URL: https://issues.apache.org/jira/browse/AMBARI-17147
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, ambari-server
Affects Versions: 2.4.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17074) Expose Spark daemon memory in Spark2

2016-06-09 Thread Weiqing Yang (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiqing Yang updated AMBARI-17074:
--
Attachment: AMBARI-17074.v1.patch

> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
>Priority: Minor
> Fix For: trunk, ambari-2.4.0
>
> Attachments: AMBARI-17074.v1.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17128) Cluster operator and ServiceAdministrator able to enable/disable/edit alert definitions


[ 
https://issues.apache.org/jira/browse/AMBARI-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322961#comment-15322961
 ] 

Hudson commented on AMBARI-17128:
-

FAILURE: Integrated in Ambari-trunk-Commit #5043 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5043/])
AMBARI-17128. Cluster operator and ServiceAdministrator able to (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4878a881bb5201a90bff0c2822b9e95afb8626b4])
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog230.java
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql


> Cluster operator and ServiceAdministrator able to enable/disable/edit alert 
> definitions
> ---
>
> Key: AMBARI-17128
> URL: https://issues.apache.org/jira/browse/AMBARI-17128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17128.patch
>
>
> Login to cluster using credentials of a cluster operator/ServiceAdministrator.
> Try moving to alerts page. Alerts are editable by cluster operator when it 
> shouldn't have been.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17142) RBAC: Roles show "empty" user after delete


[ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322962#comment-15322962
 ] 

Hudson commented on AMBARI-17142:
-

FAILURE: Integrated in Ambari-trunk-Commit #5043 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5043/])
AMBARI-17142. RBAC: Roles show "empty" user after delete (akovalenko) 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b599d192c12f9fbc57a686bc46228d1ca3aba506])
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/UserAccessListCtrl.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersShowCtrl.js


> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support


[ 
https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322960#comment-15322960
 ] 

Hudson commented on AMBARI-17112:
-

FAILURE: Integrated in Ambari-trunk-Commit #5043 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5043/])
AMBARI-17112. Fixed implementation of on-ambari-upgrade support. Patch 1 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9699f57d55c3305de2ae01290836caf60c41683e])
* ambari-server/src/main/java/org/apache/ambari/server/state/PropertyInfo.java
* 
ambari-server/src/main/resources/scripts/configurations-set-default-update-policy.sh
* 
ambari-server/src/test/java/org/apache/ambari/server/state/PropertyInfoTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/PropertyUpgradeBehavior.java
AMBARI-17112. Fixed implementation of on-ambari-upgrade support. Update 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4c5cf30eeea1d456f1cc79d888bc1b369ba5e683])
* 
ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/FLUME/configuration/flume-conf.xml
* 
ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/admin-log4j.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.0.5/services/MAPREDUCE2/configuration/mapred-site.xml
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/configuration/spark-env.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/configuration/storm-env.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/OOZIE/configuration/oozie-site.xml
* 
ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/capacity-scheduler.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HDFS/configuration/hadoop-policy.xml
* 
ambari-server/src/test/resources/stacks/HDP/0.1/services/HDFS/configuration/hbase-site.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/GLUSTERFS/configuration/core-site.xml
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-hive-site-override.xml
* 
ambari-server/src/main/resources/common-services/MAHOUT/1.0.0.2.3/configuration/mahout-log4j.xml
* 
ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/YARN/configuration-mapred/mapred-site.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/configuration/hive-env.xml
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-metrics-properties.xml
* 
ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HIVE/configuration/webhcat-site.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6.GlusterFS/services/HDFS/configuration/global.xml
* 
ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/mapred-site.xml
* 
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/ranger-kms-policymgr-ssl.xml
* 
ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HBASE/configuration/hbase-policy.xml
* 
ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/FALCON/configuration/falcon-env.xml
* 
ambari-server/src/main/resources/common-services/PXF/3.0.0/configuration/pxf-profiles.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/TEZ/configuration/tez-site.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
* 
ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HDFS/configuration/hdfs-site.xml
* 
ambari-server/src/test/resources/stacks/HDP/0.2/services/HDFS/configuration/global.xml
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-env.xml
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-log4j.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.0.5/services/MAPREDUCE2/configuration/global.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-site.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/STORM/configuration/storm-site.xml
* 
ambari-server/src/test/resources/TestAmbaryServer.samples/dummy_common_services/HIVE/0.11.0.2.0.5.0/configuration/hive-site.xml
* 
ambari-server/src/test/resources/stacks_with_cycle/OTHER/1.0/services/HDFS/configuration/hdfs-site.xml
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/llap-daemon-log4j.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml
* 
ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-worker-log4j.xml
*

[jira] [Commented] (AMBARI-17143) Ambari Admin: incorrect navigation behaviour


[ 
https://issues.apache.org/jira/browse/AMBARI-17143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322963#comment-15322963
 ] 

Hudson commented on AMBARI-17143:
-

FAILURE: Integrated in Ambari-trunk-Commit #5043 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5043/])
AMBARI-17143. Ambari Admin: incorrect navigation behaviour (akovalenko) 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6d97cba03238509990e840a2709d985525158ab8])
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/routes.js


> Ambari Admin: incorrect navigation behaviour
> 
>
> Key: AMBARI-17143
> URL: https://issues.apache.org/jira/browse/AMBARI-17143
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17143.patch
>
>
> After navigating from Roles section to any other one, Roles entry in left 
> navbar remains active as well as the current one. Also, JS errors are thrown:
> {code}
> TypeError: Cannot read property 'url' of undefined
> at Scope.$scope.isActive (main.js:1169)
> at vendor.js:21990
> at || (vendor.js:21343)
> at Object.extend.constant [as value] (vendor.js:21744)
> at Object.extend.literal [as get] (vendor.js:22053)
> at Scope.$digest (vendor.js:23676)
> at Scope.$apply (vendor.js:23949)
> at HTMLBodyElement. (vendor.js:21003)
> at HTMLBodyElement.dispatch (vendor.js:4409)
> at HTMLBodyElement.elemData.handle (vendor.js:4095)
> {code}
> Same error is thrown on entering any Ambari Admin section except Roles by 
> direct URL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17135) Ambari Views logs should include information of view instance


[ 
https://issues.apache.org/jira/browse/AMBARI-17135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322952#comment-15322952
 ] 

Hadoop QA commented on AMBARI-17135:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12809170/AMBARI-17135_branch-2.4-1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server contrib/views/capacity-scheduler contrib/views/files 
contrib/views/hive contrib/views/hive-next contrib/views/hueambarimigration 
contrib/views/jobs contrib/views/pig contrib/views/slider contrib/views/storm 
contrib/views/tez contrib/views/zeppelin:

  org.apache.ambari.view.hive.resources.jobs.JobServiceTest
  org.apache.ambari.view.hive.resources.jobs.JobLDAPServiceTest

  The test build failed in 
contrib/views/pig contrib/views/capacity-scheduler 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7278//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7278//console

This message is automatically generated.

> Ambari Views logs should include information of view instance
> -
>
> Key: AMBARI-17135
> URL: https://issues.apache.org/jira/browse/AMBARI-17135
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Attachments: AMBARI-17135_branch-2.4-1.patch
>
>
> the logs should contain information about which instance of view generated 
> this log entry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16864) Add unit tests for Spark2 service definition


[ 
https://issues.apache.org/jira/browse/AMBARI-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322937#comment-15322937
 ] 

Jayush Luniya commented on AMBARI-16864:


[~zjffdu] can you also get some UT coverage for Livy Server

> Add unit tests for Spark2 service definition
> 
>
> Key: AMBARI-16864
> URL: https://issues.apache.org/jira/browse/AMBARI-16864
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Saisai Shao
> Fix For: 2.4.0
>
>
> Propose to add Spark2 in Ambari as a standalone service in parallel with 
> Spark1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16864) Add unit tests for Spark2 service definition


[ 
https://issues.apache.org/jira/browse/AMBARI-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322934#comment-15322934
 ] 

Jayush Luniya commented on AMBARI-16864:


[~jerryshao]
1. You can refer 
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development for 
running unit tests locally. Since you are adding only python unit tests run 
"mvn clean test -DskipSurefireTests" to skip JAVA unit tests. 
2. You can use 
ambari-server/src/test/python/stacks/2.3/configs/spark_default.json as a 
reference and create a spark2_default.json under 
ambari-server/src/test/python/stacks/2.5/configs. Then add your unit tests in 
ambari-server/src/test/python/stacks/2.5/SPARK2. See 
ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py and 
ambari-server/src/test/python/stacks/2.2/SPARK as reference.


> Add unit tests for Spark2 service definition
> 
>
> Key: AMBARI-16864
> URL: https://issues.apache.org/jira/browse/AMBARI-16864
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Saisai Shao
> Fix For: 2.4.0
>
>
> Propose to add Spark2 in Ambari as a standalone service in parallel with 
> Spark1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16949) Metrics Collector API shows NPE if we use wildcard (%25 for '%') for metric name


 [ 
https://issues.apache.org/jira/browse/AMBARI-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-16949:
---
   Resolution: Fixed
Fix Version/s: 2.4.0
   Status: Resolved  (was: Patch Available)

Pushed to trunk and branch-2.4

> Metrics Collector API shows NPE if we use wildcard (%25 for '%') for metric 
> name
> 
>
> Key: AMBARI-16949
> URL: https://issues.apache.org/jira/browse/AMBARI-16949
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
> Attachments: AMBARI-16949-trunk-v1.patch
>
>
> When we request '/ws/v1/timeline/metrics' with metric name which contains %25 
> (escaped '%'), response for the API is json describing there's NPE.
> And NPE is logged for ambari-metrics-collector log file.
> {code}
> 2016-05-30 09:15:05,061 WARN 
> org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR
> java.lang.NullPointerException
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.appendAggregateMetricFromResultSet(PhoenixHBaseAccessor.java:810)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.getAggregateMetricRecords(PhoenixHBaseAccessor.java:772)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.getTimelineMetrics(HBaseTimelineMetricStore.java:178)
>   at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:372)
>   at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
> {code}
> Reason of NPE: 
> Metrics are properly fetched with wildcard. But when applying functions to 
> result set, actual metric name is not exist from map of metric name to list 
> of function.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16946) Storm Metrics Sink has high chance to discard some datapoints


 [ 
https://issues.apache.org/jira/browse/AMBARI-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-16946:
---
   Resolution: Fixed
Fix Version/s: 2.4.0
   Status: Resolved  (was: Patch Available)

Pushed to trunk and branch-2.4

> Storm Metrics Sink has high chance to discard some datapoints
> -
>
> Key: AMBARI-16946
> URL: https://issues.apache.org/jira/browse/AMBARI-16946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
> Attachments: AMBARI-16946-trunk-v2.patch, AMBARI-16946-trunk-v3.patch
>
>
> There's a mismatch between TimelineMetricsCache and Storm metrics unit, while 
> TimelineMetricsCache considers "metric name + timestamp" to be unique but 
> Storm is not.
> For example, assume that bolt B has task T1, T2 and B has registered metrics 
> M1. It's possible for metrics sink to receive (T1, M1) and (T2, M1) with same 
> timestamp TS1 (in TaskInfo, not current time), and received later will be 
> discarded from TimelineMetricsCache.
> If we want to have unique metric point of Storm, we should use "topology name 
> + component name + task id + metric name" to metric name so that "metric name 
> + timestamp" will be unique.
> There're other issues I would like to address, too.
> - Currently, hostname is written to hostname of the machine which runs 
> metrics sink. Since TaskInfo has hostname of the machine which runs task, 
> we're better to use this.
> - Unit of timestamp of TaskInfo is second, while Storm Metrics Sink uses this 
> as millisecond, resulting in timestamp flaw, and malfunction of cache 
> eviction. It should be multiplied by 1000.
> - 'component name' is not unique across the cluster, so it's not fit for app 
> id. 'topology name' is unique so proper value of app id is topology name. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17127) Ambari Stale Alert Triggers For Server-Side Performance Alert

2016-06-09 Thread Jonathan Hurley (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Hurley updated AMBARI-17127:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari Stale Alert Triggers For Server-Side Performance Alert
> -
>
> Key: AMBARI-17127
> URL: https://issues.apache.org/jira/browse/AMBARI-17127
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.4.0
>
> Attachments: AMBARI-17127.patch, AMBARI-17127.patch
>
>
> If the Ambari Server is restarted after being down for several minutes, the 
> "Ambari Server Performance" alert will trigger as being stale. This is 
> because the {{StaleAlertRunnable}} is not checking to ensure that Ambari has 
> been up and running long enough to have run the alert.
> The {{StaleAlertRunnable}} should verify that the uptime of Ambari is greater 
> than staleness interval.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17130) Duplicate key in database exception during version registration


 [ 
https://issues.apache.org/jira/browse/AMBARI-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-17130:
---
Attachment: (was: AMBARI-17130.patch)

> Duplicate key in database exception during version registration
> ---
>
> Key: AMBARI-17130
> URL: https://issues.apache.org/jira/browse/AMBARI-17130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17130.patch
>
>
> Need the ability to set the display name on VDF creation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17054) Configure Atlas Ranger Plugin

2016-06-09 Thread Gautam Borad (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gautam Borad updated AMBARI-17054:
--
Attachment: AMBARI-17054.3.patch
AMBARI-17054_trunk.1.patch

> Configure Atlas Ranger Plugin
> -
>
> Key: AMBARI-17054
> URL: https://issues.apache.org/jira/browse/AMBARI-17054
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-17054.1.patch, AMBARI-17054.2.patch, 
> AMBARI-17054.3.patch, AMBARI-17054_trunk.1.patch, AMBARI-17054_trunk.patch
>
>
> Need to do following changes to support Ranger Atlas Plugin from Ambari: 
> 1) Check stack support  and provide smart config section to Enable / disable 
> ranger atlas plugin
> 2) Stack advisor changes to suggest recommended configs on enable / disable 
> plugin actions. 
> 3) Ranger service creation on Enable plugin action from Ambari. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17130) Duplicate key in database exception during version registration


 [ 
https://issues.apache.org/jira/browse/AMBARI-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-17130:
---
Attachment: AMBARI-17130.patch

> Duplicate key in database exception during version registration
> ---
>
> Key: AMBARI-17130
> URL: https://issues.apache.org/jira/browse/AMBARI-17130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17130.patch
>
>
> Need the ability to set the display name on VDF creation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17121) Unit-test failing coz of issue "YARN service check fails if there is no queue named 'default'"


[ 
https://issues.apache.org/jira/browse/AMBARI-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322728#comment-15322728
 ] 

Hudson commented on AMBARI-17121:
-

FAILURE: Integrated in Ambari-trunk-Commit #5042 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5042/])
AMBARI-17121 Unit-test failing coz of issue "YARN service check fails if (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b57a7cfa2ff4d2668dc421826ffaa84e8425d26a])
* ambari-server/src/test/python/stacks/2.1/configs/default.json
* ambari-server/src/test/python/stacks/2.0.6/configs/default.json
* ambari-server/src/test/python/stacks/2.1/configs/secured.json
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* ambari-server/src/test/python/stacks/2.0.6/configs/secured.json


> Unit-test failing coz of issue "YARN service check fails if there is no queue 
> named 'default'"
> --
>
> Key: AMBARI-17121
> URL: https://issues.apache.org/jira/browse/AMBARI-17121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17121.patch, AMBARI-17121.patch.1, 
> test-logs-17121.txt
>
>
> {code}
> --
> Failed tests:
> ERROR: test_validateYARNConfigurationsEnv 
> (test_stack_advisor.TestHDP22StackAdvisor)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
>  line 3196, in test_validateYARNConfigurationsEnv
> res = self.stackAdvisor.validateYARNEnvConfigurations(properties, 
> recommendedDefaults, configurations, '', '')
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.2/common/../../../../../main/resources/stacks/HDP/2.2/services/stack_advisor.py",
>  line 1504, in validateYARNEnvConfigurations
> parentValidationProblems = super(HDP22StackAdvisor, 
> self).validateYARNEnvConfigurations(properties, recommendedDefaults, 
> configurations, services, hosts)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.2/common/../../../../../main/resources/stacks/HDP/2.0.6/services/stack_advisor.py",
>  line 1396, in validateYARNEnvConfigurations
> capacity_scheduler_properties, received_as_key_value_pair = 
> self.getCapacitySchedulerProperties(services)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.2/common/../../../../../main/resources/stacks/HDP/2.0.6/services/stack_advisor.py",
>  line 1512, in getCapacitySchedulerProperties
> if "capacity-scheduler" in services['configurations']:
> TypeError: string indices must be integers, not str
> ERROR: test_service_check_default (test_yarn_service_check.TestServiceCheck)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py",
>  line 45, in test_service_check_default
> checked_call_mocks = [(0, "some test text, appTrackingUrl=http:"
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 152, in executeScript
> method(RMFTestCase.env, *command_args)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
>  line 109, in service_check
> yarn_distrubuted_shell_check_cmd = format(" 
> ".join(yarn_distrubuted_shell_check_params))
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/main/python/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
>

[jira] [Commented] (AMBARI-17085) Hive View : Error in persisting JobImpl while submitting Hive Job


[ 
https://issues.apache.org/jira/browse/AMBARI-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322724#comment-15322724
 ] 

Hudson commented on AMBARI-17085:
-

FAILURE: Integrated in Ambari-trunk-Commit #5042 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5042/])
AMBARI-17085 : corrected the initialization condition of view entities. 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=140c9f13d6b663847473d50ad3b3bed74c3de84f])
* 
ambari-server/src/main/java/org/apache/ambari/server/view/persistence/DataStoreImpl.java


> Hive View : Error in persisting JobImpl while submitting Hive Job
> -
>
> Key: AMBARI-17085
> URL: https://issues.apache.org/jira/browse/AMBARI-17085
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-views
>Affects Versions: 2.2.2
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.4.0
>
> Attachments: AMBARI-17085_branch-2.4.patch
>
>
> Sometimes can be reproduced under heavy load.
> Error Log :
> {"trace":"org.apache.ambari.view.PersistenceException: Caught exception 
> trying to store view entity 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobImpl@0 
> org.apache.ambari.view.PersistenceException: Caught exception trying to store 
> view entity org.apache.ambari.view.hive.resources.jobs.viewJobs.JobImpl@0 
> \tat 
> org.apache.ambari.server.view.persistence.DataStoreImpl.throwPersistenceException(DataStoreImpl.java:658)
>  \tat 
> org.apache.ambari.server.view.persistence.DataStoreImpl.store(DataStoreImpl.java:157)
>  \tat 
> org.apache.ambari.view.hive.persistence.DataStoreStorage.store(DataStoreStorage.java:63)
>  \tat 
> org.apache.ambari.view.hive.resources.CRUDResourceManager.save(CRUDResourceManager.java:117)
>  \tat 
> org.apache.ambari.view.hive.resources.PersonalCRUDResourceManager.save(PersonalCRUDResourceManager.java:68)
>  \tat 
> org.apache.ambari.view.hive.resources.PersonalCRUDResourceManager.save(PersonalCRUDResourceManager.java:34)
>  \tat 
> org.apache.ambari.view.hive.resources.CRUDResourceManager.create(CRUDResourceManager.java:59)
>  \tat 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.create(JobResourceManager.java:52)
>  \tat 
> org.apache.ambari.view.hive.resources.jobs.JobService.create(JobService.java:428)
>  \tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) \tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> \tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  \tat java.lang.reflect.Method.invoke(Method.java:498) \tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  \tat 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  \tat 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  \tat 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>  \tat 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>  \tat 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>  \tat 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>  \tat 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>  \tat 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>  \tat 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
>  \tat 
>

[jira] [Commented] (AMBARI-17141) "Settings" button shown to cluster administrator


[ 
https://issues.apache.org/jira/browse/AMBARI-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322727#comment-15322727
 ] 

Hudson commented on AMBARI-17141:
-

FAILURE: Integrated in Ambari-trunk-Commit #5042 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5042/])
AMBARI-17141 "Settings" button shown to cluster administrator. (atkach) 
(atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f4dae12ebe27035c478f884a4d15012a12c0dd0d])
* ambari-web/app/templates/common/modal_popup.hbs
* ambari-web/app/utils/host_progress_popup.js
* ambari-web/app/templates/application.hbs


> "Settings" button shown to cluster administrator
> 
>
> Key: AMBARI-17141
> URL: https://issues.apache.org/jira/browse/AMBARI-17141
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17141.patch, Ambari - Dropdown Menu.png, Screen 
> Shot 2016-06-08 at 11.04.03 AM.png
>
>
> The button "Settings" in the drop down of the "admin" tab in ambari shouldn't 
> be shown for cluster administrator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16836) View Instance: Data Migration


[ 
https://issues.apache.org/jira/browse/AMBARI-16836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322726#comment-15322726
 ] 

Hudson commented on AMBARI-16836:
-

FAILURE: Integrated in Ambari-trunk-Commit #5042 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5042/])
AMBARI-16836 : View Instance: Data Migration. (Nitiraj Rathore via 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ddb201f8ce8ecdc2a563a5ae69c071655e481b04])
* 
ambari-server/src/test/java/org/apache/ambari/server/view/ViewRegistryTest.java
* ambari-server/src/main/python/ambari_server/serverUpgrade.py
* 
ambari-server/src/main/java/org/apache/ambari/server/view/ViewDataMigrationContextImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ViewDataMigrationService.java
* ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java
* 
ambari-server/src/test/java/org/apache/ambari/server/view/ViewDataMigrationUtilityTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/ViewDataMigrationServiceTest.java
* ambari-server/src/main/java/org/apache/ambari/server/view/ViewExtractor.java
* 
ambari-server/src/main/java/org/apache/ambari/server/view/ViewDataMigrationUtility.java
* 
ambari-server/src/test/java/org/apache/ambari/server/view/ViewDataMigrationContextImplTest.java


> View Instance: Data Migration
> -
>
> Key: AMBARI-16836
> URL: https://issues.apache.org/jira/browse/AMBARI-16836
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.4.0
>
> Attachments: AMBARI-16836_branch-2.4-1.patch
>
>
> Provide instructions for performing the following:
> 1) TWO INSTANCES, SAME VERSION
> User has view100 instance A. Create view100 instance B. After creation of 
> instance B, how the Admin will migrate data (entity, instance, perms) from A 
> -> B
> 2) TWO INSTANCES, NEWER VERSION
> User has view100 instance A. Create view200 instance B. After creation of 
> instance B, how the Admin will migrate data (entity, instance, perms) from A 
> -> B.
> 3) NEWER VERSION IN NEW AMBARI
> User has view100 instance A in Ambari 2.2.2. They upgrade to Ambari 2.4.0 
> with a newer version of view200. The view200 instance is not auto-created. So 
> would they just follow #2?
> 4) NEW INSTANCE -> NEWER VERSION
> User has view100 instance A and when they create view200 instance B, 
> automatically migrate data (entity, instance, perms) from A -> B.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17081) Hive View : Upload Table : Support for Date and Timestamp type detection according to hive specs


[ 
https://issues.apache.org/jira/browse/AMBARI-17081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322725#comment-15322725
 ] 

Hudson commented on AMBARI-17081:
-

FAILURE: Integrated in Ambari-trunk-Commit #5042 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5042/])
AMBARI-17081 : hive view upload table adding support for date and time 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9c6ab0be9f488f0d89d032c23af0138b729994f8])
* 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/Parser.java
* 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/ParseUtils.java
* 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/upload/ParseUtilsTest.java


> Hive View : Upload Table : Support for Date and Timestamp type detection 
> according to hive specs
> 
>
> Key: AMBARI-17081
> URL: https://issues.apache.org/jira/browse/AMBARI-17081
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.4.0
>
> Attachments: AMBARI-17081_branch-2.4.patch
>
>
> Hive Date and Timestamp mentioned in the specs should be supported.
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types#LanguageManualTypes-timestamp



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17128) Cluster operator and ServiceAdministrator able to enable/disable/edit alert definitions

2016-06-09 Thread Vitaly Brodetskyi (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vitaly Brodetskyi updated AMBARI-17128:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.4

> Cluster operator and ServiceAdministrator able to enable/disable/edit alert 
> definitions
> ---
>
> Key: AMBARI-17128
> URL: https://issues.apache.org/jira/browse/AMBARI-17128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17128.patch
>
>
> Login to cluster using credentials of a cluster operator/ServiceAdministrator.
> Try moving to alerts page. Alerts are editable by cluster operator when it 
> shouldn't have been.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17140) Last button in the log search pagination panel does not take the user to the last page and few more fixes


[ 
https://issues.apache.org/jira/browse/AMBARI-17140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322699#comment-15322699
 ] 

Hadoop QA commented on AMBARI-17140:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809174/AMBARI-17140.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-logsearch/ambari-logsearch-portal.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7277//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7277//console

This message is automatically generated.

> Last button in the log search pagination panel does not take the user to the 
> last page and few more fixes
> -
>
> Key: AMBARI-17140
> URL: https://issues.apache.org/jira/browse/AMBARI-17140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Dharmesh Makwana
>Assignee: Dharmesh Makwana
> Fix For: 2.4.0
>
> Attachments: AMBARI-17140.patch
>
>
> 1) Last button in the log search pagination panel does not take the user to 
> the last page.
> 2) Solr warming feature added.
> 3) Suffix in columns mapping issue fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17146) Implement config values trimming for deployment via blueprint


 [ 
https://issues.apache.org/jira/browse/AMBARI-17146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-17146:

Status: Patch Available  (was: Open)

> Implement config values trimming for deployment via blueprint
> -
>
> Key: AMBARI-17146
> URL: https://issues.apache.org/jira/browse/AMBARI-17146
> Project: Ambari
>  Issue Type: Task
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17146_1.patch
>
>
> Implement config values trimming for deployment via blueprint as we do in UI
> {code}
>   trimProperty: function (property) {
> var displayType = Em.get(property, 'displayType');
> var value = Em.get(property, 'value');
> var name = Em.get(property, 'name');
> var rez;
> switch (displayType) {
>   case 'directories':
>   case 'directory':
> rez = value.replace(/,/g, ' ').trim().split(/\s+/g).join(',');
> break;
>   case 'host':
> rez = value.trim();
> break;
>   case 'password':
> break;
>   default:
> if (name == 'javax.jdo.option.ConnectionURL' || name == 
> 'oozie.service.JPAService.jdbc.url') {
>   rez = value.trim();
> }
> rez = (typeof value == 'string') ? value.replace(/(\s+$)/g, '') : 
> value;
> }
> return ((rez == '') || (rez == undefined)) ? value : rez;
>   },
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17146) Implement config values trimming for deployment via blueprint


 [ 
https://issues.apache.org/jira/browse/AMBARI-17146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-17146:

Attachment: AMBARI-17146_1.patch

> Implement config values trimming for deployment via blueprint
> -
>
> Key: AMBARI-17146
> URL: https://issues.apache.org/jira/browse/AMBARI-17146
> Project: Ambari
>  Issue Type: Task
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17146_1.patch
>
>
> Implement config values trimming for deployment via blueprint as we do in UI
> {code}
>   trimProperty: function (property) {
> var displayType = Em.get(property, 'displayType');
> var value = Em.get(property, 'value');
> var name = Em.get(property, 'name');
> var rez;
> switch (displayType) {
>   case 'directories':
>   case 'directory':
> rez = value.replace(/,/g, ' ').trim().split(/\s+/g).join(',');
> break;
>   case 'host':
> rez = value.trim();
> break;
>   case 'password':
> break;
>   default:
> if (name == 'javax.jdo.option.ConnectionURL' || name == 
> 'oozie.service.JPAService.jdbc.url') {
>   rez = value.trim();
> }
> rez = (typeof value == 'string') ? value.replace(/(\s+$)/g, '') : 
> value;
> }
> return ((rez == '') || (rez == undefined)) ? value : rez;
>   },
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17146) Implement config values trimming for deployment via blueprint

Dmytro Sen created AMBARI-17146:
---

 Summary: Implement config values trimming for deployment via 
blueprint
 Key: AMBARI-17146
 URL: https://issues.apache.org/jira/browse/AMBARI-17146
 Project: Ambari
  Issue Type: Task
Affects Versions: 2.4.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
 Fix For: 2.4.0


Implement config values trimming for deployment via blueprint as we do in UI
{code}
  trimProperty: function (property) {
var displayType = Em.get(property, 'displayType');
var value = Em.get(property, 'value');
var name = Em.get(property, 'name');
var rez;
switch (displayType) {
  case 'directories':
  case 'directory':
rez = value.replace(/,/g, ' ').trim().split(/\s+/g).join(',');
break;
  case 'host':
rez = value.trim();
break;
  case 'password':
break;
  default:
if (name == 'javax.jdo.option.ConnectionURL' || name == 
'oozie.service.JPAService.jdbc.url') {
  rez = value.trim();
}
rez = (typeof value == 'string') ? value.replace(/(\s+$)/g, '') : value;
}
return ((rez == '') || (rez == undefined)) ? value : rez;
  },

{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17130) Duplicate key in database exception during version registration


 [ 
https://issues.apache.org/jira/browse/AMBARI-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-17130:
---
Attachment: AMBARI-17130.patch

> Duplicate key in database exception during version registration
> ---
>
> Key: AMBARI-17130
> URL: https://issues.apache.org/jira/browse/AMBARI-17130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17130.patch
>
>
> Need the ability to set the display name on VDF creation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17145) Unformatted configs remain in zeppelin-env.sh


[ 
https://issues.apache.org/jira/browse/AMBARI-17145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322679#comment-15322679
 ] 

Hadoop QA commented on AMBARI-17145:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809182/AMBARI-17145.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7276//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7276//console

This message is automatically generated.

> Unformatted configs remain in zeppelin-env.sh
> -
>
> Key: AMBARI-17145
> URL: https://issues.apache.org/jira/browse/AMBARI-17145
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
> Attachments: AMBARI-17145.patch
>
>
> When we just installed Zeppelin Notebook, 
> {{/etc/zeppelin/conf/zeppelin-env.sh}} is like this
> {code}
> # Spark master url. eg. spark://master_addr:7077. Leave empty if you want to 
> use local mode
> export MASTER=yarn-client
> export SPARK_YARN_JAR={spark_jar_dir}/zeppelin-spark-0.5.5-SNAPSHOT.jar
> (snip)
> {code}
> It maybe 
> ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py
>  doesn't import {{from resource_management.libraries.functions.format import 
> format}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17143) Ambari Admin: incorrect navigation behaviour


 [ 
https://issues.apache.org/jira/browse/AMBARI-17143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-17143:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk and branch-2.4

> Ambari Admin: incorrect navigation behaviour
> 
>
> Key: AMBARI-17143
> URL: https://issues.apache.org/jira/browse/AMBARI-17143
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17143.patch
>
>
> After navigating from Roles section to any other one, Roles entry in left 
> navbar remains active as well as the current one. Also, JS errors are thrown:
> {code}
> TypeError: Cannot read property 'url' of undefined
> at Scope.$scope.isActive (main.js:1169)
> at vendor.js:21990
> at || (vendor.js:21343)
> at Object.extend.constant [as value] (vendor.js:21744)
> at Object.extend.literal [as get] (vendor.js:22053)
> at Scope.$digest (vendor.js:23676)
> at Scope.$apply (vendor.js:23949)
> at HTMLBodyElement. (vendor.js:21003)
> at HTMLBodyElement.dispatch (vendor.js:4409)
> at HTMLBodyElement.elemData.handle (vendor.js:4095)
> {code}
> Same error is thrown on entering any Ambari Admin section except Roles by 
> direct URL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17142) RBAC: Roles show "empty" user after delete


 [ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-17142:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17142) RBAC: Roles show "empty" user after delete


[ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322644#comment-15322644
 ] 

Aleksandr Kovalenko commented on AMBARI-17142:
--

committed to trunk and branch-2.4

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17142) RBAC: Roles show "empty" user after delete


[ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322581#comment-15322581
 ] 

Aleksandr Kovalenko commented on AMBARI-17142:
--

updated patch to cover case, when user doesn't have permissions

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17142) RBAC: Roles show "empty" user after delete


 [ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-17142:
-
Attachment: AMBARI-17142.patch

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17142) RBAC: Roles show "empty" user after delete


[ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322614#comment-15322614
 ] 

Hadoop QA commented on AMBARI-17142:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809188/AMBARI-17142.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-admin.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7275//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7275//console

This message is automatically generated.

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17137) Capacity Scheduler View - Node label to queue mapping implementation


[ 
https://issues.apache.org/jira/browse/AMBARI-17137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322589#comment-15322589
 ] 

Hadoop QA commented on AMBARI-17137:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809164/AMBARI-17137.1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
contrib/views/capacity-scheduler.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7274//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7274//console

This message is automatically generated.

> Capacity Scheduler View - Node label to queue mapping implementation
> 
>
> Key: AMBARI-17137
> URL: https://issues.apache.org/jira/browse/AMBARI-17137
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Akhil PB
> Attachments: AMBARI-17137.1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17112) Fixed implementation of on-ambari-upgrade support

2016-06-09 Thread Dmitry Lysnichenko (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322602#comment-15322602
 ] 

Dmitry Lysnichenko commented on AMBARI-17112:
-

Committed patc: Fixed implementation of on-ambari-upgrade support. Patch 1 - 
change validation rules and available fields
To https://git-wip-us.apache.org/repos/asf/ambari.git
   a7edab2..a998371  branch-2.4 -> branch-2.4
   b57a7cf..4c5cf30  trunk -> trunk


> Fixed implementation of on-ambari-upgrade support
> -
>
> Key: AMBARI-17112
> URL: https://issues.apache.org/jira/browse/AMBARI-17112
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17112.patch
>
>
> Implementation of AMBARI-16272 had a broken on-ambari-upgrade support and was 
> partially reverted. Fix implementation and commit it back



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17142) RBAC: Roles show "empty" user after delete

2016-06-09 Thread Andrii Babiichuk (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322585#comment-15322585
 ] 

Andrii Babiichuk commented on AMBARI-17142:
---

+1 for the patch

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17142.patch
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17142) RBAC: Roles show "empty" user after delete


 [ 
https://issues.apache.org/jira/browse/AMBARI-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-17142:
-
Attachment: (was: AMBARI-17142.patch)

> RBAC: Roles show "empty" user after delete
> --
>
> Key: AMBARI-17142
> URL: https://issues.apache.org/jira/browse/AMBARI-17142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
>
> 1. Created a user 'test'
> 2. set role to cluster admin
> 3. deleted user 'test'
> 4. when to roles and see an "empty" space where the user was in the role. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17143) Ambari Admin: incorrect navigation behaviour


[ 
https://issues.apache.org/jira/browse/AMBARI-17143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322557#comment-15322557
 ] 

Hadoop QA commented on AMBARI-17143:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12809160/AMBARI-17143.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-admin.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7273//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7273//console

This message is automatically generated.

> Ambari Admin: incorrect navigation behaviour
> 
>
> Key: AMBARI-17143
> URL: https://issues.apache.org/jira/browse/AMBARI-17143
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17143.patch
>
>
> After navigating from Roles section to any other one, Roles entry in left 
> navbar remains active as well as the current one. Also, JS errors are thrown:
> {code}
> TypeError: Cannot read property 'url' of undefined
> at Scope.$scope.isActive (main.js:1169)
> at vendor.js:21990
> at || (vendor.js:21343)
> at Object.extend.constant [as value] (vendor.js:21744)
> at Object.extend.literal [as get] (vendor.js:22053)
> at Scope.$digest (vendor.js:23676)
> at Scope.$apply (vendor.js:23949)
> at HTMLBodyElement. (vendor.js:21003)
> at HTMLBodyElement.dispatch (vendor.js:4409)
> at HTMLBodyElement.elemData.handle (vendor.js:4095)
> {code}
> Same error is thrown on entering any Ambari Admin section except Roles by 
> direct URL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17141) "Settings" button shown to cluster administrator

2016-06-09 Thread Andrii Tkach (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Tkach updated AMBARI-17141:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> "Settings" button shown to cluster administrator
> 
>
> Key: AMBARI-17141
> URL: https://issues.apache.org/jira/browse/AMBARI-17141
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17141.patch, Ambari - Dropdown Menu.png, Screen 
> Shot 2016-06-08 at 11.04.03 AM.png
>
>
> The button "Settings" in the drop down of the "admin" tab in ambari shouldn't 
> be shown for cluster administrator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17121) Unit-test failing coz of issue "YARN service check fails if there is no queue named 'default'"