[jira] [Commented] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418434#comment-15418434
]
DIPAYAN BHOWMICK commented on AMBARI-18128:
---
Added a new patch which fixes an issue in saving the cluster type.
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.1.branch-2.4.patch,
> AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-18128:
--
Attachment: AMBARI-18128.1.branch-2.4.patch
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.1.branch-2.4.patch,
> AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-18128:
--
Attachment: (was: AMBARI-18128.branch-2.4.patch)
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-18128:
--
Attachment: AMBARI-18128.branch-2.4.patch
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated AMBARI-17999: Status: Patch Available (was: Open) > Typo in property name "yarn.nodemanager.log.retain-second", should be > "seconds" > --- > > Key: AMBARI-17999 > URL: https://issues.apache.org/jira/browse/AMBARI-17999 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Ying Zhang >Assignee: Masahiro Tanaka >Priority: Minor > Attachments: AMBARI-17999.001.patch > > > In yarn-site.xml, property name "yarn.nodemanager.log.retain-second" is > wrong, should be "yarn.nodemanager.log.retain-seconds" instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated AMBARI-17999: Attachment: AMBARI-17999.001.patch > Typo in property name "yarn.nodemanager.log.retain-second", should be > "seconds" > --- > > Key: AMBARI-17999 > URL: https://issues.apache.org/jira/browse/AMBARI-17999 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Ying Zhang >Assignee: Masahiro Tanaka >Priority: Minor > Attachments: AMBARI-17999.001.patch > > > In yarn-site.xml, property name "yarn.nodemanager.log.retain-second" is > wrong, should be "yarn.nodemanager.log.retain-seconds" instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk : [bf80a34ee1f5c8d4854053e29c6ebefa2f6a9fa5|https://github.com/apache/ambari/commit/bf80a34ee1f5c8d4854053e29c6ebefa2f6a9fa5] > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18099.1.patch, AMBARI-18099.2.patch, > AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418170#comment-15418170 ] Hudson commented on AMBARI-18120: - FAILURE: Integrated in Ambari-trunk-Commit #5512 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5512/]) AMBARI-18120. Ambari upgrade to Ambari 2.4.0.0 did not change the (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dc14815f13c465f6da7898c4b42a1fe63e8bb0ff]) * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18125: --- Attachment: AMBARI-18125.patch > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18125.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18125: --- Attachment: (was: AMBARI-18093-2.patch) > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18125.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables for AMS.
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Status: Patch Available (was: In Progress)
> Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093-2.4.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables for AMS.
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Attachment: AMBARI-18093-2.4.patch
> Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093-2.4.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18133) Error message displays mesage key instead of actual message
[ https://issues.apache.org/jira/browse/AMBARI-18133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18133: Status: Patch Available (was: In Progress) > Error message displays mesage key instead of actual message > --- > > Key: AMBARI-18133 > URL: https://issues.apache.org/jira/browse/AMBARI-18133 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-18133.patch, ErrorMessageWithFix.jpg, > MessageKeyInsteadOfMessage.jpg > > > 1. Click on a user in the Ambari Admin view -> Users. > 2. Under Local Group Membership, add a group that does not exist. > 3. The error message returns the message key instead of the actual message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables for AMS.
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Attachment: (was: AMBARI-18093.patch)
> Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables for AMS.
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Description:
TTL changes
{code}
timeline.metrics.host.aggregator.ttl : 1 day
timeline.metrics.cluster.aggregator.second.ttl : 3 days
{code}
was:
TTL changes
{code}
timeline.metrics.host.aggregator.ttl : 1 day
timeline.metrics.cluster.aggregator.second.ttl : 3 days
{code}
HBase policy changes
Remove the following
{code}
# HBase compaction policy enabled
export HBASE_NORMALIZATION_ENABLED=True
# HBase compaction policy enabled
export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
{code}
> Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables for AMS.
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Summary: Reduce TTL for high precision tables for AMS. (was: Reduce TTL
for high precision tables and remove HBase policy setters in AMS config)
> Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
> HBase policy changes
> Remove the following
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables and remove HBase policy setters in AMS config
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Fix Version/s: (was: 2.5.0)
2.4.0
> Reduce TTL for high precision tables and remove HBase policy setters in AMS
> config
> ---
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
> HBase policy changes
> Remove the following
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables and remove HBase policy setters in AMS config
[
https://issues.apache.org/jira/browse/AMBARI-18093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18093:
---
Status: Open (was: Patch Available)
> Reduce TTL for high precision tables and remove HBase policy setters in AMS
> config
> ---
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18093.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}
> HBase policy changes
> Remove the following
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.
Aravindan Vijayan created AMBARI-18132:
--
Summary: Remove FIFO and Normalizer in ams-env config.
Key: AMBARI-18132
URL: https://issues.apache.org/jira/browse/AMBARI-18132
Project: Ambari
Issue Type: Task
Components: ambari-metrics
Affects Versions: 2.4.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.5.0
It is currently
{code}
# HBase compaction policy enabled
export HBASE_NORMALIZATION_ENABLED=True
# HBase compaction policy enabled
export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18130) Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers
[ https://issues.apache.org/jira/browse/AMBARI-18130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18130: - Status: Patch Available (was: Open) > Atlas hooks to include atlas.rest.address config, allow editing in the UI, > and compute value using all Atlas Servers > > > Key: AMBARI-18130 > URL: https://issues.apache.org/jira/browse/AMBARI-18130 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-18130.patch > > > For all of the Atlas hook files (atlas-application.properties), the config > atlas.rest.address needs to be added. > Further, whenever Atlas topology changes (add/move/delete a server), the > atlas.rest.address will need to change. However, we have no mechanism of > recalculating this from the UI, so instead, allow the property to be editable > from the UI for the time being. > Lastly, the current value of atlas.rest.address is incorrect; it should be > csv of http(s):$server:$port from all of the servers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18130) Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers
[ https://issues.apache.org/jira/browse/AMBARI-18130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18130: - Attachment: AMBARI-18130.patch > Atlas hooks to include atlas.rest.address config, allow editing in the UI, > and compute value using all Atlas Servers > > > Key: AMBARI-18130 > URL: https://issues.apache.org/jira/browse/AMBARI-18130 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-18130.patch > > > For all of the Atlas hook files (atlas-application.properties), the config > atlas.rest.address needs to be added. > Further, whenever Atlas topology changes (add/move/delete a server), the > atlas.rest.address will need to change. However, we have no mechanism of > recalculating this from the UI, so instead, allow the property to be editable > from the UI for the time being. > Lastly, the current value of atlas.rest.address is incorrect; it should be > csv of http(s):$server:$port from all of the servers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18130) Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers
Alejandro Fernandez created AMBARI-18130: Summary: Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers Key: AMBARI-18130 URL: https://issues.apache.org/jira/browse/AMBARI-18130 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.4.0 For all of the Atlas hook files (atlas-application.properties), the config atlas.rest.address needs to be added. Further, whenever Atlas topology changes (add/move/delete a server), the atlas.rest.address will need to change. However, we have no mechanism of recalculating this from the UI, so instead, allow the property to be editable from the UI for the time being. Lastly, the current value of atlas.rest.address is incorrect; it should be csv of http(s):$server:$port from all of the servers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[ https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418076#comment-15418076 ] Weiqing Yang commented on AMBARI-18112: --- Failure is not related to the patch > Fix spark.executor.extraLibraryPath to include native gpl library > - > > Key: AMBARI-18112 > URL: https://issues.apache.org/jira/browse/AMBARI-18112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: AMBARI-18112_v0.patch, AMBARI-18112_v1.patch > > > When spark applications run in yarn cluster mode, there is an error from > executors: > - > java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889) > at java.lang.Runtime.loadLibrary0(Runtime.java:849) > at java.lang.System.loadLibrary(System.java:1088) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71) > at java.lang.Class.forName0(Native Method) > ... > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without > native-hadoop. > In the patch, it will set “spark.executor.extraLibraryPath > /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64” > in spark-defaults.conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18125: --- Status: Patch Available (was: Open) > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18093-2.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18125: --- Attachment: AMBARI-18093-2.patch > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18093-2.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18129) Mask trust-store password returned in plain-text by API call
Sangeeta Ravindran created AMBARI-18129:
---
Summary: Mask trust-store password returned in plain-text by API
call
Key: AMBARI-18129
URL: https://issues.apache.org/jira/browse/AMBARI-18129
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Sangeeta Ravindran
Assignee: Sangeeta Ravindran
If a trustore has been configured for Ambari Server, the SSL truststore
password is returned in plain text by the following api call:
https:///api/v1/services/AMBARI/components/AMBARI_SERVER
Sample output:
{
"href" :
"https://:/api/v1/services/AMBARI/components/AMBARI_SERVER",
"RootServiceComponents" : {
"component_name" : "AMBARI_SERVER",
"component_version" : "2.4.0.0",
"server_clock" : 1470943672,
"service_name" : "AMBARI",
"properties" : {
"agent.package.install.task.timeout" : "1800",
"agent.stack.retry.on_repo_unavailability" : "false",
"agent.stack.retry.tries" : "5",
"agent.task.timeout" : "900",
"agent.threadpool.size.max" : "25",
"ambari-server.user" : "root",
"ambari.python.wrap" : "ambari-python-wrap",
"api.ssl" : "true",
"bootstrap.dir" : "/var/run/ambari-server/bootstrap",
"bootstrap.script" :
"/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py",
"bootstrap.setup_agent.script" :
"/usr/lib/python2.6/site-packages/ambari_server/setupAgent.py",
"check_database_skipped" : "false",
"client.api.port" : "8081",
"client.api.ssl.cert_name" : "https.crt",
"client.api.ssl.key_name" : "https.key",
"client.api.ssl.port" : "",
"client.threadpool.size.max" : "25",
"common.services.path" :
"/var/lib/ambari-server/resources/common-services",
"custom.action.definitions" :
"/var/lib/ambari-server/resources/custom_action_definitions",
"extensions.path" : "/var/lib/ambari-server/resources/extensions",
"http.strict-transport-security" : "max-age=31536000",
"http.x-frame-options" : "DENY",
"http.x-xss-protection" : "1; mode=block",
"java.home" : "/usr/jdk64/jdk1.8.0_60",
"java.releases" : "jdk1.8,jdk1.7",
"java.version" : "1.8",
"jce.download.supported" : "true",
"jce.name" : "jce_policy-8.zip",
"jdk.download.supported" : "true",
"jdk.name" : "jdk-8u60-linux-x64.tar.gz",
"jdk1.7.desc" : "Oracle JDK 1.7 + Java Cryptography Extension (JCE)
Policy Files 7",
"jdk1.7.dest-file" : "jdk-7u67-linux-x64.tar.gz",
"jdk1.7.home" : "/usr/jdk64/",
"jdk1.7.jcpol-file" : "UnlimitedJCEPolicyJDK7.zip",
"jdk1.7.jcpol-url" :
"http://public-repo-1.hortonworks.com/ARTIFACTS/UnlimitedJCEPolicyJDK7.zip";,
"jdk1.7.re" : "(jdk.*)/jre",
"jdk1.7.url" :
"http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-7u67-linux-x64.tar.gz";,
"jdk1.8.desc" : "Oracle JDK 1.8 + Java Cryptography Extension (JCE)
Policy Files 8",
"jdk1.8.dest-file" : "jdk-8u60-linux-x64.tar.gz",
"jdk1.8.home" : "/usr/jdk64/",
"jdk1.8.jcpol-file" : "jce_policy-8.zip",
"jdk1.8.jcpol-url" :
"http://public-repo-1.hortonworks.com/ARTIFACTS/jce_policy-8.zip";,
"jdk1.8.re" : "(jdk.*)/jre",
"jdk1.8.url" :
"http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u60-linux-x64.tar.gz";,
"jdk_location" : "https://:/resources/",
"kerberos.keytab.cache.dir" : "/var/lib/ambari-server/data/cache",
"metadata.path" : "/var/lib/ambari-server/resources/stacks",
"mpacks.staging.path" : "/var/lib/ambari-server/resources/mpacks",
"pid.dir" : "/var/run/ambari-server",
"recommendations.artifacts.lifetime" : "1w",
"recommendations.dir" : "/var/run/ambari-server/stack-recommendations",
"resources.dir" : "/var/lib/ambari-server/resources",
"rolling.upgrade.skip.packages.prefixes" : "",
"security.server.disabled.ciphers" :
"TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384|TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384|TLS_RSA_WITH_AES_256_CBC_SHA256|TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384|TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384|TLS_DHE_RSA_WITH_AES_256_CBC_SHA256|TLS_DHE_DSS_WITH_AES_256_CBC_SHA256|TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA|TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA|TLS_RSA_WITH_AES_256_CBC_SHA|TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA|TLS_ECDH_RSA_WITH_AES_256_CBC_SHA|TLS_DHE_RSA_WITH_AES_256_CBC_SHA|TLS_DHE_DSS_WITH_AES_256_CBC_SHA|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256|TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256|TLS_RSA_WITH_AES_128_CBC_SHA256|TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256|TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256|TLS_DHE_RSA_WITH_AES_128_CBC_SHA256|TLS_DHE_DSS_WITH_AES_128_CBC_SHA256|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA|TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA|TLS_RSA_WITH_AES_128_CBC_SHA|TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA|TLS_ECDH_RSA_WITH_AES_128_CBC_SHA|TLS_DHE_RSA_WITH_AES_128_CBC_SHA|TLS_DHE_D
[jira] [Commented] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418017#comment-15418017
]
Hadoop QA commented on AMBARI-18128:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823346/AMBARI-18128.branch-2.4.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/8390//console
This message is automatically generated.
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[
https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418014#comment-15418014
]
Hadoop QA commented on AMBARI-18112:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823351/AMBARI-18112_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/8389//console
This message is automatically generated.
> Fix spark.executor.extraLibraryPath to include native gpl library
> -
>
> Key: AMBARI-18112
> URL: https://issues.apache.org/jira/browse/AMBARI-18112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: AMBARI-18112_v0.patch, AMBARI-18112_v1.patch
>
>
> When spark applications run in yarn cluster mode, there is an error from
> executors:
> -
> java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889)
> at java.lang.Runtime.loadLibrary0(Runtime.java:849)
> at java.lang.System.loadLibrary(System.java:1088)
> at
> com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32)
> at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71)
> at java.lang.Class.forName0(Native Method)
> ...
> org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without
> native-hadoop.
> In the patch, it will set “spark.executor.extraLibraryPath
> /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64”
> in spark-defaults.conf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18100) Add Kerberos Automation documentation to Ambari source tree so it may be versioned
[
https://issues.apache.org/jira/browse/AMBARI-18100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18100:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit c803237635c62aca5d4bfb6c736c6ad0b154e3f1
Author: Robert Levas
Date: Thu Aug 11 17:38:03 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit 075cef90a92841224f168776670290e964e8a3a1
Author: Robert Levas
Date: Thu Aug 11 17:44:54 2016 -0400
{noformat}
> Add Kerberos Automation documentation to Ambari source tree so it may be
> versioned
> ---
>
> Key: AMBARI-18100
> URL: https://issues.apache.org/jira/browse/AMBARI-18100
> Project: Ambari
> Issue Type: Documentation
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: documentation, kerberos, kerberos_descriptor
> Fix For: 2.4.0
>
> Attachments: AMBARI-18100_branch-2.4_01.patch,
> AMBARI-18100_branch-2.4_02.patch, AMBARI-18100_trunk_01.patch,
> AMBARI-18100_trunk_02.patch
>
>
> Add Kerberos Automation documentation to Ambari source tree so it may be
> versioned. This documentation should be added as MD (markdown) files to
> {{.../ambari-server/docs/security/kerberos}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[ https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated AMBARI-18112: -- Attachment: AMBARI-18112_v1.patch > Fix spark.executor.extraLibraryPath to include native gpl library > - > > Key: AMBARI-18112 > URL: https://issues.apache.org/jira/browse/AMBARI-18112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: AMBARI-18112_v0.patch, AMBARI-18112_v1.patch > > > When spark applications run in yarn cluster mode, there is an error from > executors: > - > java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889) > at java.lang.Runtime.loadLibrary0(Runtime.java:849) > at java.lang.System.loadLibrary(System.java:1088) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71) > at java.lang.Class.forName0(Native Method) > ... > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without > native-hadoop. > In the patch, it will set “spark.executor.extraLibraryPath > /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64” > in spark-defaults.conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-18128:
--
Status: Patch Available (was: Open)
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
[
https://issues.apache.org/jira/browse/AMBARI-18128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-18128:
--
Attachment: AMBARI-18128.branch-2.4.patch
> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
> settings.
> IMPACT: Customer not able to edit view after the fact.
> STEPS TO REPRODUCE:
> 1. Create a new instance of a view and save
> 2. try to edit a the instance such as display name.
> 3. You should get stack like:
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException:
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.
DIPAYAN BHOWMICK created AMBARI-18128:
-
Summary: Receiving Error "Cannot save settings" when trying to
edit view settings.
Key: AMBARI-18128
URL: https://issues.apache.org/jira/browse/AMBARI-18128
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.4.0
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
Fix For: 2.4.0
PROBLEM: Receiving Error "Cannot save settings" when trying to edit view
settings.
IMPACT: Customer not able to edit view after the fact.
STEPS TO REPRODUCE:
1. Create a new instance of a view and save
2. try to edit a the instance such as display name.
3. You should get stack like:
{code}
Cannot save settings
java.lang.IllegalArgumentException:
{"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid
URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18120: -- Attachment: AMBARI-18100_trunk_02.patch AMBARI-18100_branch-2.4_02.patch > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18120: -- Attachment: (was: AMBARI-18100_trunk_02.patch) > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18120: -- Attachment: (was: AMBARI-18100_branch-2.4_02.patch) > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18100) Add Kerberos Automation documentation to Ambari source tree so it may be versioned
[
https://issues.apache.org/jira/browse/AMBARI-18100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18100:
--
Attachment: AMBARI-18100_trunk_02.patch
AMBARI-18100_branch-2.4_02.patch
> Add Kerberos Automation documentation to Ambari source tree so it may be
> versioned
> ---
>
> Key: AMBARI-18100
> URL: https://issues.apache.org/jira/browse/AMBARI-18100
> Project: Ambari
> Issue Type: Documentation
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: documentation, kerberos, kerberos_descriptor
> Fix For: 2.4.0
>
> Attachments: AMBARI-18100_branch-2.4_01.patch,
> AMBARI-18100_branch-2.4_02.patch, AMBARI-18100_trunk_01.patch,
> AMBARI-18100_trunk_02.patch
>
>
> Add Kerberos Automation documentation to Ambari source tree so it may be
> versioned. This documentation should be added as MD (markdown) files to
> {{.../ambari-server/docs/security/kerberos}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417926#comment-15417926 ] Alexander Denissov commented on AMBARI-17285: - Correct, however requiring the user to switch between 2 different tabs and copy & paste URLs is not a good experience. Ambari is the tool to make installation easy and transparent, having the user to go through these operations violates this promise and introduces a potential for user errors and failed installations. > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18111) Interactive Query configs are not reset after refresh/back on Install Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417923#comment-15417923 ] Hudson commented on AMBARI-18111: - FAILURE: Integrated in Ambari-trunk-Commit #5510 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5510/]) AMBARI-18111. Interactive Query configs are not reset after refresh/back (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=677e684c59579086f66a6d2dfb2ac95b5bcd831b]) * ambari-web/test/controllers/wizard/step7/assign_master_controller_test.js * ambari-web/app/controllers/wizard/step7_controller.js * ambari-web/app/controllers/wizard.js * ambari-web/app/controllers/wizard/step7/assign_master_controller.js * ambari-web/app/controllers/installer.js * ambari-web/test/controllers/installer_test.js * ambari-web/app/controllers/wizard/step6_controller.js * ambari-web/test/controllers/wizard/step7_test.js * ambari-web/app/routes/installer.js * ambari-web/app/mixins/wizard/assign_master_components.js * ambari-web/app/controllers/wizard/step5_controller.js > Interactive Query configs are not reset after refresh/back on Install Wizard > > > Key: AMBARI-18111 > URL: https://issues.apache.org/jira/browse/AMBARI-18111 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18111.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417924#comment-15417924 ] Hudson commented on AMBARI-18099: - FAILURE: Integrated in Ambari-trunk-Commit #5510 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5510/]) AMBARI-18099. Ranger policies not syncing when Hive-server-Hive2 is (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bf80a34ee1f5c8d4854053e29c6ebefa2f6a9fa5]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/ranger-hive-security.xml > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18099.1.patch, AMBARI-18099.2.patch, > AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18127) Config merge script lower cases log4j properties
[ https://issues.apache.org/jira/browse/AMBARI-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18127: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. > Config merge script lower cases log4j properties > > > Key: AMBARI-18127 > URL: https://issues.apache.org/jira/browse/AMBARI-18127 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: trunk > > Attachments: AMBARI-18127.patch > > > ambari-server/src/main/resources/scripts/takeover_config_merge.py > Uses ConfigParser API which defaults to lower casing the contents of property > files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18127) Config merge script lower cases log4j properties
[ https://issues.apache.org/jira/browse/AMBARI-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417837#comment-15417837 ] Aravindan Vijayan commented on AMBARI-18127: +1 LGTM > Config merge script lower cases log4j properties > > > Key: AMBARI-18127 > URL: https://issues.apache.org/jira/browse/AMBARI-18127 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: trunk > > Attachments: AMBARI-18127.patch > > > ambari-server/src/main/resources/scripts/takeover_config_merge.py > Uses ConfigParser API which defaults to lower casing the contents of property > files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18127) Config merge script lower cases log4j properties
[ https://issues.apache.org/jira/browse/AMBARI-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18127: - Status: Patch Available (was: Open) > Config merge script lower cases log4j properties > > > Key: AMBARI-18127 > URL: https://issues.apache.org/jira/browse/AMBARI-18127 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: trunk > > Attachments: AMBARI-18127.patch > > > ambari-server/src/main/resources/scripts/takeover_config_merge.py > Uses ConfigParser API which defaults to lower casing the contents of property > files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18127) Config merge script lower cases log4j properties
Siddharth Wagle created AMBARI-18127: Summary: Config merge script lower cases log4j properties Key: AMBARI-18127 URL: https://issues.apache.org/jira/browse/AMBARI-18127 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: trunk Attachments: AMBARI-18127.patch ambari-server/src/main/resources/scripts/takeover_config_merge.py Uses ConfigParser API which defaults to lower casing the contents of property files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18127) Config merge script lower cases log4j properties
[ https://issues.apache.org/jira/browse/AMBARI-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18127: - Attachment: AMBARI-18127.patch > Config merge script lower cases log4j properties > > > Key: AMBARI-18127 > URL: https://issues.apache.org/jira/browse/AMBARI-18127 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: trunk > > Attachments: AMBARI-18127.patch > > > ambari-server/src/main/resources/scripts/takeover_config_merge.py > Uses ConfigParser API which defaults to lower casing the contents of property > files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation
Jonathan Hurley created AMBARI-18126:
Summary: Refactor Configuration To Allow For Generation Of
Documentation
Key: AMBARI-18126
URL: https://issues.apache.org/jira/browse/AMBARI-18126
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: trunk
As part of the work for AMBARI-18089, all of the potential properties from
{{ambari.properties}} need a way to be organized and queried in order to
generate documentation.
This Jira proposes to change our disorganized String/String (key/default)
structure found in {{Configuration}}, and instead, have a strongly-coupled
relationship between key/default/type.
Additionally, expose a way to provide extra information in the markdown
(similar to JavaDoc, but geared more for users and not developers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417808#comment-15417808 ] Nate Cole commented on AMBARI-17285: You can change the URLs even if it comes from default. We have provided the identical functionality as the previous version of Ambari, so that aspect should be no different for your users. > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417782#comment-15417782 ] Alexander Denissov commented on AMBARI-17285: - Right. This means that without a fix users will only be able to install HAWQ if they choose the default VDF, which is usually obsolete and refers to the older maintenance versions. A user would have to choose between installing the most recent stack without HAWQ and installing HAWQ with the older stack. This is not a choice we want the users to make, we would like them to be able to install the latest stack with HAWQ right out of the box. > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18118) AlertDefinitionCommand intermittently provides stale configurations
[ https://issues.apache.org/jira/browse/AMBARI-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417774#comment-15417774 ] Hudson commented on AMBARI-18118: - FAILURE: Integrated in Ambari-trunk-Commit #5509 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5509/]) AMBARI-18118. AlertDefinitionCommand intermittently provides stale (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=51bad4583b8efd8e7d8e43bd566ae65393908077]) * ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionHashTest.java * ambari-server/src/main/java/org/apache/ambari/server/agent/AlertDefinitionCommand.java > AlertDefinitionCommand intermittently provides stale configurations > --- > > Key: AMBARI-18118 > URL: https://issues.apache.org/jira/browse/AMBARI-18118 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-18118.patch > > > Existing code basically does that: > takes all config versions that ever existed, iterates them in random order, > and the config that happened to be last gets into final configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18098) stack_advisor should recommend AMS cache size and commit frequency
[ https://issues.apache.org/jira/browse/AMBARI-18098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417775#comment-15417775 ] Hudson commented on AMBARI-18098: - FAILURE: Integrated in Ambari-trunk-Commit #5509 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5509/]) AMBARI-18098 stack_advisor should recommend AMS cache size and commit (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6ff0d5767d5ab67c2f1f906283fe520c32cdf401]) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py > stack_advisor should recommend AMS cache size and commit frequency > -- > > Key: AMBARI-18098 > URL: https://issues.apache.org/jira/browse/AMBARI-18098 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, stacks >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-18098.patch, cache_size_by_sinks_count.png > > > stack_advisor should recommend AMS cache size and commit frequency depending > on cluster size -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417776#comment-15417776 ] Hudson commented on AMBARI-18122: - FAILURE: Integrated in Ambari-trunk-Commit #5509 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5509/]) AMBARI-18122. "hive.metastore.uris" and "templeton.hive.properties" (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cf7ec1298c766a2e0a8dc66c28ea0d8179dae465]) * ambari-web/test/controllers/main/host/details_test.js * ambari-web/app/utils/configs/add_component_config_initializer.js * ambari-web/app/messages.js > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50 > PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18123) Ambari server start fails after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
[
https://issues.apache.org/jira/browse/AMBARI-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1541#comment-1541
]
Hudson commented on AMBARI-18123:
-
FAILURE: Integrated in Ambari-trunk-Commit #5509 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5509/])
AMBARI-18123 Ambari server start fails after upgrade with (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3cc479e300a95870980cbd5ade7896a2dabd9343])
* contrib/views/hive/pom.xml
* contrib/views/hive-next/pom.xml
* ambari-server/pom.xml
> Ambari server start fails after upgrade with java.lang.NoSuchFieldError:
> IS_SECURITY_ENABLED
>
>
> Key: AMBARI-18123
> URL: https://issues.apache.org/jira/browse/AMBARI-18123
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-views
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18123.patch
>
>
> ambari-server --hash
> dcb6d19d2e34b76caae73bcfbd830388155c16dc
> Observed this issue after upgrade of Ambari server from 2.2.2.0 to 2.4.0.0
> where after running "ambari-server start" command, the logs throw below
> errors:
> {code}
> 05 Aug 2016 18:00:03,007 ERROR [main] AmbariServer:927 - Failed to run the
> Ambari Server
> java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
> at
> org.apache.jasper.compiler.JspRuntimeContext.(JspRuntimeContext.java:197)
> at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:532)
> at
> org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:344)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:793)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> at org.eclipse.jetty.server.Server.doStart(Server.java:282)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:616)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:925)
> {code}
> Ambari classpath contains 2 jars with JspRuntimeContext.
> The failure is caused by in Hive view
> [Loaded org.apache.jasper.compiler.JspRuntimeContext from
> file:/var/lib/ambari-server/resources/views/work/HIVE%7B1.5.0%7D/WEB-INF/lib/jasper-compiler-5.5.23.jar]
> JspRuntimeContext in this jar doesn't have field IS_SECURITY_ENABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[
https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417716#comment-15417716
]
Hadoop QA commented on AMBARI-18112:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823321/AMBARI-18112_v0.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/8388//console
This message is automatically generated.
> Fix spark.executor.extraLibraryPath to include native gpl library
> -
>
> Key: AMBARI-18112
> URL: https://issues.apache.org/jira/browse/AMBARI-18112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: AMBARI-18112_v0.patch
>
>
> When spark applications run in yarn cluster mode, there is an error from
> executors:
> -
> java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889)
> at java.lang.Runtime.loadLibrary0(Runtime.java:849)
> at java.lang.System.loadLibrary(System.java:1088)
> at
> com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32)
> at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71)
> at java.lang.Class.forName0(Native Method)
> ...
> org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without
> native-hadoop.
> In the patch, it will set “spark.executor.extraLibraryPath
> /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64”
> in spark-defaults.conf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18111) Interactive Query configs are not reset after refresh/back on Install Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18111: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on ReviewBoard. Patch committed to trunk and branch-2.4 > Interactive Query configs are not reset after refresh/back on Install Wizard > > > Key: AMBARI-18111 > URL: https://issues.apache.org/jira/browse/AMBARI-18111 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18111.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[ https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated AMBARI-18112: -- Status: Patch Available (was: Open) > Fix spark.executor.extraLibraryPath to include native gpl library > - > > Key: AMBARI-18112 > URL: https://issues.apache.org/jira/browse/AMBARI-18112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: AMBARI-18112_v0.patch > > > When spark applications run in yarn cluster mode, there is an error from > executors: > - > java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889) > at java.lang.Runtime.loadLibrary0(Runtime.java:849) > at java.lang.System.loadLibrary(System.java:1088) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71) > at java.lang.Class.forName0(Native Method) > ... > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without > native-hadoop. > In the patch, it will set “spark.executor.extraLibraryPath > /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64” > in spark-defaults.conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[ https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated AMBARI-18112: -- Attachment: AMBARI-18112_v0.patch > Fix spark.executor.extraLibraryPath to include native gpl library > - > > Key: AMBARI-18112 > URL: https://issues.apache.org/jira/browse/AMBARI-18112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: AMBARI-18112_v0.patch > > > When spark applications run in yarn cluster mode, there is an error from > executors: > - > java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889) > at java.lang.Runtime.loadLibrary0(Runtime.java:849) > at java.lang.System.loadLibrary(System.java:1088) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71) > at java.lang.Class.forName0(Native Method) > ... > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without > native-hadoop. > In the patch, it will set “spark.executor.extraLibraryPath > /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64” > in spark-defaults.conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18119) Fix typographical error in hive-mysql dependency
[
https://issues.apache.org/jira/browse/AMBARI-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417644#comment-15417644
]
Hudson commented on AMBARI-18119:
-
FAILURE: Integrated in Ambari-trunk-Commit #5508 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5508/])
AMBARI-18119. Fix typographical error in hive-mysql dependency (dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9829b2defd19758165548fb76b3a8e21a5d36577])
* ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/metainfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/metainfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/services/HIVE/metainfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/services/SQOOP/metainfo.xml
*
ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py
* ambari-server/src/main/resources/stacks/HDP/2.1/services/HIVE/metainfo.xml
* ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/metainfo.xml
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/services/OOZIE/metainfo.xml
* ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/metainfo.xml
> Fix typographical error in hive-mysql dependency
>
>
> Key: AMBARI-18119
> URL: https://issues.apache.org/jira/browse/AMBARI-18119
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18119.patch
>
>
> {code}
>
> mysql-connector-java
> true
> should_install_mysl_connector
>
> {code}
> It should be *should_install_mysql_connector*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18109) After Enabling NNHA, On restarting HDFS, namenodes are stopped
[ https://issues.apache.org/jira/browse/AMBARI-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417645#comment-15417645 ] Hudson commented on AMBARI-18109: - FAILURE: Integrated in Ambari-trunk-Commit #5508 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5508/]) AMBARI-18109. After Enabling NNHA, On restarting HDFS, namenodes are (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cb96d5389406d9bb435e465cc670d07e16aa9526]) * ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js * ambari-web/app/messages.js > After Enabling NNHA, On restarting HDFS, namenodes are stopped > -- > > Key: AMBARI-18109 > URL: https://issues.apache.org/jira/browse/AMBARI-18109 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 > Environment: ambari-server --hash: > 8f9aa197e2195da95497c8acbc2a39c47431cc6a > Ambari DB: :Oracle > OS: Debian 7 >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18109.patch > > > STR: > -> Enable NNHA > -> After NNHA is enabled, there will be a restart icon for HDFS services (is > it expected) > -> On restarting services requiring restart (from button on Services page), > restart is successful but both the Namenodes are stopped > We are stopping all DataNodes before starting all services. Instead of > stopping all DataNodes, lets stop HDFS service and then start all services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18112) Fix spark.executor.extraLibraryPath to include native gpl library
[ https://issues.apache.org/jira/browse/AMBARI-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated AMBARI-18112: -- Summary: Fix spark.executor.extraLibraryPath to include native gpl library (was: Fix spark.driver.extraLibraryPath to include native gpl library) > Fix spark.executor.extraLibraryPath to include native gpl library > - > > Key: AMBARI-18112 > URL: https://issues.apache.org/jira/browse/AMBARI-18112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Weiqing Yang >Assignee: Weiqing Yang > > When spark applications run in yarn cluster mode, there is an error from > executors: > - > java.lang.UnsatisfiedLinkError: no gplcompression in java.library.path > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1889) > at java.lang.Runtime.loadLibrary0(Runtime.java:849) > at java.lang.System.loadLibrary(System.java:1088) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:71) > at java.lang.Class.forName0(Native Method) > ... > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 16/08/08 12:59:03 ERROR LzoCodec: Cannot load native-lzo without > native-hadoop. > In the patch, it will set “spark.executor.extraLibraryPath > /usr/hdp/current/hadoop-client/lib/native:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64” > in spark-defaults.conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417616#comment-15417616 ] Sumit Mohanty commented on AMBARI-18099: +1 to AMBARI-18099.2.patch > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18099.1.patch, AMBARI-18099.2.patch, > AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
Aravindan Vijayan created AMBARI-18125: -- Summary: AMS : Allow for certain metrics to skip aggregation determined by client Key: AMBARI-18125 URL: https://issues.apache.org/jira/browse/AMBARI-18125 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.4.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.5.0 _Example_: Per disk metrics / host static info (no aggregation across hosts) The client should be able to submit a request which dimension should be skipped. The metadata can store this info and allow the SELECT query projection to skip a chunk of these metrics based on what aggregation is working. For now only across host skipping makes sense and the client part can be put in later. *Note*: Sub-task, de-normalize disk metrics so that user can find out disk per host. Grafana implication: The non-aggregated metrics can obviously be visualized only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417598#comment-15417598 ] Jayush Luniya commented on AMBARI-17285: Yes that is correct. The default static version definition should work. The dynamic version definition doesn't support add-on repos yet. > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18098) stack_advisor should recommend AMS cache size and commit frequency
[ https://issues.apache.org/jira/browse/AMBARI-18098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-18098: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > stack_advisor should recommend AMS cache size and commit frequency > -- > > Key: AMBARI-18098 > URL: https://issues.apache.org/jira/browse/AMBARI-18098 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, stacks >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-18098.patch, cache_size_by_sinks_count.png > > > stack_advisor should recommend AMS cache size and commit frequency depending > on cluster size -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18123) Ambari server start fails after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
[
https://issues.apache.org/jira/browse/AMBARI-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-18123:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> Ambari server start fails after upgrade with java.lang.NoSuchFieldError:
> IS_SECURITY_ENABLED
>
>
> Key: AMBARI-18123
> URL: https://issues.apache.org/jira/browse/AMBARI-18123
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-views
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18123.patch
>
>
> ambari-server --hash
> dcb6d19d2e34b76caae73bcfbd830388155c16dc
> Observed this issue after upgrade of Ambari server from 2.2.2.0 to 2.4.0.0
> where after running "ambari-server start" command, the logs throw below
> errors:
> {code}
> 05 Aug 2016 18:00:03,007 ERROR [main] AmbariServer:927 - Failed to run the
> Ambari Server
> java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
> at
> org.apache.jasper.compiler.JspRuntimeContext.(JspRuntimeContext.java:197)
> at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:532)
> at
> org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:344)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:793)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> at org.eclipse.jetty.server.Server.doStart(Server.java:282)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:616)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:925)
> {code}
> Ambari classpath contains 2 jars with JspRuntimeContext.
> The failure is caused by in Hive view
> [Loaded org.apache.jasper.compiler.JspRuntimeContext from
> file:/var/lib/ambari-server/resources/views/work/HIVE%7B1.5.0%7D/WEB-INF/lib/jasper-compiler-5.5.23.jar]
> JspRuntimeContext in this jar doesn't have field IS_SECURITY_ENABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[
https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417534#comment-15417534
]
Hadoop QA commented on AMBARI-18120:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823299/AMBARI-18120_trunk_01.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/8387//console
This message is automatically generated.
> Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
> --
>
> Key: AMBARI-18120
> URL: https://issues.apache.org/jira/browse/AMBARI-18120
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18120_branch-2.4_01.patch,
> AMBARI-18120_trunk_01.patch
>
>
> After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the
> krb5.conf template remained unchanged. As per AMBARI-13240, the template
> should get updated automatically after upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[
https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417532#comment-15417532
]
Hadoop QA commented on AMBARI-18122:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823309/AMBARI-18122.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/8386//console
This message is automatically generated.
> "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly
> updated when WebHCat server is added.
>
>
> Key: AMBARI-18122
> URL: https://issues.apache.org/jira/browse/AMBARI-18122
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50
> PM.png
>
>
> Starting with Hive service added with components : Hive Metastore, Hive
> Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server
> on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at
> 3.53.50 PM.png]
> we are adding webCat Server component and not hive metastore, the above
> configs should not get updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18123) Ambari server start fails after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
[
https://issues.apache.org/jira/browse/AMBARI-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-18123:
Status: Patch Available (was: Open)
> Ambari server start fails after upgrade with java.lang.NoSuchFieldError:
> IS_SECURITY_ENABLED
>
>
> Key: AMBARI-18123
> URL: https://issues.apache.org/jira/browse/AMBARI-18123
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-views
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18123.patch
>
>
> ambari-server --hash
> dcb6d19d2e34b76caae73bcfbd830388155c16dc
> Observed this issue after upgrade of Ambari server from 2.2.2.0 to 2.4.0.0
> where after running "ambari-server start" command, the logs throw below
> errors:
> {code}
> 05 Aug 2016 18:00:03,007 ERROR [main] AmbariServer:927 - Failed to run the
> Ambari Server
> java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
> at
> org.apache.jasper.compiler.JspRuntimeContext.(JspRuntimeContext.java:197)
> at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:532)
> at
> org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:344)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:793)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> at org.eclipse.jetty.server.Server.doStart(Server.java:282)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:616)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:925)
> {code}
> Ambari classpath contains 2 jars with JspRuntimeContext.
> The failure is caused by in Hive view
> [Loaded org.apache.jasper.compiler.JspRuntimeContext from
> file:/var/lib/ambari-server/resources/views/work/HIVE%7B1.5.0%7D/WEB-INF/lib/jasper-compiler-5.5.23.jar]
> JspRuntimeContext in this jar doesn't have field IS_SECURITY_ENABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18123) Ambari server start fails after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
[
https://issues.apache.org/jira/browse/AMBARI-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-18123:
Attachment: AMBARI-18123.patch
> Ambari server start fails after upgrade with java.lang.NoSuchFieldError:
> IS_SECURITY_ENABLED
>
>
> Key: AMBARI-18123
> URL: https://issues.apache.org/jira/browse/AMBARI-18123
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-views
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18123.patch
>
>
> ambari-server --hash
> dcb6d19d2e34b76caae73bcfbd830388155c16dc
> Observed this issue after upgrade of Ambari server from 2.2.2.0 to 2.4.0.0
> where after running "ambari-server start" command, the logs throw below
> errors:
> {code}
> 05 Aug 2016 18:00:03,007 ERROR [main] AmbariServer:927 - Failed to run the
> Ambari Server
> java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
> at
> org.apache.jasper.compiler.JspRuntimeContext.(JspRuntimeContext.java:197)
> at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:532)
> at
> org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:344)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:793)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> at org.eclipse.jetty.server.Server.doStart(Server.java:282)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
> org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:616)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:925)
> {code}
> Ambari classpath contains 2 jars with JspRuntimeContext.
> The failure is caused by in Hive view
> [Loaded org.apache.jasper.compiler.JspRuntimeContext from
> file:/var/lib/ambari-server/resources/views/work/HIVE%7B1.5.0%7D/WEB-INF/lib/jasper-compiler-5.5.23.jar]
> JspRuntimeContext in this jar doesn't have field IS_SECURITY_ENABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
[
https://issues.apache.org/jira/browse/AMBARI-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417531#comment-15417531
]
Hadoop QA commented on AMBARI-18124:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823311/AMBARI-18124.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/8385//console
This message is automatically generated.
> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
> line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
[
https://issues.apache.org/jira/browse/AMBARI-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18124:
Status: Patch Available (was: Open)
> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
> line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
[
https://issues.apache.org/jira/browse/AMBARI-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18124:
Affects Version/s: 2.4.0
> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
> line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
[
https://issues.apache.org/jira/browse/AMBARI-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18124:
Fix Version/s: 2.4.0
> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
> line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
[
https://issues.apache.org/jira/browse/AMBARI-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18124:
Attachment: AMBARI-18124.patch
> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
> line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
[
https://issues.apache.org/jira/browse/AMBARI-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18124:
Component/s: ambari-server
> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
> line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
Dmitry Lysnichenko created AMBARI-18124:
---
Summary: HDFS Finalize Upgrade alert shows up in Unknown state
after EU to 2.3.6
Key: AMBARI-18124
URL: https://issues.apache.org/jira/browse/AMBARI-18124
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Attachments: AMBARI-18124.patch
*Steps*
# Deploy HDP-2.2.6 cluster with Ambari 2.0.2
# Upgrade Ambari to 2.4.0.0
# Perform Express Upgrade to 2.3.6.0 and let it complete
# Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert
definition
*Result*
The alert shows in UNKWN state
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
line 132, in execute
upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
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
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18118) AlertDefinitionCommand intermittently provides stale configurations
[ https://issues.apache.org/jira/browse/AMBARI-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18118: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To https://git-wip-us.apache.org/repos/asf/ambari.git d1c5e04..056d83c branch-2.4 -> branch-2.4 cf7ec12..51bad45 trunk -> trunk > AlertDefinitionCommand intermittently provides stale configurations > --- > > Key: AMBARI-18118 > URL: https://issues.apache.org/jira/browse/AMBARI-18118 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-18118.patch > > > Existing code basically does that: > takes all config versions that ever existed, iterates them in random order, > and the config that happened to be last gets into final configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18123) Ambari server start fails after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
Dmytro Sen created AMBARI-18123:
---
Summary: Ambari server start fails after upgrade with
java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
Key: AMBARI-18123
URL: https://issues.apache.org/jira/browse/AMBARI-18123
Project: Ambari
Issue Type: Bug
Components: ambari-server, ambari-views
Affects Versions: 2.4.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Blocker
Fix For: 2.4.0
ambari-server --hash
dcb6d19d2e34b76caae73bcfbd830388155c16dc
Observed this issue after upgrade of Ambari server from 2.2.2.0 to 2.4.0.0
where after running "ambari-server start" command, the logs throw below errors:
{code}
05 Aug 2016 18:00:03,007 ERROR [main] AmbariServer:927 - Failed to run the
Ambari Server
java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
at
org.apache.jasper.compiler.JspRuntimeContext.(JspRuntimeContext.java:197)
at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
at
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:532)
at
org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:344)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:793)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:282)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:616)
at
org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:925)
{code}
Ambari classpath contains 2 jars with JspRuntimeContext.
The failure is caused by in Hive view
[Loaded org.apache.jasper.compiler.JspRuntimeContext from
file:/var/lib/ambari-server/resources/views/work/HIVE%7B1.5.0%7D/WEB-INF/lib/jasper-compiler-5.5.23.jar]
JspRuntimeContext in this jar doesn't have field IS_SECURITY_ENABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417508#comment-15417508 ] Oleg Nechiporenko commented on AMBARI-18122: Committed to trunk and 2.4 > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50 > PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18072) set JAVA_HOME in livy-env.sh
[ https://issues.apache.org/jira/browse/AMBARI-18072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18072: --- Fix Version/s: 2.4.0 > set JAVA_HOME in livy-env.sh > > > Key: AMBARI-18072 > URL: https://issues.apache.org/jira/browse/AMBARI-18072 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18072-1.patch > > > Ambari should set JAVA_HOME in livy-env.sh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417501#comment-15417501 ] Jaimin D Jetly commented on AMBARI-18122: - +1 for the patch > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50 > PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18122: --- Status: Patch Available (was: Open) Patch added > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50 > PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417497#comment-15417497 ] Oleg Nechiporenko commented on AMBARI-18122: 29240 tests complete (27 seconds) 154 tests pending > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50 > PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18122: --- Attachment: AMBARI-18122.patch > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18122.patch, Screen Shot 2016-08-09 at 3.53.50 > PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18122: --- Description: Starting with Hive service added with components : Hive Metastore, Hive Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at 3.53.50 PM.png] we are adding webCat Server component and not hive metastore, the above configs should not get updated. was: Starting with Hive service added with components : Hive Metastore, Hive Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server on another host, a popup message shows up as: [^] we are adding webCat Server component and not hive metastore, the above configs should not get updated. > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-08-09 at 3.53.50 PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^Screen Shot 2016-08-09 at > 3.53.50 PM.png] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18122: --- Attachment: Screen Shot 2016-08-09 at 3.53.50 PM.png > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-08-09 at 3.53.50 PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
Oleg Nechiporenko created AMBARI-18122: -- Summary: "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added. Key: AMBARI-18122 URL: https://issues.apache.org/jira/browse/AMBARI-18122 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Priority: Blocker Fix For: 2.4.0 Attachments: Screen Shot 2016-08-09 at 3.53.50 PM.png Starting with Hive service added with components : Hive Metastore, Hive Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server on another host, a popup message shows up as: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18122) "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly updated when WebHCat server is added.
[ https://issues.apache.org/jira/browse/AMBARI-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18122: --- Description: Starting with Hive service added with components : Hive Metastore, Hive Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server on another host, a popup message shows up as: [^] we are adding webCat Server component and not hive metastore, the above configs should not get updated. was:Starting with Hive service added with components : Hive Metastore, Hive Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server on another host, a popup message shows up as: > "hive.metastore.uris" and "templeton.hive.properties" configs gets wrongly > updated when WebHCat server is added. > > > Key: AMBARI-18122 > URL: https://issues.apache.org/jira/browse/AMBARI-18122 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-08-09 at 3.53.50 PM.png > > > Starting with Hive service added with components : Hive Metastore, Hive > Server2, MySQL Server, and 1 WebHcat Server, if I add another WebHCat server > on another host, a popup message shows up as: [^] > we are adding webCat Server component and not hive metastore, the above > configs should not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18072) set JAVA_HOME in livy-env.sh
[ https://issues.apache.org/jira/browse/AMBARI-18072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417484#comment-15417484 ] Hudson commented on AMBARI-18072: - FAILURE: Integrated in Ambari-trunk-Commit #5507 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5507/]) AMBARI-18072. set JAVA_HOME in livy-env.sh (Jeff Zhang via smohanty) (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b45690cd6a2724b6fc44cdef64783b210ea20994]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/SPARK/configuration/livy-env.xml * ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/params.py > set JAVA_HOME in livy-env.sh > > > Key: AMBARI-18072 > URL: https://issues.apache.org/jira/browse/AMBARI-18072 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang >Priority: Critical > Attachments: AMBARI-18072-1.patch > > > Ambari should set JAVA_HOME in livy-env.sh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18116) Fix UT issues
[ https://issues.apache.org/jira/browse/AMBARI-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417485#comment-15417485 ] Hudson commented on AMBARI-18116: - FAILURE: Integrated in Ambari-trunk-Commit #5507 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5507/]) AMBARI-18116. Fix UT issues (onechiporenko) (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4001428d86fc9cd305d2bf14f29690f0b8b074c0]) * ambari-web/test/mixins/common/configs/enhanced_configs_test.js * ambari-web/test/mixins/common/configs/config_with_override_recommendation_parser_test.js * ambari-web/test/mixins/common/configs/configs_loader_test.js > Fix UT issues > - > > Key: AMBARI-18116 > URL: https://issues.apache.org/jira/browse/AMBARI-18116 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-18116.patch > > > * ambari-web/test/mixins/common/configs/enhanced_configs_test.js > * > ambari-web/test/mixins/common/configs/config_with_override_recommendation_parser_test.js > * ambari-web/test/mixins/common/configs/configs_loader_test.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18117) Add unit tests for zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417483#comment-15417483 ] Hudson commented on AMBARI-18117: - FAILURE: Integrated in Ambari-trunk-Commit #5507 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5507/]) AMBARI-18117. Add unit tests for zeppelin (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=281b2ca5cfc359f5a431280da53efacb57599486]) * ambari-server/src/test/python/stacks/2.5/configs/default.json * ambari-server/src/test/python/stacks/2.5/configs/secured.json * ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py > Add unit tests for zeppelin > --- > > Key: AMBARI-18117 > URL: https://issues.apache.org/jira/browse/AMBARI-18117 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-18117.patch > > > Currently zeppelin is one of few services which is not covered by unit tests. > Which can lead to excessive number of code errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18115) Zeppelin: quicklinks url protocol should switch to https when ssl is enabled in zeppelin conf
[ https://issues.apache.org/jira/browse/AMBARI-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417486#comment-15417486 ] Hudson commented on AMBARI-18115: - FAILURE: Integrated in Ambari-trunk-Commit #5507 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5507/]) AMBARI-18115. Zeppelin: quicklinks url protocol should switch to https (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=033b1afbe09b16c448ebe244cc3369e9fddfc650]) * ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/quicklinks/quicklinks.json > Zeppelin: quicklinks url protocol should switch to https when ssl is enabled > in zeppelin conf > - > > Key: AMBARI-18115 > URL: https://issues.apache.org/jira/browse/AMBARI-18115 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Renjith Kamath >Assignee: Renjith Kamath >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18115_trunk+branch-2.4_v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18121) Cover utils/config with unit tests
Andrii Babiichuk created AMBARI-18121: - Summary: Cover utils/config with unit tests Key: AMBARI-18121 URL: https://issues.apache.org/jira/browse/AMBARI-18121 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18120: -- Description: After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the krb5.conf template remained unchanged. As per AMBARI-13240, the template should get updated automatically after upgrade. (was: After the successfully upgrading from Ambari 2.2.2 to Ambari 2.3.0, the krb5.conf template remained unchanged. As per AMBARI-13240, the template should get updated automatically after upgrade.) > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18120: -- Attachment: AMBARI-18120_trunk_01.patch AMBARI-18120_branch-2.4_01.patch > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.3.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
[ https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18120: -- Status: Patch Available (was: In Progress) > Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template > -- > > Key: AMBARI-18120 > URL: https://issues.apache.org/jira/browse/AMBARI-18120 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18120_branch-2.4_01.patch, > AMBARI-18120_trunk_01.patch > > > After the successfully upgrading from Ambari 2.2.2 to Ambari 2.3.0, the > krb5.conf template remained unchanged. As per AMBARI-13240, the template > should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18118) AlertDefinitionCommand intermittently provides stale configurations
[
https://issues.apache.org/jira/browse/AMBARI-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417443#comment-15417443
]
Hadoop QA commented on AMBARI-18118:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823288/AMBARI-18118.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/8384//console
This message is automatically generated.
> AlertDefinitionCommand intermittently provides stale configurations
> ---
>
> Key: AMBARI-18118
> URL: https://issues.apache.org/jira/browse/AMBARI-18118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18118.patch
>
>
> Existing code basically does that:
> takes all config versions that ever existed, iterates them in random order,
> and the config that happened to be last gets into final configuration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18109) After Enabling NNHA, On restarting HDFS, namenodes are stopped
[ https://issues.apache.org/jira/browse/AMBARI-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18109: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.4 > After Enabling NNHA, On restarting HDFS, namenodes are stopped > -- > > Key: AMBARI-18109 > URL: https://issues.apache.org/jira/browse/AMBARI-18109 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 > Environment: ambari-server --hash: > 8f9aa197e2195da95497c8acbc2a39c47431cc6a > Ambari DB: :Oracle > OS: Debian 7 >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18109.patch > > > STR: > -> Enable NNHA > -> After NNHA is enabled, there will be a restart icon for HDFS services (is > it expected) > -> On restarting services requiring restart (from button on Services page), > restart is successful but both the Namenodes are stopped > We are stopping all DataNodes before starting all services. Instead of > stopping all DataNodes, lets stop HDFS service and then start all services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18120) Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
Robert Levas created AMBARI-18120: - Summary: Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template Key: AMBARI-18120 URL: https://issues.apache.org/jira/browse/AMBARI-18120 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Robert Levas Assignee: Robert Levas Priority: Blocker Fix For: 2.4.0 After the successfully upgrading from Ambari 2.2.2 to Ambari 2.3.0, the krb5.conf template remained unchanged. As per AMBARI-13240, the template should get updated automatically after upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18109) After Enabling NNHA, On restarting HDFS, namenodes are stopped
[ https://issues.apache.org/jira/browse/AMBARI-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417421#comment-15417421 ] Antonenko Alexander commented on AMBARI-18109: -- rat check passed 29246 tests complete (27 seconds) 154 tests pending > After Enabling NNHA, On restarting HDFS, namenodes are stopped > -- > > Key: AMBARI-18109 > URL: https://issues.apache.org/jira/browse/AMBARI-18109 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 > Environment: ambari-server --hash: > 8f9aa197e2195da95497c8acbc2a39c47431cc6a > Ambari DB: :Oracle > OS: Debian 7 >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18109.patch > > > STR: > -> Enable NNHA > -> After NNHA is enabled, there will be a restart icon for HDFS services (is > it expected) > -> On restarting services requiring restart (from button on Services page), > restart is successful but both the Namenodes are stopped > We are stopping all DataNodes before starting all services. Instead of > stopping all DataNodes, lets stop HDFS service and then start all services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18109) After Enabling NNHA, On restarting HDFS, namenodes are stopped
[ https://issues.apache.org/jira/browse/AMBARI-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417392#comment-15417392 ] Aleksandr Kovalenko commented on AMBARI-18109: -- +1 for the patch > After Enabling NNHA, On restarting HDFS, namenodes are stopped > -- > > Key: AMBARI-18109 > URL: https://issues.apache.org/jira/browse/AMBARI-18109 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 > Environment: ambari-server --hash: > 8f9aa197e2195da95497c8acbc2a39c47431cc6a > Ambari DB: :Oracle > OS: Debian 7 >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18109.patch > > > STR: > -> Enable NNHA > -> After NNHA is enabled, there will be a restart icon for HDFS services (is > it expected) > -> On restarting services requiring restart (from button on Services page), > restart is successful but both the Namenodes are stopped > We are stopping all DataNodes before starting all services. Instead of > stopping all DataNodes, lets stop HDFS service and then start all services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
