[jira] [Commented] (AMBARI-20253) HiveView2.0: Auto refresh not working.
[ https://issues.apache.org/jira/browse/AMBARI-20253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900123#comment-15900123 ] Hudson commented on AMBARI-20253: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1203 (See [https://builds.apache.org/job/Ambari-branch-2.5/1203/]) AMBARI-20253. HiveView2.0: Auto refresh not working.(dipayanb) (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dff7754b7cb718de7e3bcfaac7afa0a4ce936afe]) * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/databases/database/tables.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/transforms/date.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/new.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases.js * (add) contrib/views/hive20/src/main/resources/ui/app/services/auto-refresh.js * (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js > HiveView2.0: Auto refresh not working. > -- > > Key: AMBARI-20253 > URL: https://issues.apache.org/jira/browse/AMBARI-20253 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20253.branch-2.5.patch > > > Auto Refresh of current databases and tables for the selected database in > table manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order
[ https://issues.apache.org/jira/browse/AMBARI-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reopened AMBARI-20157: > Ambari sends SNMP notifications in incorrect order > -- > > Key: AMBARI-20157 > URL: https://issues.apache.org/jira/browse/AMBARI-20157 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-20157 > > > Ambari sends notifications in wrong order. ideally first generated Alert > should be notified first. > This issue is reproducible in straight steps. > 1. Have 4 to 5 alerts generated in short span of time. > 2. when Ambari notifier thread queries Database with the query like "select * > from alert_notice where notify_state = 'PENDING'" > This query returns last one first. > Ex: > 2066 51 4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26 > 2065 51 4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa > 2064 51 4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8 > 2063 51 4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909 > 2062 51 4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e > 2061 51 4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89 > So Notified threads loops that list and sends one by one. > This needs to be fixed. either have to read " order by notification_id" so > that it gives correct order. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required
[
https://issues.apache.org/jira/browse/AMBARI-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900068#comment-15900068
]
Hadoop QA commented on AMBARI-20343:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856633/AMBARI-20343-branch-2.5-v1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10919//console
This message is automatically generated.
> Zeppelin: Configure both Hive and Hive interactive interpreters whenever
> required
> -
>
> Key: AMBARI-20343
> URL: https://issues.apache.org/jira/browse/AMBARI-20343
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: 2.5.0
>Reporter: Kshitij Badani
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-20343-branch-2.5-v1.patch
>
>
> Currently only jdbc(hive) is present in the interpreter config. But lets say
> if we have only HSI (hive server interactive) present on our cluster , or if
> we have both HSI and Hive present then we need some changes to the way
> interpreters are being defined
> We should use %jdbc(hive) refer Hive interactive when only Hive interactive
> is present in the cluster.
> Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive
> interactive based on the availability of Hive/Hive interactive.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20253) HiveView2.0: Auto refresh not working.
[ https://issues.apache.org/jira/browse/AMBARI-20253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900071#comment-15900071 ] Hudson commented on AMBARI-20253: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6966 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6966/]) AMBARI-20253. HiveView2.0: Auto refresh not working.(dipayanb) (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a6dac1fdf6728c7dfb1d14a072052ebe47df83bd]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/databases/database/tables.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/new.js * (add) contrib/views/hive20/src/main/resources/ui/app/transforms/date.js * (add) contrib/views/hive20/src/main/resources/ui/app/services/auto-refresh.js * (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js > HiveView2.0: Auto refresh not working. > -- > > Key: AMBARI-20253 > URL: https://issues.apache.org/jira/browse/AMBARI-20253 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20253.branch-2.5.patch > > > Auto Refresh of current databases and tables for the selected database in > table manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20256) Auto Hive 2.0 instance is missing permission for default Ambari roles
[ https://issues.apache.org/jira/browse/AMBARI-20256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900069#comment-15900069 ] Hudson commented on AMBARI-20256: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6966 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6966/]) AMBARI-20256. Auto Hive 2.0 instance is missing permission for default (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d62755233ccb489cbca1ec78ae2b7e86857d6efe]) * (edit) contrib/views/hive20/src/main/resources/view.xml > Auto Hive 2.0 instance is missing permission for default Ambari roles > - > > Key: AMBARI-20256 > URL: https://issues.apache.org/jira/browse/AMBARI-20256 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20256.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20345) Alert Event Publisher Executor Doesn't Scale Threads
[
https://issues.apache.org/jira/browse/AMBARI-20345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900065#comment-15900065
]
Hudson commented on AMBARI-20345:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6966 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6966/])
AMBARI-20345 - Alert Event Publisher Executor Doesn't Scale Threads (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=434ff1f25fa62e26709a500d70bf8012e531d5bb])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOCachedTest.java
* (edit) ambari-server/docs/configuration/index.md
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/services/CachedAlertFlushServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/events/publishers/AlertEventPublisher.java
> Alert Event Publisher Executor Doesn't Scale Threads
>
>
> Key: AMBARI-20345
> URL: https://issues.apache.org/jira/browse/AMBARI-20345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-20345.patch
>
>
> The event bus which is used to handling incoming {{AlertEvent}} events is
> incorrectly initialized and can never scale from the core number of threads.
> This is because it uses an unbounded queued. From the
> [ThreadPoolExecutor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> documentation:
> {quote}
> A ThreadPoolExecutor will automatically adjust the pool size (see
> getPoolSize()) according to the bounds set by corePoolSize (see
> getCorePoolSize()) and maximumPoolSize (see getMaximumPoolSize()). When a new
> task is submitted in method execute(java.lang.Runnable), and fewer than
> corePoolSize threads are running, a new thread is created to handle the
> request, even if other worker threads are idle. If there are more than
> corePoolSize but less than maximumPoolSize threads running, *a new thread
> will be created only if the queue is full.*
> {quote}
> We should switch to a configurable, bounded queue so that this property can
> be utilized in large clusters where more than the default of 2 core threads
> is needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order
[ https://issues.apache.org/jira/browse/AMBARI-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-20157: --- Status: Patch Available (was: Open) > Ambari sends SNMP notifications in incorrect order > -- > > Key: AMBARI-20157 > URL: https://issues.apache.org/jira/browse/AMBARI-20157 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Labels: patch > Fix For: trunk > > > Ambari sends notifications in wrong order. ideally first generated Alert > should be notified first. > This issue is reproducible in straight steps. > 1. Have 4 to 5 alerts generated in short span of time. > 2. when Ambari notifier thread queries Database with the query like "select * > from alert_notice where notify_state = 'PENDING'" > This query returns last one first. > Ex: > 2066 51 4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26 > 2065 51 4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa > 2064 51 4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8 > 2063 51 4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909 > 2062 51 4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e > 2061 51 4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89 > So Notified threads loops that list and sends one by one. > This needs to be fixed. either have to read " order by notification_id" so > that it gives correct order. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used
[
https://issues.apache.org/jira/browse/AMBARI-20346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900063#comment-15900063
]
Hadoop QA commented on AMBARI-20346:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856637/AMBARI-20346.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10918//console
This message is automatically generated.
> Log Search Upgrade should modify keystore / truststore path if it wasn't used
> -
>
> Key: AMBARI-20346
> URL: https://issues.apache.org/jira/browse/AMBARI-20346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20346.patch
>
>
> The default path for the truststore / keystore in 2.4 was under
> /etc/security, which may cause permission problems. If the user haven't used
> the keystore / truststore, and haven't altered the path yet it should be
> modified upon upgrade to the new default value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-19790) HiveCLI and AtlasHook do not work correctly
[ https://issues.apache.org/jira/browse/AMBARI-19790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Senia resolved AMBARI-19790. - Resolution: Won't Fix > HiveCLI and AtlasHook do not work correctly > --- > > Key: AMBARI-19790 > URL: https://issues.apache.org/jira/browse/AMBARI-19790 > Project: Ambari > Issue Type: Bug > Environment: HDP 2.5.3.x >Reporter: Greg Senia > > After upgrading to HDP 2.5.3.x we are no longer able to correctly use the > HiveCLI with Atlas Hive Hook. Some assumptions specifically that the only > access method is HiveServer2. > We need the ability to split option in Ambari so HiveCLI AtlasHook uses the > following options: > atlas.jaas.KafkaClient.loginModuleControlFlag=required > atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule > atlas.jaas.KafkaClient.option.serviceName=kafka > atlas.jaas.KafkaClient.option.renewTicket=True > atlas.jaas.KafkaClient.option.useTicketCache=True > and HiveServer2 using: > atlas.jaas.KafkaClient.loginModuleControlFlag=required > atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule > atlas.jaas.KafkaClient.option.keyTab=/etc/security/keytabs/hive.service.keytab > atlas.jaas.KafkaClient.option.principal=hive/_h...@tech.hdp.example.com > atlas.jaas.KafkaClient.option.serviceName=kafka > atlas.jaas.KafkaClient.option.storeKey=True > atlas.jaas.KafkaClient.option.useKeyTab=True > If this is not done HiveCLI will fail to post to Kafka: > ve/warehouse/nyse_stocks_test"}, endTime=Mon Jan 30 11:42:38 EST 2017}}]] > after 3 retries. Quitting > org.apache.kafka.common.KafkaException: Failed to construct kafka producer > at > org.apache.kafka.clients.producer.KafkaProducer.(KafkaProducer.java:335) > at > org.apache.kafka.clients.producer.KafkaProducer.(KafkaProducer.java:188) > at > org.apache.atlas.kafka.KafkaNotification.createProducer(KafkaNotification.java:311) > at > org.apache.atlas.kafka.KafkaNotification.sendInternal(KafkaNotification.java:220) > at > org.apache.atlas.notification.AbstractNotification.send(AbstractNotification.java:84) > at > org.apache.atlas.hook.AtlasHook.notifyEntitiesInternal(AtlasHook.java:129) > at org.apache.atlas.hook.AtlasHook.notifyEntities(AtlasHook.java:114) > at org.apache.atlas.hook.AtlasHook.notifyEntities(AtlasHook.java:167) > at > org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:282) > at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:82) > at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:193) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.apache.kafka.common.KafkaException: > javax.security.auth.login.LoginException: Could not login: the client is > being asked for a password, but the Kafka client code does not currently > support obtaining a password from the user. not available to garner > authentication information from the user > at > org.apache.kafka.common.network.SaslChannelBuilder.configure(SaslChannelBuilder.java:86) > at > org.apache.kafka.common.network.ChannelBuilders.create(ChannelBuilders.java:71) > at > org.apache.kafka.clients.ClientUtils.createChannelBuilder(ClientUtils.java:83) > at > org.apache.kafka.clients.producer.KafkaProducer.(KafkaProducer.java:277) > After adjusting atlas-application.properties: > -b558-4b02d509d888 > 2017-01-30 23:13:41,053 INFO [main]: log.PerfLogger > (PerfLogger.java:PerfLogBegin(148)) - method=PostHook.org.apache.atlas.hive.hook.HiveHook > from=org.apache.hadoop.hive.ql.Driver> > 2017-01-30 23:13:41,062 INFO [main]: log.PerfLogger > (PerfLogger.java:PerfLogEnd(176)) - method=PostHook.org.apache.atlas.hive.hook.HiveHook start=1485836021053 > end=1485836021062 duration=9 from=org.apache.hadoop.hive.ql.Driver> > 2017-01-30 23:13:41,062 INFO [Atlas Logger 1]: hook.HiveHook > (HiveHook.java:fireAndForget(209)) - Entered Atlas hook for hook type > POST_EXEC_HOOK operation CREATETABLE_AS_SELECT > 2017-01-30 23:13:41,062 INFO [main]: ql.Driver (Driver.java:execute(1635)) - > Resetting the caller context to -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20345) Alert Event Publisher Executor Doesn't Scale Threads
[
https://issues.apache.org/jira/browse/AMBARI-20345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900126#comment-15900126
]
Hudson commented on AMBARI-20345:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1203 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1203/])
AMBARI-20345 - Alert Event Publisher Executor Doesn't Scale Threads (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=07a30a12b6b7b091e735f9688ebc6934d4b9cf23])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/events/publishers/AlertEventPublisher.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/services/CachedAlertFlushServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOCachedTest.java
* (edit) ambari-server/docs/configuration/index.md
> Alert Event Publisher Executor Doesn't Scale Threads
>
>
> Key: AMBARI-20345
> URL: https://issues.apache.org/jira/browse/AMBARI-20345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-20345.patch
>
>
> The event bus which is used to handling incoming {{AlertEvent}} events is
> incorrectly initialized and can never scale from the core number of threads.
> This is because it uses an unbounded queued. From the
> [ThreadPoolExecutor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> documentation:
> {quote}
> A ThreadPoolExecutor will automatically adjust the pool size (see
> getPoolSize()) according to the bounds set by corePoolSize (see
> getCorePoolSize()) and maximumPoolSize (see getMaximumPoolSize()). When a new
> task is submitted in method execute(java.lang.Runnable), and fewer than
> corePoolSize threads are running, a new thread is created to handle the
> request, even if other worker threads are idle. If there are more than
> corePoolSize but less than maximumPoolSize threads running, *a new thread
> will be created only if the queue is full.*
> {quote}
> We should switch to a configurable, bounded queue so that this property can
> be utilized in large clusters where more than the default of 2 core threads
> is needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20349) When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF Process alert fails
[
https://issues.apache.org/jira/browse/AMBARI-20349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900180#comment-15900180
]
Robert Levas commented on AMBARI-20349:
---
FYI, [~jaoki], [~bhuvnesh2703]
> When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF
> Process alert fails
> -
>
> Key: AMBARI-20349
> URL: https://issues.apache.org/jira/browse/AMBARI-20349
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: PHD, PXF, kerberos
> Fix For: 2.5.0
>
>
> When SPNEGO authentication is enabled for Hadoop in a cluster where NN HA is
> enabled, PXF Process alert fails with the following errors in the
> ambari-agent.log file
> {noformat}
> ERROR 2017-03-07 18:03:58,417 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesy
> stem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> INFO 2017-03-07 18:04:02,769 logger.py:71 - call['ambari-sudo.sh su hdfs -l
> -s /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmphTXg76 2>/tmp/tmp5bm2nM''] {'quiet': False}
> INFO 2017-03-07 18:04:02,797 logger.py:71 - call returned (0, '')
> ERROR 2017-03-07 18:04:02,798 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {noformat}
> *Cause*
> During the test for the {{PXF Process}} alert, the Active NN is found using a
> JMX call. This call requires SPNEGO authentication since SPNEGO
> authentication is turned on for the Hadoop web interfaces. However, a valid
> Kerberos ticket is not found in the configured user's Kerberos ticket cache.
> In this case, the configured users is the HDFS user - which technically is
> not necessary.
> This occurs in
> {code:title=common-services/PXF/3.0.0/package/alerts/api_status.py:137}
> if CLUSTER_ENV_SECURITY in configurations and
> configurations[CLUSTER_ENV_SECURITY].lower() == "true":
> if 'dfs.nameservices' in configurations[HDFS_SITE]:
> namenode_address =
> get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
> configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
> else:
> namenode_address =
> configurations[HDFS_SITE]['dfs.namenode.http-address']
> token = _get_delegation_token(namenode_address,
> configurations[HADOOP_ENV_HDFS_USER],
>
> configurations[HADOOP_ENV_HDFS_USER_KEYTAB],
>
> configurations[HADOOP_ENV_HDFS_PRINCIPAL_NAME],
> None)
> commonPXFHeaders.update({"X-GP-TOKEN": token})
> {code}
> Inside the call at
> {code}
> namenode_address =
> get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
> configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
> {code}
> *Solution*
> Ensure the configured user's Kerberos ticket cache contains a valid ticket
> before querying for the active NN. Possibly change the acting user to one
> executing the PXF component.
--
This message was sent by Atlassian JIRA
[jira] [Updated] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order
[ https://issues.apache.org/jira/browse/AMBARI-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-20157: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari sends SNMP notifications in incorrect order > -- > > Key: AMBARI-20157 > URL: https://issues.apache.org/jira/browse/AMBARI-20157 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-20157 > > > Ambari sends notifications in wrong order. ideally first generated Alert > should be notified first. > This issue is reproducible in straight steps. > 1. Have 4 to 5 alerts generated in short span of time. > 2. when Ambari notifier thread queries Database with the query like "select * > from alert_notice where notify_state = 'PENDING'" > This query returns last one first. > Ex: > 2066 51 4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26 > 2065 51 4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa > 2064 51 4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8 > 2063 51 4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909 > 2062 51 4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e > 2061 51 4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89 > So Notified threads loops that list and sends one by one. > This needs to be fixed. either have to read " order by notification_id" so > that it gives correct order. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order
[ https://issues.apache.org/jira/browse/AMBARI-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-20157: --- Attachment: AMBARI-20157 > Ambari sends SNMP notifications in incorrect order > -- > > Key: AMBARI-20157 > URL: https://issues.apache.org/jira/browse/AMBARI-20157 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-20157 > > > Ambari sends notifications in wrong order. ideally first generated Alert > should be notified first. > This issue is reproducible in straight steps. > 1. Have 4 to 5 alerts generated in short span of time. > 2. when Ambari notifier thread queries Database with the query like "select * > from alert_notice where notify_state = 'PENDING'" > This query returns last one first. > Ex: > 2066 51 4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26 > 2065 51 4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa > 2064 51 4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8 > 2063 51 4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909 > 2062 51 4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e > 2061 51 4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89 > So Notified threads loops that list and sends one by one. > This needs to be fixed. either have to read " order by notification_id" so > that it gives correct order. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order
[ https://issues.apache.org/jira/browse/AMBARI-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900142#comment-15900142 ] amarnathreddy commented on AMBARI-20157: Code review request - https://reviews.apache.org/r/57304/ > Ambari sends SNMP notifications in incorrect order > -- > > Key: AMBARI-20157 > URL: https://issues.apache.org/jira/browse/AMBARI-20157 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-20157 > > > Ambari sends notifications in wrong order. ideally first generated Alert > should be notified first. > This issue is reproducible in straight steps. > 1. Have 4 to 5 alerts generated in short span of time. > 2. when Ambari notifier thread queries Database with the query like "select * > from alert_notice where notify_state = 'PENDING'" > This query returns last one first. > Ex: > 2066 51 4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26 > 2065 51 4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa > 2064 51 4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8 > 2063 51 4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909 > 2062 51 4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e > 2061 51 4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89 > So Notified threads loops that list and sends one by one. > This needs to be fixed. either have to read " order by notification_id" so > that it gives correct order. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20329) After restarting Ranger, PAM files are overwritten by default template
[ https://issues.apache.org/jira/browse/AMBARI-20329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-20329: -- Status: Open (was: Patch Available) > After restarting Ranger, PAM files are overwritten by default template > -- > > Key: AMBARI-20329 > URL: https://issues.apache.org/jira/browse/AMBARI-20329 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > > AMBARI-18425 add PAM support for ranger authentication in Ambari, but every > time restart ranger-admin it will generate the files again, which will > overwrite the user change. Need to check first if these files already exist, > do not generate again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20349) When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF Process alert fails
Robert Levas created AMBARI-20349:
-
Summary: When SPNEGO authentication is enabled for Hadoop in a
cluster with NN HA, PXF Process alert fails
Key: AMBARI-20349
URL: https://issues.apache.org/jira/browse/AMBARI-20349
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.5.0
When SPNEGO authentication is enabled for Hadoop in a cluster where NN HA is
enabled, PXF Process alert fails with the following errors in the
ambari-agent.log file
{noformat}
ERROR 2017-03-07 18:03:58,417 jmx.py:44 - Getting jmx metrics from NN failed.
URL:
http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesy
stem
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
line 41, in get_value_from_jmx
data_dict = json.loads(data)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
353, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
INFO 2017-03-07 18:04:02,769 logger.py:71 - call['ambari-sudo.sh su hdfs -l -s
/bin/bash -c 'curl --negotiate -u : -s
'"'"'http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
1>/tmp/tmphTXg76 2>/tmp/tmp5bm2nM''] {'quiet': False}
INFO 2017-03-07 18:04:02,797 logger.py:71 - call returned (0, '')
ERROR 2017-03-07 18:04:02,798 jmx.py:44 - Getting jmx metrics from NN failed.
URL:
http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
line 41, in get_value_from_jmx
data_dict = json.loads(data)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
353, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
{noformat}
*Cause*
During the test for the {{PXF Process}} alert, the Active NN is found using a
JMX call. This call requires SPNEGO authentication since SPNEGO authentication
is turned on for the Hadoop web interfaces. However, a valid Kerberos ticket is
not found in the configured user's Kerberos ticket cache. In this case, the
configured users is the HDFS user - which technically is not necessary.
This occurs in
{code:title=common-services/PXF/3.0.0/package/alerts/api_status.py:137}
if CLUSTER_ENV_SECURITY in configurations and
configurations[CLUSTER_ENV_SECURITY].lower() == "true":
if 'dfs.nameservices' in configurations[HDFS_SITE]:
namenode_address =
get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
else:
namenode_address =
configurations[HDFS_SITE]['dfs.namenode.http-address']
token = _get_delegation_token(namenode_address,
configurations[HADOOP_ENV_HDFS_USER],
configurations[HADOOP_ENV_HDFS_USER_KEYTAB],
configurations[HADOOP_ENV_HDFS_PRINCIPAL_NAME],
None)
commonPXFHeaders.update({"X-GP-TOKEN": token})
{code}
Inside the call at
{code}
namenode_address =
get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
{code}
*Solution*
Ensure the configured user's Kerberos ticket cache contains a valid ticket
before querying for the active NN. Possibly change the acting user to one
executing the PXF component.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order
[ https://issues.apache.org/jira/browse/AMBARI-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20157. Resolution: Fixed Committed to trunk > Ambari sends SNMP notifications in incorrect order > -- > > Key: AMBARI-20157 > URL: https://issues.apache.org/jira/browse/AMBARI-20157 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-20157 > > > Ambari sends notifications in wrong order. ideally first generated Alert > should be notified first. > This issue is reproducible in straight steps. > 1. Have 4 to 5 alerts generated in short span of time. > 2. when Ambari notifier thread queries Database with the query like "select * > from alert_notice where notify_state = 'PENDING'" > This query returns last one first. > Ex: > 2066 51 4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26 > 2065 51 4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa > 2064 51 4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8 > 2063 51 4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909 > 2062 51 4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e > 2061 51 4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89 > So Notified threads loops that list and sends one by one. > This needs to be fixed. either have to read " order by notification_id" so > that it gives correct order. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
Supreeth Sharma created AMBARI-20337: Summary: Need to show timer while loading coordinator name while bundle creation Key: AMBARI-20337 URL: https://issues.apache.org/jira/browse/AMBARI-20337 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Fix For: 2.5.0 Need to show timer while loading coordinator name while bundle creation. Issue 1 : Some times coordinator name is not fetch even after 5secs. So its better to show timer to indicate that name is getting loaded. Issue 2: If user provides invalid coordinator path, then appropriate error message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20336) Use lowercase of principal for livy
[ https://issues.apache.org/jira/browse/AMBARI-20336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved AMBARI-20336. - Resolution: Not A Problem Seems already fixed > Use lowercase of principal for livy > --- > > Key: AMBARI-20336 > URL: https://issues.apache.org/jira/browse/AMBARI-20336 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898926#comment-15898926
]
wangyaoxin commented on AMBARI-19079:
-
Hi [~rlevas]
The OS is not LinuxONE, but its core is identical with Redhat’s/Centos’s,
therefore HDP and Ambari can run on PPC properly.
HDP needs repack on PPC. For instance,Hadoop code will import jar packages from
JDK; since IBM jar packages and Sun jar packages contain different content,
recompilation is required within IBM JDK.
It would be simple to edit configuration:only needs adding one configuration
into Kerberos. For example, jdk_type, sunor ibm, and –kt.
eg: hbase_master_jaas.conf.j2
{% if java_type == "sun" %}
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
storeKey=true
useTicketCache=false
keyTab="{{master_keytab_path}}"
principal="{{master_jaas_princ}}";
};
{% endif %}
{% if java_type == "ibm" %}
Client {
com.ibm.security.auth.module.Krb5LoginModule required
useKeytab="{{master_keytab_path}}"
principal="{{master_jaas_princ}}"
credsType=both
debug=true;
};
{% endif %}
PPC JDK has two self-contained commands, klist and kinit. The usages of them
are indentical with the ones of Kerberos. eg: kinit -kt (I once mentioned it
must be kint -A -k -t, that was wrong, -kt is also allowed)
It has been completed before that deploying Ambari on PPC platform with
supporting Kerberos. If it is considered that supporting Ambari with kerberos
enabled on PPC platform, I will attach the patch afterwards. My pleasure to
discuss subjects on Kerberos with you, thanks for your patience andtime!
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20303) HiveView2.0: Issues in worksheet
[ https://issues.apache.org/jira/browse/AMBARI-20303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20303: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > HiveView2.0: Issues in worksheet > > > Key: AMBARI-20303 > URL: https://issues.apache.org/jira/browse/AMBARI-20303 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20303.branch-2.5.patch > > > 1. No options to rename worksheet > 2. No option to close worksheet -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[ https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20338: --- Status: Patch Available (was: Open) +1 by [~BuzhorDenys] on the review board > Alert Definition Name with brackets marked as invalid > - > > Key: AMBARI-20338 > URL: https://issues.apache.org/jira/browse/AMBARI-20338 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20338.patch > > > * Go to definition details page "NameNode Heap Usage (Daily)" > * Click Edit definition name > * It's already marked as invalid > *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20324) Wrong permissions on /var/run/ambari-server when not running as root
[ https://issues.apache.org/jira/browse/AMBARI-20324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899327#comment-15899327 ] Björn Busse commented on AMBARI-20324: -- It seems the directory gets created via ambari/ambari-server/src/main/python/ambari_server/serverConfiguration.py:430: os.makedirs(directory, 0755) invoked by ambari/ambari-server/src/main/python/ambari_server/serverConfiguration.py:384: self.check_if_directories_writable([self.OUT_DIR, self.PID_DIR]) By the time the (init-) process is still running as root. One possibility would be to chown() the dir to the ambari-user after creation of that dir > Wrong permissions on /var/run/ambari-server when not running as root > > > Key: AMBARI-20324 > URL: https://issues.apache.org/jira/browse/AMBARI-20324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Björn Busse > > /var/run/ambari-server has wrong permissions when not running as root. > The user under which ambari-server is running (ambari-server.user) should own > /var/run/ambari-server > $ cat /etc/ambari-server/conf/ambari.properties | grep server.user > ambari-server.user=ambari -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20340) Issue with toggling of Execute/Stop button in query page while successful and failure execution of query.
[ https://issues.apache.org/jira/browse/AMBARI-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20340: Status: Patch Available (was: In Progress) > Issue with toggling of Execute/Stop button in query page while successful and > failure execution of query. > - > > Key: AMBARI-20340 > URL: https://issues.apache.org/jira/browse/AMBARI-20340 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20340.branch-2.5.patch > > > Create two tabs in query page and execute query in first tab and switch to > second tab. > The stop button of first tab is visible in second tab. > This scenario have to be handled while successful and failure execution of > query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[ https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899305#comment-15899305 ] Hudson commented on AMBARI-20338: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6961 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6961/]) AMBARI-20338. Alert Definition Name with brackets marked as invalid (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e6dcdf633f3949f8a59203185c8fb65874932e67]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/utils/validator.js * (edit) ambari-web/test/utils/validator_test.js > Alert Definition Name with brackets marked as invalid > - > > Key: AMBARI-20338 > URL: https://issues.apache.org/jira/browse/AMBARI-20338 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20338.patch > > > * Go to definition details page "NameNode Heap Usage (Daily)" > * Click Edit definition name > * It's already marked as invalid > *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20340) Issue with toggling of Execute/Stop button in query page while successful and failure execution of query.
[ https://issues.apache.org/jira/browse/AMBARI-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20340: Attachment: AMBARI-20340.branch-2.5.patch > Issue with toggling of Execute/Stop button in query page while successful and > failure execution of query. > - > > Key: AMBARI-20340 > URL: https://issues.apache.org/jira/browse/AMBARI-20340 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20340.branch-2.5.patch > > > Create two tabs in query page and execute query in first tab and switch to > second tab. > The stop button of first tab is visible in second tab. > This scenario have to be handled while successful and failure execution of > query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[ https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899341#comment-15899341 ] Hudson commented on AMBARI-20338: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1198 (See [https://builds.apache.org/job/Ambari-branch-2.5/1198/]) AMBARI-20338. Alert Definition Name with brackets marked as invalid (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b9451a4b87ab680219d1790d7b2a091e9c330da0]) * (edit) ambari-web/test/utils/validator_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/utils/validator.js > Alert Definition Name with brackets marked as invalid > - > > Key: AMBARI-20338 > URL: https://issues.apache.org/jira/browse/AMBARI-20338 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20338.patch > > > * Go to definition details page "NameNode Heap Usage (Daily)" > * Click Edit definition name > * It's already marked as invalid > *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[
https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899237#comment-15899237
]
Hadoop QA commented on AMBARI-20338:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856560/AMBARI-20338.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10904//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10904//console
This message is automatically generated.
> Alert Definition Name with brackets marked as invalid
> -
>
> Key: AMBARI-20338
> URL: https://issues.apache.org/jira/browse/AMBARI-20338
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20338.patch
>
>
> * Go to definition details page "NameNode Heap Usage (Daily)"
> * Click Edit definition name
> * It's already marked as invalid
> *ER* Name with brackets should not be marked as invalid
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20316) Move breadcrumbs to the separated view
[ https://issues.apache.org/jira/browse/AMBARI-20316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20316: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Move breadcrumbs to the separated view > -- > > Key: AMBARI-20316 > URL: https://issues.apache.org/jira/browse/AMBARI-20316 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20316.patch > > > Breadcrumbs items should be defined in the routes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20341) Main menu visible when cluster not installed
Andrii Tkach created AMBARI-20341: - Summary: Main menu visible when cluster not installed Key: AMBARI-20341 URL: https://issues.apache.org/jira/browse/AMBARI-20341 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[ https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20338: --- Attachment: AMBARI-20338.patch > Alert Definition Name with brackets marked as invalid > - > > Key: AMBARI-20338 > URL: https://issues.apache.org/jira/browse/AMBARI-20338 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20338.patch > > > * Go to definition details page "NameNode Heap Usage (Daily)" > * Click Edit definition name > * It's already marked as invalid > *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[ https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899263#comment-15899263 ] Oleg Nechiporenko commented on AMBARI-20338: Committed to trunk and 2.5 > Alert Definition Name with brackets marked as invalid > - > > Key: AMBARI-20338 > URL: https://issues.apache.org/jira/browse/AMBARI-20338 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20338.patch > > > * Go to definition details page "NameNode Heap Usage (Daily)" > * Click Edit definition name > * It's already marked as invalid > *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20339) JS Lint warning removal
Pallav Kulshreshtha created AMBARI-20339: Summary: JS Lint warning removal Key: AMBARI-20339 URL: https://issues.apache.org/jira/browse/AMBARI-20339 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Pallav Kulshreshtha Assignee: Pallav Kulshreshtha Fix For: 2.5.0 JS Lint warning removal -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20340) Issue with toggling of Execute/Stop button in query page while successful and failure execution of query.
venkat created AMBARI-20340: --- Summary: Issue with toggling of Execute/Stop button in query page while successful and failure execution of query. Key: AMBARI-20340 URL: https://issues.apache.org/jira/browse/AMBARI-20340 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 Create two tabs in query page and execute query in first tab and switch to second tab. The stop button of first tab is visible in second tab. This scenario have to be handled while successful and failure execution of query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20339) JS Lint warning removal
[ https://issues.apache.org/jira/browse/AMBARI-20339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20339: - Attachment: AMBARI-20339-branch-2-5.patch > JS Lint warning removal > --- > > Key: AMBARI-20339 > URL: https://issues.apache.org/jira/browse/AMBARI-20339 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20339-branch-2-5.patch > > > JS Lint warning removal -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20339) JS Lint warning removal
[ https://issues.apache.org/jira/browse/AMBARI-20339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20339: - Status: Patch Available (was: Open) > JS Lint warning removal > --- > > Key: AMBARI-20339 > URL: https://issues.apache.org/jira/browse/AMBARI-20339 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20339-branch-2-5.patch > > > JS Lint warning removal -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20339) JS Lint warning removal
[
https://issues.apache.org/jira/browse/AMBARI-20339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899335#comment-15899335
]
Hadoop QA commented on AMBARI-20339:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856581/AMBARI-20339-branch-2-5.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 test build failed in
contrib/views/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10905//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10905//console
This message is automatically generated.
> JS Lint warning removal
> ---
>
> Key: AMBARI-20339
> URL: https://issues.apache.org/jira/browse/AMBARI-20339
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-20339-branch-2-5.patch
>
>
> JS Lint warning removal
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
Oleg Nechiporenko created AMBARI-20338: -- Summary: Alert Definition Name with brackets marked as invalid Key: AMBARI-20338 URL: https://issues.apache.org/jira/browse/AMBARI-20338 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Priority: Critical Fix For: 2.5.0 * Go to definition details page "NameNode Heap Usage (Daily)" * Click Edit definition name * It's already marked as invalid *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[
https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899338#comment-15899338
]
Hadoop QA commented on AMBARI-20338:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856560/AMBARI-20338.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/10906//console
This message is automatically generated.
> Alert Definition Name with brackets marked as invalid
> -
>
> Key: AMBARI-20338
> URL: https://issues.apache.org/jira/browse/AMBARI-20338
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20338.patch
>
>
> * Go to definition details page "NameNode Heap Usage (Daily)"
> * Click Edit definition name
> * It's already marked as invalid
> *ER* Name with brackets should not be marked as invalid
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20324) Wrong permissions on /var/run/ambari-server when not running as root
[ https://issues.apache.org/jira/browse/AMBARI-20324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899337#comment-15899337 ] Björn Busse commented on AMBARI-20324: -- Another possiblity is to switch to the ambari user early, maybe already before the python script gets invoked in /etc/init.d/ambari-server > Wrong permissions on /var/run/ambari-server when not running as root > > > Key: AMBARI-20324 > URL: https://issues.apache.org/jira/browse/AMBARI-20324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Björn Busse > > /var/run/ambari-server has wrong permissions when not running as root. > The user under which ambari-server is running (ambari-server.user) should own > /var/run/ambari-server > $ cat /etc/ambari-server/conf/ambari.properties | grep server.user > ambari-server.user=ambari -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed
[ https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899356#comment-15899356 ] Hudson commented on AMBARI-20319: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6962 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6962/]) AMBARI-20319 Server startup script keeps waiting even if DB consistency (lpuskas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c21f77dfb6ca4fdd012af4313696eabcc11c1fbc]) * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/python/ambari_server/utils.py > Server startup script keeps waiting even if DB consistency has failed > - > > Key: AMBARI-20319 > URL: https://issues.apache.org/jira/browse/AMBARI-20319 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Minor > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-20319-Startup_errors-trunk-v1.patch > > > The current logic of the Ambari server startup script: > 1. Wait for java server process PID > 2. Java process starts Database check > 3. Script waits until UI becomes available or timeout occurs > If DB check fails, the script waits some 50 seconds for the UI, before > timeout occurs, although it should fail instantly in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20341) Main menu visible when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20341: -- Attachment: main_menu_views.png > Main menu visible when cluster not installed > > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899373#comment-15899373 ] Aleksandr Kovalenko commented on AMBARI-20341: -- +1 for the patch > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20342: - Status: Patch Available (was: Open) > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20342: - Attachment: AMBARI-20342_trunk.patch > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20341: -- Attachment: AMBARI-20341.patch > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899370#comment-15899370 ] Andrii Tkach commented on AMBARI-20341: --- 20575 passing (34s) 153 pending > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20341: -- Status: Patch Available (was: Open) > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
Padma Priya Nagaraj created AMBARI-20342: Summary: WFM:Performance improvement for adding node on a decision node in large workflow. Key: AMBARI-20342 URL: https://issues.apache.org/jira/browse/AMBARI-20342 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Performance improvement on adding node to large workflow on lower part of decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed
[ https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899509#comment-15899509 ] Hudson commented on AMBARI-20319: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1199 (See [https://builds.apache.org/job/Ambari-branch-2.5/1199/]) AMBARI-20319 Server startup script keeps waiting even if DB consistency (lpuskas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4df38c35f42a632dd822c6c59e4e520f6caad8fd]) * (edit) ambari-server/src/main/python/ambari_server/utils.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/python/ambari_server_main.py > Server startup script keeps waiting even if DB consistency has failed > - > > Key: AMBARI-20319 > URL: https://issues.apache.org/jira/browse/AMBARI-20319 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Minor > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-20319-Startup_errors-trunk-v1.patch > > > The current logic of the Ambari server startup script: > 1. Wait for java server process PID > 2. Java process starts Database check > 3. Script waits until UI becomes available or timeout occurs > If DB check fails, the script waits some 50 seconds for the UI, before > timeout occurs, although it should fail instantly in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required
Kshitij Badani created AMBARI-20343: --- Summary: Zeppelin: Configure both Hive and Hive interactive interpreters whenever required Key: AMBARI-20343 URL: https://issues.apache.org/jira/browse/AMBARI-20343 Project: Ambari Issue Type: Bug Components: blueprints Affects Versions: 2.5.0 Reporter: Kshitij Badani Fix For: 2.5.0 Currently only jdbc(hive) is present in the interpreter config. But lets say if we have only HSI (hive server interactive) present on our cluster , or if we have both HSI and Hive present then we need some changes to the way interpreters are being defined We should use %jdbc(hive) refer Hive interactive when only Hive interactive is present in the cluster. Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive interactive based on the availability of Hive/Hive interactive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[
https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899409#comment-15899409
]
Hadoop QA commented on AMBARI-20341:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856590/AMBARI-20341.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10907//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10907//console
This message is automatically generated.
> Main menu incorrectly displayed when cluster not installed
> --
>
> Key: AMBARI-20341
> URL: https://issues.apache.org/jira/browse/AMBARI-20341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-20341.patch, main_menu_views.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed
[ https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-20319: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Server startup script keeps waiting even if DB consistency has failed > - > > Key: AMBARI-20319 > URL: https://issues.apache.org/jira/browse/AMBARI-20319 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Minor > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-20319-Startup_errors-trunk-v1.patch > > > The current logic of the Ambari server startup script: > 1. Wait for java server process PID > 2. Java process starts Database check > 3. Script waits until UI becomes available or timeout occurs > If DB check fails, the script waits some 50 seconds for the UI, before > timeout occurs, although it should fail instantly in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20338) Alert Definition Name with brackets marked as invalid
[ https://issues.apache.org/jira/browse/AMBARI-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20338: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Alert Definition Name with brackets marked as invalid > - > > Key: AMBARI-20338 > URL: https://issues.apache.org/jira/browse/AMBARI-20338 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20338.patch > > > * Go to definition details page "NameNode Heap Usage (Daily)" > * Click Edit definition name > * It's already marked as invalid > *ER* Name with brackets should not be marked as invalid -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20335) Kerberos identity reference not working for ranger-audit property in hbase
[
https://issues.apache.org/jira/browse/AMBARI-20335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20335:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit fddf8fd006296642d7444f3318bef564f95b0ffe
Author: Robert Levas
Date: Tue Mar 7 09:37:14 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit 225edb97f91428be6426f50b794ba051df2bb65e
Author: Robert Levas
Date: Tue Mar 7 10:03:12 2017 -0500
{noformat}
> Kerberos identity reference not working for ranger-audit property in hbase
> --
>
> Key: AMBARI-20335
> URL: https://issues.apache.org/jira/browse/AMBARI-20335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-20335_branch-2.5_01.patch,
> AMBARI-20335_trunk_01.patch
>
>
> From stack 2.5 onwards
> {{xasecure.audit.jaas.Client.option.principal/ranger-hbase-audit}} needs to
> have principal value available under
> {{hbase.master.kerberos.principal/hbase-site}}
> To achieve that added below block of code under hbase
> [kerberos.json|https://github.com/apache/ambari/blob/branch-2.5/ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json]
> {noformat}
> {
> "name": "/HBASE/HBASE_MASTER/hbase_master_hbase",
> "principal": {
> "configuration":
> "ranger-hbase-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hbase-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {noformat}
> But on test cluster,
> {{xasecure.audit.jaas.Client.option.principal/ranger-hbase-audit}} property
> is not showing the expected value. It is showing the principal/keytab values
> of {{ams_hbase_master_hbase}} identity.
> Because of wrong reference of principal audit to solr is not working in
> kerberos environment, as security.json have below entry instead of
> {{hb...@example.com}}
> {noformat}
> "amshb...@example.com":[
> "ranger_audit_user",
> "dev"]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Attachment: AMBARI-19835_2.patch > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Attachment: (was: AMBARI-19835_2.patch) > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20335) Kerberos identity reference not working for ranger-audit property in hbase
[
https://issues.apache.org/jira/browse/AMBARI-20335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899598#comment-15899598
]
Hudson commented on AMBARI-20335:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6963 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6963/])
AMBARI-20335. Kerberos identity reference not working for ranger-audit (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fddf8fd006296642d7444f3318bef564f95b0ffe])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/kerberos.json
* (edit)
ambari-server/src/test/resources/kerberos/test_kerberos_descriptor_2_5_infra_solr.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
> Kerberos identity reference not working for ranger-audit property in hbase
> --
>
> Key: AMBARI-20335
> URL: https://issues.apache.org/jira/browse/AMBARI-20335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-20335_branch-2.5_01.patch,
> AMBARI-20335_trunk_01.patch
>
>
> From stack 2.5 onwards
> {{xasecure.audit.jaas.Client.option.principal/ranger-hbase-audit}} needs to
> have principal value available under
> {{hbase.master.kerberos.principal/hbase-site}}
> To achieve that added below block of code under hbase
> [kerberos.json|https://github.com/apache/ambari/blob/branch-2.5/ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json]
> {noformat}
> {
> "name": "/HBASE/HBASE_MASTER/hbase_master_hbase",
> "principal": {
> "configuration":
> "ranger-hbase-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hbase-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {noformat}
> But on test cluster,
> {{xasecure.audit.jaas.Client.option.principal/ranger-hbase-audit}} property
> is not showing the expected value. It is showing the principal/keytab values
> of {{ams_hbase_master_hbase}} identity.
> Because of wrong reference of principal audit to solr is not working in
> kerberos environment, as security.json have below entry instead of
> {{hb...@example.com}}
> {noformat}
> "amshb...@example.com":[
> "ranger_audit_user",
> "dev"]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Attachment: AMBARI-20344.patch
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Status: Patch Available (was: Open)
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Updated] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20322: Status: Patch Available (was: Open) > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899564#comment-15899564 ] Andrii Tkach commented on AMBARI-20341: --- committed to trunk > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20341: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20339) JS Lint warning removal
[ https://issues.apache.org/jira/browse/AMBARI-20339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20339: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > JS Lint warning removal > --- > > Key: AMBARI-20339 > URL: https://issues.apache.org/jira/browse/AMBARI-20339 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20339-branch-2-5.patch > > > JS Lint warning removal -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20323: --- Attachment: AMBARI-20323.3.patch > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20323: --- Attachment: AMBARI-20323.4.patch > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Component/s: ambari-server
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
>
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Status: Patch Available (was: Open) > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Status: Open (was: Patch Available) > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20323: --- Attachment: AMBARI-20323.2.patch > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reassigned AMBARI-20322: --- Assignee: Dmytro Sen > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20322: Attachment: AMBARI-20322.patch > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[
https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899607#comment-15899607
]
Hadoop QA commented on AMBARI-20322:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856612/AMBARI-20322.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/10908//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10908//console
This message is automatically generated.
> HDP 3.0 TP - create Service Advisor for Slider
> --
>
> Key: AMBARI-20322
> URL: https://issues.apache.org/jira/browse/AMBARI-20322
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
> Attachments: AMBARI-20322.patch
>
>
> Create a Service Advisor script for Slider in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten
> from HDP 2.0.6 through HDP 2.6
> Slider is being added to the HDP 3.0 stack temporarily in order to unblock
> Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We
> may still keep Slider as a Service, but it may move as a component of YARN
> instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
Dmitry Lysnichenko created AMBARI-20344:
---
Summary: RU: MR2 service check failed during rolling upgrade
Key: AMBARI-20344
URL: https://issues.apache.org/jira/browse/AMBARI-20344
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Blocker
During RU MapReduce Service check failed with exception:
{code:java}
17/02/25 14:18:24 INFO service.AbstractService: Service
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state STARTED;
cause: java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
at
org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at
org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
... 35 more
Caused by: java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
... 36 more
17/02/25 14:18:24 INFO service.AbstractService: Service
org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Class
org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
at
org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at
org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at
[jira] [Commented] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899747#comment-15899747
]
Hudson commented on AMBARI-20344:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6965 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6965/])
AMBARI-20344. RU: MR2 service check failed during rolling upgrade
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=245fda34c2b61cff267f024551fe3dc52c2bb1a0])
* (edit)
ambari-server/src/main/resources/common-services/SLIDER/0.60.0.2.2/package/scripts/service_check.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
>
[jira] [Updated] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required
[ https://issues.apache.org/jira/browse/AMBARI-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-20343: Assignee: Renjith Kamath Status: Patch Available (was: Open) > Zeppelin: Configure both Hive and Hive interactive interpreters whenever > required > - > > Key: AMBARI-20343 > URL: https://issues.apache.org/jira/browse/AMBARI-20343 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-20343-branch-2.5-v1.patch > > > Currently only jdbc(hive) is present in the interpreter config. But lets say > if we have only HSI (hive server interactive) present on our cluster , or if > we have both HSI and Hive present then we need some changes to the way > interpreters are being defined > We should use %jdbc(hive) refer Hive interactive when only Hive interactive > is present in the cluster. > Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive > interactive based on the availability of Hive/Hive interactive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required
[ https://issues.apache.org/jira/browse/AMBARI-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-20343: Attachment: AMBARI-20343-branch-2.5-v1.patch > Zeppelin: Configure both Hive and Hive interactive interpreters whenever > required > - > > Key: AMBARI-20343 > URL: https://issues.apache.org/jira/browse/AMBARI-20343 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-20343-branch-2.5-v1.patch > > > Currently only jdbc(hive) is present in the interpreter config. But lets say > if we have only HSI (hive server interactive) present on our cluster , or if > we have both HSI and Hive present then we need some changes to the way > interpreters are being defined > We should use %jdbc(hive) refer Hive interactive when only Hive interactive > is present in the cluster. > Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive > interactive based on the availability of Hive/Hive interactive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Fix Version/s: 2.5.0
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException:
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException:
[jira] [Commented] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899654#comment-15899654
]
Dmitry Lysnichenko commented on AMBARI-20344:
-
Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
3bc3d6861a..7e8a8150e8 branch-2.5 -> branch-2.5
98f35228f1..245fda34c2 trunk -> trunk
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Priority: Major (was: Critical)
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Commented] (AMBARI-20339) JS Lint warning removal
[ https://issues.apache.org/jira/browse/AMBARI-20339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899663#comment-15899663 ] Hudson commented on AMBARI-20339: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6964 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6964/]) AMBARI-20339. JS Lint warning removal (pallavkul) (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=98f35228f1438b07076ffb33bfa61ea36011d403]) * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/job.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/hdfs-viewer.js * (edit) contrib/views/hive20/src/main/resources/ui/.jshintrc * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/transformer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/saved-query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/udf-new.js * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer-force.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/file-resource.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/edit-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/models/table-property.js * (edit) contrib/views/hive20/src/main/resources/ui/app/router.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/savedqueries.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/stats-service.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/table-advanced-settings.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-editor.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/export-result.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/table-operations.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/table-advanced-settings.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/log.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/table-info.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/jobs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/helpers/extract-value.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/jobs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/udf-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-result-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/create-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/job-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/settings.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/service-check.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/upload-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/upload-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/udf.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/udf.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/validated-text-field.js * (edit) contrib/views/hive20/src/main/resources/ui/app/configs/datatypes.js * (edit) contrib/views/hive20/src/main/resources/ui/app/helpers/format-column-size.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/notification-message.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/new.js * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/enhancer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/fileresource-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/list-filter.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/table/edit.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/visual-explain.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/udfs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/controllers/service-check.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/saved-queries.js > JS Lint warning removal > --- > > Key: AMBARI-20339 > URL: https://issues.apache.org/jira/browse/AMBARI-20339 > Project: Ambari > Issue Type: Bug > Components:
[jira] [Commented] (AMBARI-20341) Main menu incorrectly displayed when cluster not installed
[ https://issues.apache.org/jira/browse/AMBARI-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899662#comment-15899662 ] Hudson commented on AMBARI-20341: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6964 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6964/]) AMBARI-20341 Main menu incorrectly displayed when cluster not installed. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=137613da0acc109ebd6d69e51013a0b8212040b2]) * (edit) ambari-web/app/views/application.js * (edit) ambari-web/app/styles/top-nav.less > Main menu incorrectly displayed when cluster not installed > -- > > Key: AMBARI-20341 > URL: https://issues.apache.org/jira/browse/AMBARI-20341 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20341.patch, main_menu_views.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[
https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899711#comment-15899711
]
Hadoop QA commented on AMBARI-19835:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856613/AMBARI-19835_2.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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10910//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10910//console
This message is automatically generated.
> HDP 3.0 support for Slider with configs, kerberos, widgets, metrics,
> quicklinks, and themes
> ---
>
> Key: AMBARI-19835
> URL: https://issues.apache.org/jira/browse/AMBARI-19835
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
> Attachments: AMBARI-19835_2.patch
>
>
> HDP 3.0 support for Slider with configs, kerberos, widgets, metrics,
> quicklinks, and themes
> Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0
> In HDP 3.0, we have created a new stack definition that does not inherit from
> other stacks, in order to reduce the complexity of having to analyze older
> stacks.
> This means that we need to create a service definition (metainfo.xml,
> configs, kerberos, widgets, metrics, quicklinks, and themes) that is
> equivalent to what is inherit and deleted from all of the previous stacks.
> A merge needs to account for additions, overrides, and deletions.
> metainfo.xml and configs perform a merge of older versions
> kerberos.json always seems to override the previous file
> Because the bits for this service may not yet be available in the HDP 3.0
> repo,
> the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER
> (which uses inheritance) is equivalent to the flattening of
> /api/v1/stacks/HDP/versions/3.0/services/SLIDER .
> Please take a look at how this was done for ZK, HDFS, and YARN/MR.
> This means that you will not be able to actually install the service for now,
> but can still perform validation during the Install Wizard that the correct
> components and configs show up.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899764#comment-15899764
]
Hudson commented on AMBARI-20344:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1201 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1201/])
AMBARI-20344. RU: MR2 service check failed during rolling upgrade
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7e8a8150e8e103e1835c72cfd8bcc65a623b6d46])
* (edit)
ambari-server/src/main/resources/common-services/SLIDER/0.60.0.2.2/package/scripts/service_check.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
>
[jira] [Updated] (AMBARI-20344) RU: MR2 service check failed during rolling upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20344:
Priority: Critical (was: Blocker)
> RU: MR2 service check failed during rolling upgrade
> ---
>
> Key: AMBARI-20344
> URL: https://issues.apache.org/jira/browse/AMBARI-20344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-20344.patch
>
>
> During RU MapReduce Service check failed with exception:
> {code:java}
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl failed in state
> STARTED; cause: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
> at
> org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:160)
> at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
> at
> org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:188)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceStart(ResourceMgrDelegate.java:109)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:98)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1260)
> at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1256)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapreduce.Job.connect(Job.java:1255)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1284)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
> at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
> at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
> at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not
> found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2195)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2219)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> ... 36 more
> 17/02/25 14:18:24 INFO service.AbstractService: Service
> org.apache.hadoop.mapred.ResourceMgrDelegate failed in state STARTED; cause:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider not found
> java.lang.RuntimeException: java.lang.RuntimeException:
>
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[
https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899656#comment-15899656
]
Hadoop QA commented on AMBARI-20323:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856623/AMBARI-20323.3.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 3 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-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10909//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10909//console
This message is automatically generated.
> Commands timed-out on ambari host without any error logs
>
>
> Key: AMBARI-20323
> URL: https://issues.apache.org/jira/browse/AMBARI-20323
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch,
> AMBARI-20323.4.patch, AMBARI-20323.patch
>
>
> Ambari-agent stop execution commands. It is happend because of threads
> blocking due to broken multiprocessing.Queue after killing
> StatusCommandsExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20335) Kerberos identity reference not working for ranger-audit property in hbase
[
https://issues.apache.org/jira/browse/AMBARI-20335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899676#comment-15899676
]
Hudson commented on AMBARI-20335:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1200 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1200/])
AMBARI-20335. Kerberos identity reference not working for ranger-audit (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=225edb97f91428be6426f50b794ba051df2bb65e])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/kerberos.json
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/test/resources/kerberos/test_kerberos_descriptor_2_5_infra_solr.json
> Kerberos identity reference not working for ranger-audit property in hbase
> --
>
> Key: AMBARI-20335
> URL: https://issues.apache.org/jira/browse/AMBARI-20335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-20335_branch-2.5_01.patch,
> AMBARI-20335_trunk_01.patch
>
>
> From stack 2.5 onwards
> {{xasecure.audit.jaas.Client.option.principal/ranger-hbase-audit}} needs to
> have principal value available under
> {{hbase.master.kerberos.principal/hbase-site}}
> To achieve that added below block of code under hbase
> [kerberos.json|https://github.com/apache/ambari/blob/branch-2.5/ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json]
> {noformat}
> {
> "name": "/HBASE/HBASE_MASTER/hbase_master_hbase",
> "principal": {
> "configuration":
> "ranger-hbase-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hbase-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {noformat}
> But on test cluster,
> {{xasecure.audit.jaas.Client.option.principal/ranger-hbase-audit}} property
> is not showing the expected value. It is showing the principal/keytab values
> of {{ams_hbase_master_hbase}} identity.
> Because of wrong reference of principal audit to solr is not working in
> kerberos environment, as security.json have below entry instead of
> {{hb...@example.com}}
> {noformat}
> "amshb...@example.com":[
> "ranger_audit_user",
> "dev"]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20339) JS Lint warning removal
[ https://issues.apache.org/jira/browse/AMBARI-20339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899677#comment-15899677 ] Hudson commented on AMBARI-20339: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1200 (See [https://builds.apache.org/job/Ambari-branch-2.5/1200/]) AMBARI-20339. JS Lint warning removal (pallavkul) (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3bc3d6861a634c775a87881ab4eda67d06b676bc]) * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/new.js * (edit) contrib/views/hive20/src/main/resources/ui/app/helpers/extract-value.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-result-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/router.js * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer-force.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/udfs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/file-resource.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/upload-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query/log.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/savedqueries.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/jobs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/visual-explain.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/udf-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/hdfs-viewer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/validated-text-field.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/job-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/table-operations.js * (edit) contrib/views/hive20/src/main/resources/ui/.jshintrc * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/transformer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/saved-queries.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/udf-new.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/upload-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/service-check.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/export-result.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/fileresource-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/list-filter.js * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/renderer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/jobs.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/table-info.js * (edit) contrib/views/hive20/src/main/resources/ui/app/utils/hive-explainer/enhancer.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/table/edit.js * (edit) contrib/views/hive20/src/main/resources/ui/app/configs/datatypes.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/table-advanced-settings.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/services/udf.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/udf.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-editor.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/settings.js * (edit) contrib/views/hive20/src/main/resources/ui/app/helpers/format-column-size.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/job.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/saved-query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/edit-table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/table.js * (edit) contrib/views/hive20/src/main/resources/ui/app/controllers/service-check.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/notification-message.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/table-advanced-settings.js * (edit) contrib/views/hive20/src/main/resources/ui/app/services/stats-service.js * (edit) contrib/views/hive20/src/main/resources/ui/app/models/table-property.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/create-table.js > JS Lint warning removal > --- > > Key: AMBARI-20339 > URL: https://issues.apache.org/jira/browse/AMBARI-20339 > Project: Ambari > Issue Type: Bug > Components:
[jira] [Created] (AMBARI-20345) Alert Event Publisher Executor Doesn't Scale Threads
Jonathan Hurley created AMBARI-20345:
Summary: Alert Event Publisher Executor Doesn't Scale Threads
Key: AMBARI-20345
URL: https://issues.apache.org/jira/browse/AMBARI-20345
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.5.0
The event bus which is used to handling incoming {{AlertEvent}} events is
incorrectly initialized and can never scale from the core number of threads.
This is because it uses an unbounded queued. From the
[ThreadPoolExecutor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
documentation:
{quote}
A ThreadPoolExecutor will automatically adjust the pool size (see
getPoolSize()) according to the bounds set by corePoolSize (see
getCorePoolSize()) and maximumPoolSize (see getMaximumPoolSize()). When a new
task is submitted in method execute(java.lang.Runnable), and fewer than
corePoolSize threads are running, a new thread is created to handle the
request, even if other worker threads are idle. If there are more than
corePoolSize but less than maximumPoolSize threads running, *a new thread will
be created only if the queue is full.*
{quote}
We should switch to a configurable, bounded queue so that this property can be
utilized in large clusters where more than the default of 2 core threads is
needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20345) Alert Event Publisher Executor Doesn't Scale Threads
[
https://issues.apache.org/jira/browse/AMBARI-20345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20345:
-
Status: Patch Available (was: Open)
> Alert Event Publisher Executor Doesn't Scale Threads
>
>
> Key: AMBARI-20345
> URL: https://issues.apache.org/jira/browse/AMBARI-20345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-20345.patch
>
>
> The event bus which is used to handling incoming {{AlertEvent}} events is
> incorrectly initialized and can never scale from the core number of threads.
> This is because it uses an unbounded queued. From the
> [ThreadPoolExecutor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> documentation:
> {quote}
> A ThreadPoolExecutor will automatically adjust the pool size (see
> getPoolSize()) according to the bounds set by corePoolSize (see
> getCorePoolSize()) and maximumPoolSize (see getMaximumPoolSize()). When a new
> task is submitted in method execute(java.lang.Runnable), and fewer than
> corePoolSize threads are running, a new thread is created to handle the
> request, even if other worker threads are idle. If there are more than
> corePoolSize but less than maximumPoolSize threads running, *a new thread
> will be created only if the queue is full.*
> {quote}
> We should switch to a configurable, bounded queue so that this property can
> be utilized in large clusters where more than the default of 2 core threads
> is needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used
Miklos Gergely created AMBARI-20346: --- Summary: Log Search Upgrade should modify keystore / truststore path if it wasn't used Key: AMBARI-20346 URL: https://issues.apache.org/jira/browse/AMBARI-20346 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.5.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 The default path for the truststore / keystore in 2.4 was under /etc/security, which may cause permission problems. If the user haven't used the keystore / truststore, and haven't altered the path yet it should be modified upon upgrade to the new default value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[
https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899774#comment-15899774
]
Hadoop QA commented on AMBARI-20322:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856612/AMBARI-20322.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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10911//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10911//console
This message is automatically generated.
> HDP 3.0 TP - create Service Advisor for Slider
> --
>
> Key: AMBARI-20322
> URL: https://issues.apache.org/jira/browse/AMBARI-20322
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
> Attachments: AMBARI-20322.patch
>
>
> Create a Service Advisor script for Slider in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten
> from HDP 2.0.6 through HDP 2.6
> Slider is being added to the HDP 3.0 stack temporarily in order to unblock
> Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We
> may still keep Slider as a Service, but it may move as a component of YARN
> instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20345) Alert Event Publisher Executor Doesn't Scale Threads
[
https://issues.apache.org/jira/browse/AMBARI-20345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20345:
-
Attachment: AMBARI-20345.patch
> Alert Event Publisher Executor Doesn't Scale Threads
>
>
> Key: AMBARI-20345
> URL: https://issues.apache.org/jira/browse/AMBARI-20345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-20345.patch
>
>
> The event bus which is used to handling incoming {{AlertEvent}} events is
> incorrectly initialized and can never scale from the core number of threads.
> This is because it uses an unbounded queued. From the
> [ThreadPoolExecutor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> documentation:
> {quote}
> A ThreadPoolExecutor will automatically adjust the pool size (see
> getPoolSize()) according to the bounds set by corePoolSize (see
> getCorePoolSize()) and maximumPoolSize (see getMaximumPoolSize()). When a new
> task is submitted in method execute(java.lang.Runnable), and fewer than
> corePoolSize threads are running, a new thread is created to handle the
> request, even if other worker threads are idle. If there are more than
> corePoolSize but less than maximumPoolSize threads running, *a new thread
> will be created only if the queue is full.*
> {quote}
> We should switch to a configurable, bounded queue so that this property can
> be utilized in large clusters where more than the default of 2 core threads
> is needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used
[ https://issues.apache.org/jira/browse/AMBARI-20346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20346: Status: Patch Available (was: In Progress) > Log Search Upgrade should modify keystore / truststore path if it wasn't used > - > > Key: AMBARI-20346 > URL: https://issues.apache.org/jira/browse/AMBARI-20346 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20346.patch > > > The default path for the truststore / keystore in 2.4 was under > /etc/security, which may cause permission problems. If the user haven't used > the keystore / truststore, and haven't altered the path yet it should be > modified upon upgrade to the new default value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used
[ https://issues.apache.org/jira/browse/AMBARI-20346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20346: Attachment: AMBARI-20346.patch > Log Search Upgrade should modify keystore / truststore path if it wasn't used > - > > Key: AMBARI-20346 > URL: https://issues.apache.org/jira/browse/AMBARI-20346 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20346.patch > > > The default path for the truststore / keystore in 2.4 was under > /etc/security, which may cause permission problems. If the user haven't used > the keystore / truststore, and haven't altered the path yet it should be > modified upon upgrade to the new default value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20347) Display Ranger DB backup instruction in sections on the manual step during EU and RU
Di Li created AMBARI-20347: -- Summary: Display Ranger DB backup instruction in sections on the manual step during EU and RU Key: AMBARI-20347 URL: https://issues.apache.org/jira/browse/AMBARI-20347 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Priority: Minor Fix For: trunk it's currently displayed as one paragraph, it's clearer to display the instruction in sections. this is to update upgrade xml files for such display. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20347) Display Ranger DB backup instruction in sections on the manual step during EU and RU
[ https://issues.apache.org/jira/browse/AMBARI-20347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20347: --- Status: Patch Available (was: Open) > Display Ranger DB backup instruction in sections on the manual step during EU > and RU > > > Key: AMBARI-20347 > URL: https://issues.apache.org/jira/browse/AMBARI-20347 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20347.patch > > > it's currently displayed as one paragraph, it's clearer to display the > instruction in sections. this is to update upgrade xml files for such display. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20347) Display Ranger DB backup instruction in sections on the manual step during EU and RU
[ https://issues.apache.org/jira/browse/AMBARI-20347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20347: --- Attachment: AMBARI-20347.patch > Display Ranger DB backup instruction in sections on the manual step during EU > and RU > > > Key: AMBARI-20347 > URL: https://issues.apache.org/jira/browse/AMBARI-20347 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20347.patch > > > it's currently displayed as one paragraph, it's clearer to display the > instruction in sections. this is to update upgrade xml files for such display. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20348) Discard/Save buttons for service configs are always enabled if custom property is overridden with empty value
Andrii Babiichuk created AMBARI-20348: - Summary: Discard/Save buttons for service configs are always enabled if custom property is overridden with empty value Key: AMBARI-20348 URL: https://issues.apache.org/jira/browse/AMBARI-20348 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.5.0 *STR* # Create custom property for any service # Create override for this property (override value should be empty) # Save changes *Result* Discard and Save button on configs page of the mentioned service are always enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
