[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: (was: AMBARI-22656_branch-2.5.patch) > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: (was: AMBARI-22656.patch) > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: AMBARI-22656.patch > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22721) Centralize the Management of Tarball Uploading
Jonathan Hurley created AMBARI-22721:
Summary: Centralize the Management of Tarball Uploading
Key: AMBARI-22721
URL: https://issues.apache.org/jira/browse/AMBARI-22721
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.2
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.6.2
Ambari is required to upload tarballs into HDFS for many of the services to
correctly function after they are installed. This tarball management is not
centralized in any way, and is instead, spread out between several different
Python files for various services:
Hive uploads Tez, MapReduce2, Sqoop, etc tarballs
Yarn does Tez, Slider, MapReduce2
This causes a problem when patching a specific service, such as Sqoop. Sqoop
requires that sqoop.tar.gz and mapreduce.tar.gz are available in the same
versioned folder in HDFS. However, no Sqoop components perform this upload -
Hive does. So, if Hive is not upgrading, these tarballs are never uploaded.
The proposal here is to remove the coupling of tarball uploads and to manage
these relationships on the stack:
{code}
{
"tarball": {
"MAPREDUCE2": {
"JOB_HISTORY_SERVER": [
{
"tarball": "mapreduce.tar.gz",
"source_dir": "{0}/{1}/hadoop/mapreduce.tar.gz",
"target_dir": "/{0}/apps/{1}/mapreduce/mapreduce.tar.gz"
}
]
},
"HIVE": {
"HIVE_SERVER2": [
{
"tarball": "mapreduce.tar.gz",
"source_dir": "{0}/{1}/hadoop/mapreduce.tar.gz",
"target_dir": "/{0}/apps/{1}/mapreduce/mapreduce.tar.gz"
},
{
"tarball": "sqoop.tar.gz",
"source_dir": "{0}/{1}/sqoop/sqoop.tar.gz",
"target_dir": "/{0}/apps/{1}/sqoop/sqoop.tar.gz"
}
]
},
"SQOOP": {
"SQOOP": [
{
"tarball": "mapreduce.tar.gz",
"source_dir": "{0}/{1}/hadoop/mapreduce.tar.gz",
"target_dir": "/{0}/apps/{1}/mapreduce/mapreduce.tar.gz"
},
{
"tarball": "sqoop.tar.gz",
"source_dir": "{0}/{1}/sqoop/sqoop.tar.gz",
"target_dir": "/{0}/apps/{1}/sqoop/sqoop.tar.gz"
}
]
}
}
}
{code}
- after-INSTALL hooks will check for {{CLIENT}} as the component category
- after-START hooks will check for NOT {{CLIENT}}
Additionally, using the file length for a checksum may no longer be sufficient.
We should also add a checksum file to HDFS for each tarball so we can easily
tell if work needs to be done (during an install, restart, upgrade, etc) to
upload a new tarball (one that is also potentially modified with native
libraries):
{code:title=ambari-tarball-checksum.json (0644)}
{
"mapreduce.tar.gz": {
"native_libraries": true,
"file_count": 509
},
"hadoop-streaming.tar.gz": {
"native_libraries": false,
"file_count": 10
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22721) Centralize the Management of Tarball Uploading
[
https://issues.apache.org/jira/browse/AMBARI-22721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22721:
-
Issue Type: Task (was: Bug)
> Centralize the Management of Tarball Uploading
> --
>
> Key: AMBARI-22721
> URL: https://issues.apache.org/jira/browse/AMBARI-22721
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
>
> Ambari is required to upload tarballs into HDFS for many of the services to
> correctly function after they are installed. This tarball management is not
> centralized in any way, and is instead, spread out between several different
> Python files for various services:
> Hive uploads Tez, MapReduce2, Sqoop, etc tarballs
> Yarn does Tez, Slider, MapReduce2
> This causes a problem when patching a specific service, such as Sqoop. Sqoop
> requires that sqoop.tar.gz and mapreduce.tar.gz are available in the same
> versioned folder in HDFS. However, no Sqoop components perform this upload -
> Hive does. So, if Hive is not upgrading, these tarballs are never uploaded.
> The proposal here is to remove the coupling of tarball uploads and to manage
> these relationships on the stack:
> {code}
> {
> "tarball": {
> "MAPREDUCE2": {
> "JOB_HISTORY_SERVER": [
> {
> "tarball": "mapreduce.tar.gz",
> "source_dir": "{0}/{1}/hadoop/mapreduce.tar.gz",
> "target_dir": "/{0}/apps/{1}/mapreduce/mapreduce.tar.gz"
> }
> ]
> },
> "HIVE": {
> "HIVE_SERVER2": [
> {
> "tarball": "mapreduce.tar.gz",
> "source_dir": "{0}/{1}/hadoop/mapreduce.tar.gz",
> "target_dir": "/{0}/apps/{1}/mapreduce/mapreduce.tar.gz"
> },
> {
> "tarball": "sqoop.tar.gz",
> "source_dir": "{0}/{1}/sqoop/sqoop.tar.gz",
> "target_dir": "/{0}/apps/{1}/sqoop/sqoop.tar.gz"
> }
> ]
> },
> "SQOOP": {
> "SQOOP": [
> {
> "tarball": "mapreduce.tar.gz",
> "source_dir": "{0}/{1}/hadoop/mapreduce.tar.gz",
> "target_dir": "/{0}/apps/{1}/mapreduce/mapreduce.tar.gz"
> },
> {
> "tarball": "sqoop.tar.gz",
> "source_dir": "{0}/{1}/sqoop/sqoop.tar.gz",
> "target_dir": "/{0}/apps/{1}/sqoop/sqoop.tar.gz"
> }
> ]
> }
> }
> }
> {code}
> - after-INSTALL hooks will check for {{CLIENT}} as the component category
> - after-START hooks will check for NOT {{CLIENT}}
> Additionally, using the file length for a checksum may no longer be
> sufficient. We should also add a checksum file to HDFS for each tarball so we
> can easily tell if work needs to be done (during an install, restart,
> upgrade, etc) to upload a new tarball (one that is also potentially modified
> with native libraries):
> {code:title=ambari-tarball-checksum.json (0644)}
> {
> "mapreduce.tar.gz": {
> "native_libraries": true,
> "file_count": 509
> },
> "hadoop-streaming.tar.gz": {
> "native_libraries": false,
> "file_count": 10
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22720) Create initial Ambari Infra Mpack with AMS.
[ https://issues.apache.org/jira/browse/AMBARI-22720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-22720: -- Assignee: Aravindan Vijayan > Create initial Ambari Infra Mpack with AMS. > --- > > Key: AMBARI-22720 > URL: https://issues.apache.org/jira/browse/AMBARI-22720 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22720) Create initial Ambari Infra Mpack with AMS.
Aravindan Vijayan created AMBARI-22720: -- Summary: Create initial Ambari Infra Mpack with AMS. Key: AMBARI-22720 URL: https://issues.apache.org/jira/browse/AMBARI-22720 Project: Ambari Issue Type: Bug Components: ambari-infra, ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22702) Infra Manager: scheduled deleting of Infra Solr documents
[ https://issues.apache.org/jira/browse/AMBARI-22702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309544#comment-16309544 ] Hudson commented on AMBARI-22702: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8570 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8570/]) AMBARI-22702. Infra Manager: scheduled deleting of Infra Solr documents (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a85ff23bd8737a17544983c44752a9fd602d864a]) * (edit) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentWiper.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentArchivingConfiguration.java * (edit) ambari-infra/ambari-infra-manager/docker/infra-manager-docker-compose.sh * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/S3Uploader.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDocumentIterator.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/AbstractFileAction.java * (edit) ambari-infra/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/deleting/DocumentDeletingConfiguration.java * (edit) ambari-infra/ambari-infra-manager/pom.xml * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/JobPropertyMap.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/LocalDocumentItemWriter.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/Document.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/FileAction.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/deleting/DocumentDeletingPropertyMap.java * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/SolrQueryBuilderTest.java * (edit) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/ExportJobsSteps.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/S3Properties.java * (delete) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportJobListener.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrQueryBuilder.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrParametrizedString.java * (add) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/JobPropertiesTest.java * (edit) ambari-infra/ambari-infra-manager/src/main/resources/infra-manager.properties * (delete) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/DocumentExportPropertiesTest.java * (edit) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/OffsetDateTimeConverter.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/deleting/DocumentDeletingProperties.java * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/LocalDocumentItemWriterTest.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/LocalItemWriterListener.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDocumentSource.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/WriteCompletedEvent.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/deleting/DocumentWiperTasklet.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportPropertyMap.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/PropertyMap.java * (add) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/SolrParametrizedStringTest.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/FileNameSuffixFormatter.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/SolrDAOBase.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDAO.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/CompositeFileAction.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/TarGzCompressor.java * (add)
[jira] [Commented] (AMBARI-22716) zeppelin.livy.url is not getting updated after moving livy to a new host
[
https://issues.apache.org/jira/browse/AMBARI-22716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309540#comment-16309540
]
Hadoop QA commented on AMBARI-22716:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904267/0AMBARI-22716_branch-2.6_v1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12917//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12917//console
This message is automatically generated.
> zeppelin.livy.url is not getting updated after moving livy to a new host
>
>
> Key: AMBARI-22716
> URL: https://issues.apache.org/jira/browse/AMBARI-22716
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version 2.6.1.0-137
> HDP-2.6.4.0-86
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: 0AMBARI-22716_branch-2.6_v1.patch,
> 0AMBARI-22716_trunk_v1.patch
>
>
> zeppelin.livy.url is not getting updated after moving livy to a new host
> Steps to reproduce :
> 1) Create a cluster with both Spark and Spark2 component
> 2) Delete livy component from current host.
> 3) Add the livy component on a new host
> 4) Restart zeppelin server.
> 5) Now check the zeppelin interpreter settings. zeppelin.livy.url is still
> referring to older livy host.
> Its not reflecting the new livy server address.
> Note 1 : If I restart zeppelin server after step1 (ie after deleting the livy
> host) before performing rest of the steps, then changes are getting reflected
> properly. System test was mistakenly doing this step so didn't fail during
> nightly run
> Note 2 : Issue is happening only when both Spark and Spark2 are installed. If
> cluster contains only Spark2, this feature works as expected.
> Issue is coming if I add Spark(version 1) to it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22403) Read the JAVA_HOME depending on the OS family during Service install (action & command) and upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309538#comment-16309538
]
Hadoop QA commented on AMBARI-22403:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904349/AMBARI-22403.001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12916//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12916//console
This message is automatically generated.
> Read the JAVA_HOME depending on the OS family during Service install (action
> & command) and upgrade
> ---
>
> Key: AMBARI-22403
> URL: https://issues.apache.org/jira/browse/AMBARI-22403
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22403.001.patch
>
>
> Use of proper java_home value during service install and configuration base
> on host OS type.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22719) Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
[
https://issues.apache.org/jira/browse/AMBARI-22719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22719:
---
Status: Patch Available (was: In Progress)
> Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
> -
>
> Key: AMBARI-22719
> URL: https://issues.apache.org/jira/browse/AMBARI-22719
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22719.branch-2.6.patch, AMBARI-22719.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Deploy secure cluster (ZooKeeper + Kafka)
> # Set {{security.inter.broker.protocol}} to {{SASL_PLAINTEXT}} (or
> {{SASL_SSL}})
> # Remove {{security.inter.broker.protocol}} from cluster Kerberos descriptor
> or update it to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
>
> ([steps|https://community.hortonworks.com/articles/89713/updating-the-user-sepecified-kerberos-descriptor.html])
> # Regenerate Keytabs
> Result: {{security.inter.broker.protocol}} is reset to {{PLAINTEXTSASL}}
> This is caused by stack advisor forcing {{PLAINTEXTSASL}} for secure cluster,
> although {{SASL_PLAINTEXT}} (or {{SASL_SSL}}) is also valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22719) Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
[
https://issues.apache.org/jira/browse/AMBARI-22719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22719:
---
Attachment: AMBARI-22719.trunk.patch
> Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
> -
>
> Key: AMBARI-22719
> URL: https://issues.apache.org/jira/browse/AMBARI-22719
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22719.branch-2.6.patch, AMBARI-22719.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Deploy secure cluster (ZooKeeper + Kafka)
> # Set {{security.inter.broker.protocol}} to {{SASL_PLAINTEXT}} (or
> {{SASL_SSL}})
> # Remove {{security.inter.broker.protocol}} from cluster Kerberos descriptor
> or update it to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
>
> ([steps|https://community.hortonworks.com/articles/89713/updating-the-user-sepecified-kerberos-descriptor.html])
> # Regenerate Keytabs
> Result: {{security.inter.broker.protocol}} is reset to {{PLAINTEXTSASL}}
> This is caused by stack advisor forcing {{PLAINTEXTSASL}} for secure cluster,
> although {{SASL_PLAINTEXT}} (or {{SASL_SSL}}) is also valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309523#comment-16309523
]
Hadoop QA commented on AMBARI-22718:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904364/AMBARI-22718.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12915//console
This message is automatically generated.
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch, AMBARI-22718.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22719) Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
[
https://issues.apache.org/jira/browse/AMBARI-22719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22719:
---
Attachment: AMBARI-22719.branch-2.6.patch
> Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
> -
>
> Key: AMBARI-22719
> URL: https://issues.apache.org/jira/browse/AMBARI-22719
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22719.branch-2.6.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Deploy secure cluster (ZooKeeper + Kafka)
> # Set {{security.inter.broker.protocol}} to {{SASL_PLAINTEXT}} (or
> {{SASL_SSL}})
> # Remove {{security.inter.broker.protocol}} from cluster Kerberos descriptor
> or update it to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
>
> ([steps|https://community.hortonworks.com/articles/89713/updating-the-user-sepecified-kerberos-descriptor.html])
> # Regenerate Keytabs
> Result: {{security.inter.broker.protocol}} is reset to {{PLAINTEXTSASL}}
> This is caused by stack advisor forcing {{PLAINTEXTSASL}} for secure cluster,
> although {{SASL_PLAINTEXT}} (or {{SASL_SSL}}) is also valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22719) Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
[
https://issues.apache.org/jira/browse/AMBARI-22719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22719:
---
Attachment: (was: AMBARI-22719.branch-2.6.patch)
> Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
> -
>
> Key: AMBARI-22719
> URL: https://issues.apache.org/jira/browse/AMBARI-22719
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22719.branch-2.6.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Deploy secure cluster (ZooKeeper + Kafka)
> # Set {{security.inter.broker.protocol}} to {{SASL_PLAINTEXT}} (or
> {{SASL_SSL}})
> # Remove {{security.inter.broker.protocol}} from cluster Kerberos descriptor
> or update it to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
>
> ([steps|https://community.hortonworks.com/articles/89713/updating-the-user-sepecified-kerberos-descriptor.html])
> # Regenerate Keytabs
> Result: {{security.inter.broker.protocol}} is reset to {{PLAINTEXTSASL}}
> This is caused by stack advisor forcing {{PLAINTEXTSASL}} for secure cluster,
> although {{SASL_PLAINTEXT}} (or {{SASL_SSL}}) is also valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22719) Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
[
https://issues.apache.org/jira/browse/AMBARI-22719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22719:
---
Attachment: AMBARI-22719.branch-2.6.patch
> Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
> -
>
> Key: AMBARI-22719
> URL: https://issues.apache.org/jira/browse/AMBARI-22719
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22719.branch-2.6.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Deploy secure cluster (ZooKeeper + Kafka)
> # Set {{security.inter.broker.protocol}} to {{SASL_PLAINTEXT}} (or
> {{SASL_SSL}})
> # Remove {{security.inter.broker.protocol}} from cluster Kerberos descriptor
> or update it to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
>
> ([steps|https://community.hortonworks.com/articles/89713/updating-the-user-sepecified-kerberos-descriptor.html])
> # Regenerate Keytabs
> Result: {{security.inter.broker.protocol}} is reset to {{PLAINTEXTSASL}}
> This is caused by stack advisor forcing {{PLAINTEXTSASL}} for secure cluster,
> although {{SASL_PLAINTEXT}} (or {{SASL_SSL}}) is also valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22702) Infra Manager: scheduled deleting of Infra Solr documents
[ https://issues.apache.org/jira/browse/AMBARI-22702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-22702. --- Resolution: Fixed > Infra Manager: scheduled deleting of Infra Solr documents > - > > Key: AMBARI-22702 > URL: https://issues.apache.org/jira/browse/AMBARI-22702 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa > Fix For: 3.0.0 > > > delete Document from Infra Solr specified by an interval > also in archiving mode delete Documents which are successfully exported and > uploaded -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22702) Infra Manager: scheduled deleting of Infra Solr documents
[
https://issues.apache.org/jira/browse/AMBARI-22702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309482#comment-16309482
]
Olivér Szabó commented on AMBARI-22702:
---
committed to trunk:
{code:java}
Author: Krisztian Kasa
Date: Wed Jan 3 11:38:43 2018 +0100
AMBARI-22702. Infra Manager: scheduled deleting of Infra Solr documents
(Krisztian Kasa via oleewere)
{code}
> Infra Manager: scheduled deleting of Infra Solr documents
> -
>
> Key: AMBARI-22702
> URL: https://issues.apache.org/jira/browse/AMBARI-22702
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-infra
>Affects Versions: 3.0.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
> Fix For: 3.0.0
>
>
> delete Document from Infra Solr specified by an interval
> also in archiving mode delete Documents which are successfully exported and
> uploaded
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22719) Regenerate Keytabs resets security.inter.broker.protocol to PLAINTEXTSASL
Doroszlai, Attila created AMBARI-22719:
--
Summary: Regenerate Keytabs resets security.inter.broker.protocol
to PLAINTEXTSASL
Key: AMBARI-22719
URL: https://issues.apache.org/jira/browse/AMBARI-22719
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.6.1
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 3.0.0, 2.6.2
STR:
# Install Ambari 2.6.1
# Deploy secure cluster (ZooKeeper + Kafka)
# Set {{security.inter.broker.protocol}} to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
# Remove {{security.inter.broker.protocol}} from cluster Kerberos descriptor or
update it to {{SASL_PLAINTEXT}} (or {{SASL_SSL}})
([steps|https://community.hortonworks.com/articles/89713/updating-the-user-sepecified-kerberos-descriptor.html])
# Regenerate Keytabs
Result: {{security.inter.broker.protocol}} is reset to {{PLAINTEXTSASL}}
This is caused by stack advisor forcing {{PLAINTEXTSASL}} for secure cluster,
although {{SASL_PLAINTEXT}} (or {{SASL_SSL}}) is also valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22718:
---
Fix Version/s: 3.0.0
Status: Patch Available (was: In Progress)
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch, AMBARI-22718.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22718:
---
Attachment: AMBARI-22718.trunk.patch
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch, AMBARI-22718.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22718:
---
Attachment: AMBARI-22718.branch-2.6.patch
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22391) Backend and UI changes for Ambari repo URLs related to OS arch types
[ https://issues.apache.org/jira/browse/AMBARI-22391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh resolved AMBARI-22391. Resolution: Fixed > Backend and UI changes for Ambari repo URLs related to OS arch types > > > Key: AMBARI-22391 > URL: https://issues.apache.org/jira/browse/AMBARI-22391 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > > For Hybrid cluster, we need an user interface to allow user to enter the > Ambari repository url for the added host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22394) Store and retrieve the ambari repo urls for os family during bootstrap
[ https://issues.apache.org/jira/browse/AMBARI-22394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22394: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Store and retrieve the ambari repo urls for os family during bootstrap > -- > > Key: AMBARI-22394 > URL: https://issues.apache.org/jira/browse/AMBARI-22394 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22394.patch > > > ambari configuration will have list of repo urls for each os type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22403) Read the JAVA_HOME depending on the OS family during Service install (action & command) and upgrade
[ https://issues.apache.org/jira/browse/AMBARI-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22403: --- Attachment: AMBARI-22403.001.patch > Read the JAVA_HOME depending on the OS family during Service install (action > & command) and upgrade > --- > > Key: AMBARI-22403 > URL: https://issues.apache.org/jira/browse/AMBARI-22403 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22403.001.patch > > > Use of proper java_home value during service install and configuration base > on host OS type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22403) Read the JAVA_HOME depending on the OS family during Service install (action & command) and upgrade
[ https://issues.apache.org/jira/browse/AMBARI-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22403: --- Status: Patch Available (was: In Progress) > Read the JAVA_HOME depending on the OS family during Service install (action > & command) and upgrade > --- > > Key: AMBARI-22403 > URL: https://issues.apache.org/jira/browse/AMBARI-22403 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22403.001.patch > > > Use of proper java_home value during service install and configuration base > on host OS type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
Doroszlai, Attila created AMBARI-22718:
--
Summary: Cannot set security.inter.broker.protocol: SASL_SSL via
Blueprint with Kerberos
Key: AMBARI-22718
URL: https://issues.apache.org/jira/browse/AMBARI-22718
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.6.1
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.6.2
STR:
# Install Ambari 2.6.1
# Tweak {{stack_features.json}} to lower {{min_version}} for
{{kafka_extended_sasl_support}}
# Create secure cluster via blueprint (ZooKeeper + Kafka) with
{{security.inter.broker.protocol: SASL_SSL}}
Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
