[jira] [Updated] (AMBARI-25174) OneFS Mpack missing configuration settings needed for Spark2
[ https://issues.apache.org/jira/browse/AMBARI-25174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-25174: - Description: The OneFS management pack does not include the below HDFS configurations/parameters. If using the OneFS mpack as a replacement for the HDFS service, these parameters no longer exist. dfs.datanode.kerberos.principal=hdfs/_HOST@ dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab dfs.namenode.kerberos.principal=hdfs/_HOST@ dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab These are required by Spark2 in a Kerberised environment, and starting the Spark2 History Server will otherwise fail with obscure errors such as "Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Failed to specify server's Kerberos principal name" See my answer on [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487] Workaround was to add them back to Custom hdfs-site, but it should be part of the mpack so it gets handled automatically. was: The OneFS management pack does not include the below HDFS configurations/parameters. If using the OneFS mpack as a replacement for the HDFS service, these parameters no longer exist. dfs.datanode.kerberos.principal=hdfs/_HOST@ dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab dfs.namenode.kerberos.principal=hdfs/_HOST@ dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab These are required by Spark2 in a Kerberised environment, and starting the Spark2 History Server will otherwise fail with obscure errors such as "Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Failed to specify server's Kerberos principal name" See my answer on [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487 Workaround was to add them back to Custom hdfs-site, but it should be part of the mpack so it gets handled automatically. > OneFS Mpack missing configuration settings needed for Spark2 > > > Key: AMBARI-25174 > URL: https://issues.apache.org/jira/browse/AMBARI-25174 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 > Environment: HDP 3.1.1 using OneFS instead of HDFS > Isilon 8.2.1.0 (simulator) > isilon-onefs-mpack-1.0.0.0 >Reporter: Bjorn Olsen >Priority: Major > > The OneFS management pack does not include the below HDFS > configurations/parameters. If using the OneFS mpack as a replacement for the > HDFS service, these parameters no longer exist. > dfs.datanode.kerberos.principal=hdfs/_HOST@ > dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab > dfs.namenode.kerberos.principal=hdfs/_HOST@ > dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab > These are required by Spark2 in a Kerberised environment, and starting the > Spark2 History Server will otherwise fail with obscure errors such as "Failed > on local exception: java.io.IOException: Couldn't set up IO streams: > java.lang.IllegalArgumentException: > Failed to specify server's Kerberos principal name" > See my answer on > [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487] > > Workaround was to add them back to Custom hdfs-site, but it should be part of > the mpack so it gets handled automatically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25174) OneFS Mpack missing configuration settings needed for Spark2
[ https://issues.apache.org/jira/browse/AMBARI-25174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-25174: - Description: The OneFS management pack does not include the below HDFS configurations/parameters. If using the OneFS mpack as a replacement for the HDFS service, these parameters no longer exist. dfs.datanode.kerberos.principal=hdfs/_HOST@ dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab dfs.namenode.kerberos.principal=hdfs/_HOST@ dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab These are required by Spark2 in a Kerberised environment, and starting the Spark2 History Server will otherwise fail with obscure errors such as "Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Failed to specify server's Kerberos principal name" See my answer on [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487 ] Workaround was to add them back to Custom hdfs-site, but it should be part of the mpack so it gets handled automatically. was: The OneFS management pack does not include the below HDFS configurations/parameters. If using the OneFS mpack as a replacement for the HDFS service, these parameters no longer exist. dfs.datanode.kerberos.principal=hdfs/_HOST@ dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab dfs.namenode.kerberos.principal=hdfs/_HOST@ dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab These are required by Spark2 in a Kerberised environment, and starting the Spark2 History Server will otherwise fail with obscure errors such as "Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Failed to specify server's Kerberos principal name" See my answer on [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487] > OneFS Mpack missing configuration settings needed for Spark2 > > > Key: AMBARI-25174 > URL: https://issues.apache.org/jira/browse/AMBARI-25174 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 > Environment: HDP 3.1.1 using OneFS instead of HDFS > Isilon 8.2.1.0 (simulator) > isilon-onefs-mpack-1.0.0.0 >Reporter: Bjorn Olsen >Priority: Major > > The OneFS management pack does not include the below HDFS > configurations/parameters. If using the OneFS mpack as a replacement for the > HDFS service, these parameters no longer exist. > dfs.datanode.kerberos.principal=hdfs/_HOST@ > dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab > dfs.namenode.kerberos.principal=hdfs/_HOST@ > dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab > These are required by Spark2 in a Kerberised environment, and starting the > Spark2 History Server will otherwise fail with obscure errors such as "Failed > on local exception: java.io.IOException: Couldn't set up IO streams: > java.lang.IllegalArgumentException: > Failed to specify server's Kerberos principal name" > See my answer on > [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487 > ] > Workaround was to add them back to Custom hdfs-site, but it should be part of > the mpack so it gets handled automatically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25174) OneFS Mpack missing configuration settings needed for Spark2
[ https://issues.apache.org/jira/browse/AMBARI-25174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-25174: - Description: The OneFS management pack does not include the below HDFS configurations/parameters. If using the OneFS mpack as a replacement for the HDFS service, these parameters no longer exist. dfs.datanode.kerberos.principal=hdfs/_HOST@ dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab dfs.namenode.kerberos.principal=hdfs/_HOST@ dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab These are required by Spark2 in a Kerberised environment, and starting the Spark2 History Server will otherwise fail with obscure errors such as "Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Failed to specify server's Kerberos principal name" See my answer on [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487 Workaround was to add them back to Custom hdfs-site, but it should be part of the mpack so it gets handled automatically. was: The OneFS management pack does not include the below HDFS configurations/parameters. If using the OneFS mpack as a replacement for the HDFS service, these parameters no longer exist. dfs.datanode.kerberos.principal=hdfs/_HOST@ dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab dfs.namenode.kerberos.principal=hdfs/_HOST@ dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab These are required by Spark2 in a Kerberised environment, and starting the Spark2 History Server will otherwise fail with obscure errors such as "Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Failed to specify server's Kerberos principal name" See my answer on [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487 ] Workaround was to add them back to Custom hdfs-site, but it should be part of the mpack so it gets handled automatically. > OneFS Mpack missing configuration settings needed for Spark2 > > > Key: AMBARI-25174 > URL: https://issues.apache.org/jira/browse/AMBARI-25174 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 > Environment: HDP 3.1.1 using OneFS instead of HDFS > Isilon 8.2.1.0 (simulator) > isilon-onefs-mpack-1.0.0.0 >Reporter: Bjorn Olsen >Priority: Major > > The OneFS management pack does not include the below HDFS > configurations/parameters. If using the OneFS mpack as a replacement for the > HDFS service, these parameters no longer exist. > dfs.datanode.kerberos.principal=hdfs/_HOST@ > dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab > dfs.namenode.kerberos.principal=hdfs/_HOST@ > dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab > These are required by Spark2 in a Kerberised environment, and starting the > Spark2 History Server will otherwise fail with obscure errors such as "Failed > on local exception: java.io.IOException: Couldn't set up IO streams: > java.lang.IllegalArgumentException: > Failed to specify server's Kerberos principal name" > See my answer on > [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487 > > Workaround was to add them back to Custom hdfs-site, but it should be part of > the mpack so it gets handled automatically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25174) OneFS Mpack missing configuration settings needed for Spark2
[
https://issues.apache.org/jira/browse/AMBARI-25174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bjorn Olsen updated AMBARI-25174:
-
Description:
The OneFS management pack does not include the below HDFS
configurations/parameters. If using the OneFS mpack as a replacement for the
HDFS service, these parameters no longer exist.
dfs.datanode.kerberos.principal=hdfs/_HOST@
dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab
dfs.namenode.kerberos.principal=hdfs/_HOST@
dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab
These are required by Spark2 in a Kerberised environment, and starting the
Spark2 History Server will otherwise fail with obscure errors such as "Failed
on local exception: java.io.IOException: Couldn't set up IO streams:
java.lang.IllegalArgumentException:
Failed to specify server's Kerberos principal name"
See my answer on
[https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487]
was:
The OneFS management pack does not include the below HDFS
configurations/parameters. If using the OneFS mpack as a replacement for the
HDFS service, these parameters no longer exist.
{{dfs.datanode.kerberos.principal=hdfs/_HOST@
dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab
dfs.namenode.kerberos.principal=hdfs/_HOST@
dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab }}
These are required by Spark2 in a Kerberised environment, and Spark2 will fail
with obscure errors "Failed on local exception: java.io.IOException: Couldn't
set up IO streams: java.lang.IllegalArgumentException:
Failed to specify server's Kerberos principal name"
when these parameters do not exist.
See my answer on
https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487
> OneFS Mpack missing configuration settings needed for Spark2
>
>
> Key: AMBARI-25174
> URL: https://issues.apache.org/jira/browse/AMBARI-25174
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.3
> Environment: HDP 3.1.1 using OneFS instead of HDFS
> Isilon 8.2.1.0 (simulator)
> isilon-onefs-mpack-1.0.0.0
>Reporter: Bjorn Olsen
>Priority: Major
>
> The OneFS management pack does not include the below HDFS
> configurations/parameters. If using the OneFS mpack as a replacement for the
> HDFS service, these parameters no longer exist.
> dfs.datanode.kerberos.principal=hdfs/_HOST@
> dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab
> dfs.namenode.kerberos.principal=hdfs/_HOST@
> dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab
> These are required by Spark2 in a Kerberised environment, and starting the
> Spark2 History Server will otherwise fail with obscure errors such as "Failed
> on local exception: java.io.IOException: Couldn't set up IO streams:
> java.lang.IllegalArgumentException:
> Failed to specify server's Kerberos principal name"
> See my answer on
> [https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25174) OneFS Mpack missing configuration settings needed for Spark2
Bjorn Olsen created AMBARI-25174:
Summary: OneFS Mpack missing configuration settings needed for
Spark2
Key: AMBARI-25174
URL: https://issues.apache.org/jira/browse/AMBARI-25174
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.3
Environment: HDP 3.1.1 using OneFS instead of HDFS
Isilon 8.2.1.0 (simulator)
isilon-onefs-mpack-1.0.0.0
Reporter: Bjorn Olsen
The OneFS management pack does not include the below HDFS
configurations/parameters. If using the OneFS mpack as a replacement for the
HDFS service, these parameters no longer exist.
{{dfs.datanode.kerberos.principal=hdfs/_HOST@
dfs.datanode.keytab.file=/etc/security/keytabs/hdfs.service.keytab
dfs.namenode.kerberos.principal=hdfs/_HOST@
dfs.namenode.keytab.file=/etc/security/keytabs/hdfs.service.keytab }}
These are required by Spark2 in a Kerberised environment, and Spark2 will fail
with obscure errors "Failed on local exception: java.io.IOException: Couldn't
set up IO streams: java.lang.IllegalArgumentException:
Failed to specify server's Kerberos principal name"
when these parameters do not exist.
See my answer on
https://stackoverflow.com/questions/35325720/connecting-to-kerberrized-hdfs-java-lang-illegalargumentexception-failed-to-s/54926487
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24793) Background tasks dialog should indicate the Request User
[ https://issues.apache.org/jira/browse/AMBARI-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-24793: - Summary: Background tasks dialog should indicate the Request User (was: Background tasks dialog should show the Request User) > Background tasks dialog should indicate the Request User > > > Key: AMBARI-24793 > URL: https://issues.apache.org/jira/browse/AMBARI-24793 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > In a multi-user environment it is useful to know which user has initiated a > particular administrative function. This assists when support is carried out > by multiple users who may need to ascertain from other users why a particular > action was done. > Currently this is easily visible for configuration changes, but not for > starting/stopping services, running service checks etc. > > This improvement is to add the "Requesting user" to the current "Background > tasks" dialog so that it is immediately apparent which user requested each > action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24793) Background tasks dialog should indicate the user which requested the task
[ https://issues.apache.org/jira/browse/AMBARI-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-24793: - Summary: Background tasks dialog should indicate the user which requested the task (was: Background tasks dialog should indicate the Request User) > Background tasks dialog should indicate the user which requested the task > - > > Key: AMBARI-24793 > URL: https://issues.apache.org/jira/browse/AMBARI-24793 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > In a multi-user environment it is useful to know which user has initiated a > particular administrative function. This assists when support is carried out > by multiple users who may need to ascertain from other users why a particular > action was done. > Currently this is easily visible for configuration changes, but not for > starting/stopping services, running service checks etc. > > This improvement is to add the "Requesting user" to the current "Background > tasks" dialog so that it is immediately apparent which user requested each > action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24793) Background tasks dialog should show the User
Bjorn Olsen created AMBARI-24793: Summary: Background tasks dialog should show the User Key: AMBARI-24793 URL: https://issues.apache.org/jira/browse/AMBARI-24793 Project: Ambari Issue Type: Improvement Components: ambari-server Reporter: Bjorn Olsen In a multi-user environment it is useful to know which user has initiated a particular administrative function. This assists when support is carried out by multiple users who may need to ascertain from other users why a particular action was done. Currently this is easily visible for configuration changes, but not for starting/stopping services, running service checks etc. This improvement is to add the "Requesting user" to the current "Background tasks" dialog so that it is immediately apparent which user requested each action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24793) Background tasks dialog should show the Request User
[ https://issues.apache.org/jira/browse/AMBARI-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-24793: - Summary: Background tasks dialog should show the Request User (was: Background tasks dialog should show the User) > Background tasks dialog should show the Request User > > > Key: AMBARI-24793 > URL: https://issues.apache.org/jira/browse/AMBARI-24793 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > In a multi-user environment it is useful to know which user has initiated a > particular administrative function. This assists when support is carried out > by multiple users who may need to ascertain from other users why a particular > action was done. > Currently this is easily visible for configuration changes, but not for > starting/stopping services, running service checks etc. > > This improvement is to add the "Requesting user" to the current "Background > tasks" dialog so that it is immediately apparent which user requested each > action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24377) Indicate to user whenever output rows are limited in Hive view
Bjorn Olsen created AMBARI-24377: Summary: Indicate to user whenever output rows are limited in Hive view Key: AMBARI-24377 URL: https://issues.apache.org/jira/browse/AMBARI-24377 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: Bjorn Olsen Ambari hive view output is limited to 50 rows displayed. The user can press the "Next Page" button to view subsequent output. However this behavior is not intuitive for small datasets. Users who are unfamiliar with Ambari and viewing the data might think that some data is missing from the selected table. The user cannot currently see row numbers on Ambari (if they saw that output ended at exactly 50 rows this behavior might be more intuitive) nor is there a message to say "output was limited to 50 rows" or similar. Suggestion would be to add row numbers to the UI, alternatively to add a message at the bottom of the output display to indicate that the rows displayed are limited. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21465) Setting for comments to be required when saving configuration
[ https://issues.apache.org/jira/browse/AMBARI-21465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-21465: - Description: When configuration changes are saved to an Ambari-managed service, the Save Configuration dialog appears and asks "What did you change?". Currently a user does not need to populate any comment here, and the configuration can still be saved. It would be preferable to have a setting in Ambari to require a minimum length for this field. This would encourage Ambari users to populate meaningful comments when changing service configurations, which makes the configuration version history easier to understand. This is especially useful in multi-user or production environments. The setting could be set to 0 length to support current functionality of not requiring a comment to be populated when configurations are changed. was: When configuration changes are saved to an Ambari-managed service, the Save Configuration dialog appears and asks "What did you change?". Currently a user does not need to populate any comment here, and the configuration can still be saved. It would be preferable to have a setting in Ambari to require a minimum length for this field. This would encourage Ambari users to populate meaningful comments when changing service configurations, which makes the configuration version history easier to understand. This is especially useful in multi-user or production environments. > Setting for comments to be required when saving configuration > - > > Key: AMBARI-21465 > URL: https://issues.apache.org/jira/browse/AMBARI-21465 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > When configuration changes are saved to an Ambari-managed service, the Save > Configuration dialog appears and asks "What did you change?". Currently a > user does not need to populate any comment here, and the configuration can > still be saved. > It would be preferable to have a setting in Ambari to require a minimum > length for this field. This would encourage Ambari users to populate > meaningful comments when changing service configurations, which makes the > configuration version history easier to understand. This is especially useful > in multi-user or production environments. > The setting could be set to 0 length to support current functionality of not > requiring a comment to be populated when configurations are changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21465) Setting for comments to be required when saving configuration
Bjorn Olsen created AMBARI-21465: Summary: Setting for comments to be required when saving configuration Key: AMBARI-21465 URL: https://issues.apache.org/jira/browse/AMBARI-21465 Project: Ambari Issue Type: Improvement Components: ambari-server Reporter: Bjorn Olsen Priority: Minor When configuration changes are saved to an Ambari-managed service, the Save Configuration dialog appears and asks "What did you change?". Currently a user does not need to populate any comment here, and the configuration can still be saved. It would be preferable to have a setting in Ambari to require a minimum length for this field. This would encourage Ambari users to populate meaningful comments when changing service configurations, which makes the configuration version history easier to understand. This is especially useful in multi-user or production environments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
