[jira] [Commented] (AMBARI-22235) Druid service check failed during EU
[
https://issues.apache.org/jira/browse/AMBARI-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203694#comment-16203694
]
slim bouguerra commented on AMBARI-22235:
-
https://reviews.apache.org/r/62978/
> Druid service check failed during EU
>
>
> Key: AMBARI-22235
> URL: https://issues.apache.org/jira/browse/AMBARI-22235
> Project: Ambari
> Issue Type: Bug
>Reporter: slim bouguerra
>Assignee: Robert Levas
>
> Observed this issue on two clusters
> Druid service check failed during EU
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 44, in
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 30, in service_check
> self.checkComponent(params, "druid_coordinator", "druid-coordinator")
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 40, in checkComponent
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o
> /dev/null -w'%{http_code}' --negotiate -u: -k
> ctr-e134-1499953498516-217002-01-10.hwx.site:8081/status | grep 200'
> returned 1.
> {code}
> Here is the failure stack trace from druid logs
> {code}
>
> Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match expected
> value (906)
> at sun.security.krb5.internal.KDCRep.init(KDCRep.java:140)
> ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.init(ASRep.java:64) ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.(ASRep.java:59)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsRep.(KrbAsRep.java:60) ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:316)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:361)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584)
> ~[?:1.7.0_95]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.7.0_95]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> ~[?:1.7.0_95]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.7.0_95]
> at java.lang.reflect.Method.invoke(Method.java:606) ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.invoke(LoginContext.java:762)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext$4.run(LoginContext.java:690)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext$4.run(LoginContext.java:688)
> ~[?:1.7.0_95]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:687)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.login(LoginContext.java:595)
> ~[?:1.7.0_95]
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:1089)
> ~[?:?]
>
[jira] [Commented] (AMBARI-22235) Druid service check failed during EU
[
https://issues.apache.org/jira/browse/AMBARI-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203691#comment-16203691
]
slim bouguerra commented on AMBARI-22235:
-
Also, will be applying [~rlevas] suggestion to remove unnecessary identity
blocks from the Druid Kerberos descriptor file. For example any identity block
the simply declares a reverence to "/druid" is not really doing anything,
especially since there is no identity named "/druid" at the root of the
Kerberos descriptor tree.
> Druid service check failed during EU
>
>
> Key: AMBARI-22235
> URL: https://issues.apache.org/jira/browse/AMBARI-22235
> Project: Ambari
> Issue Type: Bug
>Reporter: slim bouguerra
>
> Observed this issue on two clusters
> Druid service check failed during EU
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 44, in
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 30, in service_check
> self.checkComponent(params, "druid_coordinator", "druid-coordinator")
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 40, in checkComponent
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o
> /dev/null -w'%{http_code}' --negotiate -u: -k
> ctr-e134-1499953498516-217002-01-10.hwx.site:8081/status | grep 200'
> returned 1.
> {code}
> Here is the failure stack trace from druid logs
> {code}
>
> Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match expected
> value (906)
> at sun.security.krb5.internal.KDCRep.init(KDCRep.java:140)
> ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.init(ASRep.java:64) ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.(ASRep.java:59)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsRep.(KrbAsRep.java:60) ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:316)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:361)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584)
> ~[?:1.7.0_95]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.7.0_95]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> ~[?:1.7.0_95]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.7.0_95]
> at java.lang.reflect.Method.invoke(Method.java:606) ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.invoke(LoginContext.java:762)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext$4.run(LoginContext.java:690)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext$4.run(LoginContext.java:688)
> ~[?:1.7.0_95]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[?:1.7.0_95]
> at
>
[jira] [Updated] (AMBARI-22235) Druid service check failed during EU
[
https://issues.apache.org/jira/browse/AMBARI-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
slim bouguerra updated AMBARI-22235:
Assignee: Robert Levas
Status: Patch Available (was: Open)
> Druid service check failed during EU
>
>
> Key: AMBARI-22235
> URL: https://issues.apache.org/jira/browse/AMBARI-22235
> Project: Ambari
> Issue Type: Bug
>Reporter: slim bouguerra
>Assignee: Robert Levas
>
> Observed this issue on two clusters
> Druid service check failed during EU
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 44, in
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 30, in service_check
> self.checkComponent(params, "druid_coordinator", "druid-coordinator")
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 40, in checkComponent
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o
> /dev/null -w'%{http_code}' --negotiate -u: -k
> ctr-e134-1499953498516-217002-01-10.hwx.site:8081/status | grep 200'
> returned 1.
> {code}
> Here is the failure stack trace from druid logs
> {code}
>
> Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match expected
> value (906)
> at sun.security.krb5.internal.KDCRep.init(KDCRep.java:140)
> ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.init(ASRep.java:64) ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.(ASRep.java:59)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsRep.(KrbAsRep.java:60) ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:316)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:361)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584)
> ~[?:1.7.0_95]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.7.0_95]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> ~[?:1.7.0_95]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.7.0_95]
> at java.lang.reflect.Method.invoke(Method.java:606) ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.invoke(LoginContext.java:762)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext$4.run(LoginContext.java:690)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext$4.run(LoginContext.java:688)
> ~[?:1.7.0_95]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:687)
> ~[?:1.7.0_95]
> at
> javax.security.auth.login.LoginContext.login(LoginContext.java:595)
> ~[?:1.7.0_95]
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:1089)
> ~[?:?]
>
[jira] [Commented] (AMBARI-22235) Druid service check failed during EU
[
https://issues.apache.org/jira/browse/AMBARI-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203686#comment-16203686
]
slim bouguerra commented on AMBARI-22235:
-
As per [~rlevas] explanation.
The issue is related to the default value of the Druid principal...
{code}
"value": "${druid-env/druid_user}@${realm}",
{code}
Though technically this is correct, by not adding some potentially unique value
to the principal name we run the risk of invalidating the Druid keytab file if
multiple clusters are configured to use the same KDC. This is because Ambari
will change the password for a principal when it goes to create the relevant
keytab file.
All headless (or user) Kerberos identities should include something like the
cluster name in its principal name. Ambari will do this for you by adding the
{principal_suffix}} variable. For example:
{code}
"value": "${druid-env/druid_user}${principal_suffix}@${realm}",
{code}
By default, this is set to a dash followed by the cluster's name. This may
result in the following principal name:
{code}
druid-...@hwqe.hortonworks.com
{code}
> Druid service check failed during EU
>
>
> Key: AMBARI-22235
> URL: https://issues.apache.org/jira/browse/AMBARI-22235
> Project: Ambari
> Issue Type: Bug
>Reporter: slim bouguerra
>
> Observed this issue on two clusters
> Druid service check failed during EU
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 44, in
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 30, in service_check
> self.checkComponent(params, "druid_coordinator", "druid-coordinator")
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
> line 40, in checkComponent
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o
> /dev/null -w'%{http_code}' --negotiate -u: -k
> ctr-e134-1499953498516-217002-01-10.hwx.site:8081/status | grep 200'
> returned 1.
> {code}
> Here is the failure stack trace from druid logs
> {code}
>
> Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match expected
> value (906)
> at sun.security.krb5.internal.KDCRep.init(KDCRep.java:140)
> ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.init(ASRep.java:64) ~[?:1.7.0_95]
> at sun.security.krb5.internal.ASRep.(ASRep.java:59)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsRep.(KrbAsRep.java:60) ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:316)
> ~[?:1.7.0_95]
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:361)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735)
> ~[?:1.7.0_95]
> at
> com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584)
> ~[?:1.7.0_95]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.7.0_95]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> ~[?:1.7.0_95]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.7.0_95]
> at
[jira] [Created] (AMBARI-22235) Druid service check failed during EU
slim bouguerra created AMBARI-22235:
---
Summary: Druid service check failed during EU
Key: AMBARI-22235
URL: https://issues.apache.org/jira/browse/AMBARI-22235
Project: Ambari
Issue Type: Bug
Reporter: slim bouguerra
Observed this issue on two clusters
Druid service check failed during EU
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
line 44, in
ServiceCheck().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 367, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
line 30, in service_check
self.checkComponent(params, "druid_coordinator", "druid-coordinator")
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py",
line 40, in checkComponent
logoutput=True)
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 166, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 262, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 72, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o
/dev/null -w'%{http_code}' --negotiate -u: -k
ctr-e134-1499953498516-217002-01-10.hwx.site:8081/status | grep 200'
returned 1.
{code}
Here is the failure stack trace from druid logs
{code}
Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match expected
value (906)
at sun.security.krb5.internal.KDCRep.init(KDCRep.java:140) ~[?:1.7.0_95]
at sun.security.krb5.internal.ASRep.init(ASRep.java:64) ~[?:1.7.0_95]
at sun.security.krb5.internal.ASRep.(ASRep.java:59) ~[?:1.7.0_95]
at sun.security.krb5.KrbAsRep.(KrbAsRep.java:60) ~[?:1.7.0_95]
at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:316)
~[?:1.7.0_95]
at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:361)
~[?:1.7.0_95]
at
com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735)
~[?:1.7.0_95]
at
com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584)
~[?:1.7.0_95]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:1.7.0_95]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
~[?:1.7.0_95]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.7.0_95]
at java.lang.reflect.Method.invoke(Method.java:606) ~[?:1.7.0_95]
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:762)
~[?:1.7.0_95]
at
javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
~[?:1.7.0_95]
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:690)
~[?:1.7.0_95]
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:688)
~[?:1.7.0_95]
at java.security.AccessController.doPrivileged(Native Method)
~[?:1.7.0_95]
at
javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:687)
~[?:1.7.0_95]
at javax.security.auth.login.LoginContext.login(LoginContext.java:595)
~[?:1.7.0_95]
at
org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:1089)
~[?:?]
at
io.druid.storage.hdfs.HdfsStorageAuthentication.authenticate(HdfsStorageAuthentication.java:65)
~[?:?]
... 10 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22162) Move out the druid configurations from hive-site to hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-22162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-22162: Status: Patch Available (was: Reopened) > Move out the druid configurations from hive-site to hive-interactive-site. > --- > > Key: AMBARI-22162 > URL: https://issues.apache.org/jira/browse/AMBARI-22162 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Reporter: slim bouguerra >Assignee: Swapan Shridhar > Attachments: AMBARI-22162.branch2_6.3.patch > > > Move out the druid configurations from hive-site to hive-interactive-site. > Druid properties do not apply to hive one anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22162) Move out the druid configurations from hive-site to hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-22162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-22162: Attachment: AMBARI-22162.branch2_6.3.patch > Move out the druid configurations from hive-site to hive-interactive-site. > --- > > Key: AMBARI-22162 > URL: https://issues.apache.org/jira/browse/AMBARI-22162 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Reporter: slim bouguerra >Assignee: Swapan Shridhar > Attachments: AMBARI-22162.branch2_6.3.patch > > > Move out the druid configurations from hive-site to hive-interactive-site. > Druid properties do not apply to hive one anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22176) Remove duplicate kerberos setting for superset
[ https://issues.apache.org/jira/browse/AMBARI-22176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197475#comment-16197475 ] slim bouguerra commented on AMBARI-22176: - [~rlevas] Ambari kerberos setup is failing due to the collision between keys setups of the superset. This is due to the fact that superset is no longer using druid credentials but using its own pair of user/key. > Remove duplicate kerberos setting for superset > -- > > Key: AMBARI-22176 > URL: https://issues.apache.org/jira/browse/AMBARI-22176 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: slim bouguerra >Assignee: slim bouguerra > Attachments: AMBARI-22176.patch > > > Remove duplicate setting of kerberos key related to superset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22176) Remove duplicate kerberos setting for superset
[ https://issues.apache.org/jira/browse/AMBARI-22176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197460#comment-16197460 ] slim bouguerra commented on AMBARI-22176: - https://reviews.apache.org/r/62849/ > Remove duplicate kerberos setting for superset > -- > > Key: AMBARI-22176 > URL: https://issues.apache.org/jira/browse/AMBARI-22176 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: slim bouguerra >Assignee: Robert Levas > Attachments: AMBARI-22176.patch > > > Remove duplicate setting of kerberos key related to superset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22176) Remove duplicate kerberos setting for superset
[ https://issues.apache.org/jira/browse/AMBARI-22176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-22176: Attachment: AMBARI-22176.patch > Remove duplicate kerberos setting for superset > -- > > Key: AMBARI-22176 > URL: https://issues.apache.org/jira/browse/AMBARI-22176 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: slim bouguerra >Assignee: Robert Levas > Attachments: AMBARI-22176.patch > > > Remove duplicate setting of kerberos key related to superset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22176) Remove duplicate kerberos setting for superset
[ https://issues.apache.org/jira/browse/AMBARI-22176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-22176: Status: Patch Available (was: Open) > Remove duplicate kerberos setting for superset > -- > > Key: AMBARI-22176 > URL: https://issues.apache.org/jira/browse/AMBARI-22176 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: slim bouguerra >Assignee: Robert Levas > > Remove duplicate setting of kerberos key related to superset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22176) Remove duplicate kerberos setting for superset
slim bouguerra created AMBARI-22176: --- Summary: Remove duplicate kerberos setting for superset Key: AMBARI-22176 URL: https://issues.apache.org/jira/browse/AMBARI-22176 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: slim bouguerra Assignee: Robert Levas Remove duplicate setting of kerberos key related to superset -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22162) Move out the druid configurations from hive-site to hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-22162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194783#comment-16194783 ] slim bouguerra commented on AMBARI-22162: - https://reviews.apache.org/r/62811/ > Move out the druid configurations from hive-site to hive-interactive-site. > --- > > Key: AMBARI-22162 > URL: https://issues.apache.org/jira/browse/AMBARI-22162 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Reporter: slim bouguerra >Assignee: Swapan Shridhar > > Move out the druid configurations from hive-site to hive-interactive-site. > Druid properties do not apply to hive one anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22162) Move out the druid configurations from hive-site to hive-interactive-site.
slim bouguerra created AMBARI-22162: --- Summary: Move out the druid configurations from hive-site to hive-interactive-site. Key: AMBARI-22162 URL: https://issues.apache.org/jira/browse/AMBARI-22162 Project: Ambari Issue Type: Bug Components: HiveServer2, Metastore, and Client Heap Sizes to Smart Configs Reporter: slim bouguerra Assignee: Swapan Shridhar Move out the druid configurations from hive-site to hive-interactive-site. Druid properties do not apply to hive one anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22162) Move out the druid configurations from hive-site to hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-22162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-22162: Status: Patch Available (was: Open) > Move out the druid configurations from hive-site to hive-interactive-site. > --- > > Key: AMBARI-22162 > URL: https://issues.apache.org/jira/browse/AMBARI-22162 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Reporter: slim bouguerra >Assignee: Swapan Shridhar > > Move out the druid configurations from hive-site to hive-interactive-site. > Druid properties do not apply to hive one anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21776) Move druid version to druid 0.10.1 and drop TP flag
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190535#comment-16190535 ] slim bouguerra commented on AMBARI-21776: - I have done the manually upgrade testing and services were up and running. > Move druid version to druid 0.10.1 and drop TP flag > --- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > Attachments: AMBARI-21776.2.patch > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21776) Move druid version to druid 0.10.1 and drop TP flag
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21776: Attachment: AMBARI-21776.2.patch > Move druid version to druid 0.10.1 and drop TP flag > --- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > Attachments: AMBARI-21776.2.patch > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21776) Move druid version to druid 0.10.1 and drop TP flag
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21776: Attachment: (was: AMBARI-21776.patch) > Move druid version to druid 0.10.1 and drop TP flag > --- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21786) Add Forking properties to druid MM nodes
[ https://issues.apache.org/jira/browse/AMBARI-21786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137753#comment-16137753 ] slim bouguerra commented on AMBARI-21786: - https://reviews.apache.org/r/61834/ > Add Forking properties to druid MM nodes > > > Key: AMBARI-21786 > URL: https://issues.apache.org/jira/browse/AMBARI-21786 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > > In cases where the cluster timezone is not UTC we need to have such > properties to make sure that druid indexing works -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21786) Add Forking properties to druid MM nodes
slim bouguerra created AMBARI-21786: --- Summary: Add Forking properties to druid MM nodes Key: AMBARI-21786 URL: https://issues.apache.org/jira/browse/AMBARI-21786 Project: Ambari Issue Type: Bug Reporter: slim bouguerra Assignee: slim bouguerra In cases where the cluster timezone is not UTC we need to have such properties to make sure that druid indexing works -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21775) [Druid] Wrong logrotate configuration for generating an excess of cron email messages
[
https://issues.apache.org/jira/browse/AMBARI-21775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137750#comment-16137750
]
slim bouguerra commented on AMBARI-21775:
-
https://reviews.apache.org/r/61831/
> [Druid] Wrong logrotate configuration for generating an excess of cron email
> messages
> -
>
> Key: AMBARI-21775
> URL: https://issues.apache.org/jira/browse/AMBARI-21775
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: slim bouguerra
>Assignee: slim bouguerra
> Fix For: 2.6.0
>
>
> Druid related configuration is generating the following corn email
> {code}
> /etc/cron.daily/logrotate:
> error: druid:12 unknown unit 'B'
> error: found error in /var/log/druid/*.log , skipping
> {code}
> This is due to wrong logrotate config
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21776) Move druid version to druid 0.10.1 and drop TP flag
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137678#comment-16137678 ] slim bouguerra commented on AMBARI-21776: - https://reviews.apache.org/r/61830/ > Move druid version to druid 0.10.1 and drop TP flag > --- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > Attachments: AMBARI-21776.patch > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21776) Move druid version to druid 0.10.1 and drop TP flag
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21776: Summary: Move druid version to druid 0.10.1 and drop TP flag (was: Move druid version to druid 0.10.1) > Move druid version to druid 0.10.1 and drop TP flag > --- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > Attachments: AMBARI-21776.patch > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21776) Move druid version to druid 0.10.1
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21776: Attachment: AMBARI-21776.patch > Move druid version to druid 0.10.1 > -- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > Attachments: AMBARI-21776.patch > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21776) Move druid version to druid 0.10.1
[ https://issues.apache.org/jira/browse/AMBARI-21776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21776: Status: Patch Available (was: Open) > Move druid version to druid 0.10.1 > -- > > Key: AMBARI-21776 > URL: https://issues.apache.org/jira/browse/AMBARI-21776 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > > Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21776) Move druid version to druid 0.10.1
slim bouguerra created AMBARI-21776: --- Summary: Move druid version to druid 0.10.1 Key: AMBARI-21776 URL: https://issues.apache.org/jira/browse/AMBARI-21776 Project: Ambari Issue Type: Bug Reporter: slim bouguerra Assignee: slim bouguerra Fix For: 2.6.0 Move druid version to 0.10.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21775) [Druid] Wrong logrotate configuration for generating an excess of cron email messages
slim bouguerra created AMBARI-21775:
---
Summary: [Druid] Wrong logrotate configuration for generating an
excess of cron email messages
Key: AMBARI-21775
URL: https://issues.apache.org/jira/browse/AMBARI-21775
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: slim bouguerra
Fix For: 2.6.0
Druid related configuration is generating the following corn email
{code}
/etc/cron.daily/logrotate:
error: druid:12 unknown unit 'B'
error: found error in /var/log/druid/*.log , skipping
{code}
This is due to wrong logrotate config
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21775) [Druid] Wrong logrotate configuration for generating an excess of cron email messages
[
https://issues.apache.org/jira/browse/AMBARI-21775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
slim bouguerra reassigned AMBARI-21775:
---
Assignee: slim bouguerra
> [Druid] Wrong logrotate configuration for generating an excess of cron email
> messages
> -
>
> Key: AMBARI-21775
> URL: https://issues.apache.org/jira/browse/AMBARI-21775
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: slim bouguerra
>Assignee: slim bouguerra
> Fix For: 2.6.0
>
>
> Druid related configuration is generating the following corn email
> {code}
> /etc/cron.daily/logrotate:
> error: druid:12 unknown unit 'B'
> error: found error in /var/log/druid/*.log , skipping
> {code}
> This is due to wrong logrotate config
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21641) Add llap task keytab file and user config values
[
https://issues.apache.org/jira/browse/AMBARI-21641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
slim bouguerra updated AMBARI-21641:
Attachment: testing_kerberos.png
> Add llap task keytab file and user config values
>
>
> Key: AMBARI-21641
> URL: https://issues.apache.org/jira/browse/AMBARI-21641
> Project: Ambari
> Issue Type: Improvement
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Reporter: slim bouguerra
>Assignee: Swapan Shridhar
> Fix For: 2.6.0
>
> Attachments: testing_kerberos.png
>
>
> As per
> https://github.com/hortonworks-spark/spark-llap/wiki/5.-Configuration#custom-hive-interactive-site
> When using on kerberized clusters, we have to add the followings properties
> into hive-interactive-site
> {code}
> hive.llap.task.principal=hive/_h...@example.com
> hive.llap.task.keytab.file=/etc/security/keytabs/hive.service.keytab
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21641) Add llap task keytab file and user config values
[
https://issues.apache.org/jira/browse/AMBARI-21641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
slim bouguerra updated AMBARI-21641:
Status: Patch Available (was: Open)
> Add llap task keytab file and user config values
>
>
> Key: AMBARI-21641
> URL: https://issues.apache.org/jira/browse/AMBARI-21641
> Project: Ambari
> Issue Type: Improvement
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Reporter: slim bouguerra
>Assignee: Swapan Shridhar
> Fix For: 2.6.0
>
>
> As per
> https://github.com/hortonworks-spark/spark-llap/wiki/5.-Configuration#custom-hive-interactive-site
> When using on kerberized clusters, we have to add the followings properties
> into hive-interactive-site
> {code}
> hive.llap.task.principal=hive/_h...@example.com
> hive.llap.task.keytab.file=/etc/security/keytabs/hive.service.keytab
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21642) Add hadoop LZO jars if installed in the cluster
[ https://issues.apache.org/jira/browse/AMBARI-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122151#comment-16122151 ] slim bouguerra commented on AMBARI-21642: - [~aonishuk] thanks! > Add hadoop LZO jars if installed in the cluster > --- > > Key: AMBARI-21642 > URL: https://issues.apache.org/jira/browse/AMBARI-21642 > Project: Ambari > Issue Type: Improvement >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > > Check the existence of hadoop lzo packages and added to the > druid-hadoop-clients directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21642) Add hadoop LZO jars if installed in the cluster
[
https://issues.apache.org/jira/browse/AMBARI-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120534#comment-16120534
]
slim bouguerra commented on AMBARI-21642:
-
This seems to be independent from the druid code it self.
Looking at the exception root
[code|https://github.com/apache/ambari/blob/ddaa5be40965768283e7a7e4f57db5646389bce1/ambari-common/src/main/python/resource_management/libraries/functions/packages_analyzer.py#L283]
seems like the function {code} rmf_shell.checked_call{code} is returning 2
values instead of 3 which is a valid case looking at the code source of the
function here [function
here|https://github.com/apache/ambari/blob/383901fdec7acd9a0be1c42c97438048f7031272/ambari-common/src/main/python/resource_management/core/shell.py#L309]
cc [~aonishuk] the original author of shell.py any idea if the fix should be
something like this
{code}
results = rmf_shell.checked_call(
"rpm -q --queryformat '%{{version}}-%{{release}}' {0} | sed -e
's/\.el[0-9]//g'".format(package_name),
stderr=subprocess.PIPE)
if (len(results) == 3):
code, out, err = results
elif (len(results) == 2):
code, out = results
{code}
> Add hadoop LZO jars if installed in the cluster
> ---
>
> Key: AMBARI-21642
> URL: https://issues.apache.org/jira/browse/AMBARI-21642
> Project: Ambari
> Issue Type: Improvement
>Reporter: slim bouguerra
>Assignee: slim bouguerra
> Fix For: 2.6.0
>
>
> Check the existence of hadoop lzo packages and added to the
> druid-hadoop-clients directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21642) Add hadoop LZO jars if installed in the cluster
[ https://issues.apache.org/jira/browse/AMBARI-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21642: Description: Check the existence of hadoop lzo packages and added to the druid-hadoop-clients directory. was:Set the hadoop class path using ambari > Add hadoop LZO jars if installed in the cluster > --- > > Key: AMBARI-21642 > URL: https://issues.apache.org/jira/browse/AMBARI-21642 > Project: Ambari > Issue Type: Improvement >Reporter: slim bouguerra > Fix For: 2.6.0 > > > Check the existence of hadoop lzo packages and added to the > druid-hadoop-clients directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21642) Add hadoop LZO jars if installed in the cluster
[ https://issues.apache.org/jira/browse/AMBARI-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21642: Summary: Add hadoop LZO jars if installed in the cluster (was: set druid hadoop classpath via ambari) > Add hadoop LZO jars if installed in the cluster > --- > > Key: AMBARI-21642 > URL: https://issues.apache.org/jira/browse/AMBARI-21642 > Project: Ambari > Issue Type: Improvement >Reporter: slim bouguerra > Fix For: 2.6.0 > > > Set the hadoop class path using ambari -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21642) set druid hadoop classpath via ambari
slim bouguerra created AMBARI-21642: --- Summary: set druid hadoop classpath via ambari Key: AMBARI-21642 URL: https://issues.apache.org/jira/browse/AMBARI-21642 Project: Ambari Issue Type: Improvement Reporter: slim bouguerra Fix For: 2.6.0 Set the hadoop class path using ambari -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21641) Add llap task keytab file and user config values
slim bouguerra created AMBARI-21641:
---
Summary: Add llap task keytab file and user config values
Key: AMBARI-21641
URL: https://issues.apache.org/jira/browse/AMBARI-21641
Project: Ambari
Issue Type: Improvement
Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
Configs
Reporter: slim bouguerra
Assignee: Swapan Shridhar
Fix For: 2.6.0
As per
https://github.com/hortonworks-spark/spark-llap/wiki/5.-Configuration#custom-hive-interactive-site
When using on kerberized clusters, we have to add the followings properties
into hive-interactive-site
{code}
hive.llap.task.principal=hive/_h...@example.com
hive.llap.task.keytab.file=/etc/security/keytabs/hive.service.keytab
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21620) Set the needed druid/hive properties via ambari
[ https://issues.apache.org/jira/browse/AMBARI-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra reassigned AMBARI-21620: --- Assignee: Swapan Shridhar > Set the needed druid/hive properties via ambari > - > > Key: AMBARI-21620 > URL: https://issues.apache.org/jira/browse/AMBARI-21620 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Swapan Shridhar > Fix For: 2.6.0 > > > setup the shared properties between druid and hive. > Currently hive does have dozen of druid properties > https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java#L2003-L2068 > This Pr adds the properties to the ambari hive site file and set some values > to defaults and other to the needed value via stack adviser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21620) Set the needed druid/hive properties via ambari
[ https://issues.apache.org/jira/browse/AMBARI-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21620: Affects Version/s: 2.5.0 Fix Version/s: 2.6.0 > Set the needed druid/hive properties via ambari > - > > Key: AMBARI-21620 > URL: https://issues.apache.org/jira/browse/AMBARI-21620 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: slim bouguerra > Fix For: 2.6.0 > > > setup the shared properties between druid and hive. > Currently hive does have dozen of druid properties > https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java#L2003-L2068 > This Pr adds the properties to the ambari hive site file and set some values > to defaults and other to the needed value via stack adviser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21620) Set the needed druid/hive properties via ambari
slim bouguerra created AMBARI-21620: --- Summary: Set the needed druid/hive properties via ambari Key: AMBARI-21620 URL: https://issues.apache.org/jira/browse/AMBARI-21620 Project: Ambari Issue Type: Improvement Reporter: slim bouguerra setup the shared properties between druid and hive. Currently hive does have dozen of druid properties https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java#L2003-L2068 This Pr adds the properties to the ambari hive site file and set some values to defaults and other to the needed value via stack adviser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21138) Uncorrect setting of java path for druid service.
[ https://issues.apache.org/jira/browse/AMBARI-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027419#comment-16027419 ] slim bouguerra commented on AMBARI-21138: - https://reviews.apache.org/r/59617/ > Uncorrect setting of java path for druid service. > - > > Key: AMBARI-21138 > URL: https://issues.apache.org/jira/browse/AMBARI-21138 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra > Attachments: AMBARI-21138.patch > > > Currently we append the java_bin to the shell variable PATH, that will not > work if there another java path before hand. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21138) Uncorrect setting of java path for druid service.
[ https://issues.apache.org/jira/browse/AMBARI-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027056#comment-16027056 ] slim bouguerra commented on AMBARI-21138: - CC [~mnishant14] > Uncorrect setting of java path for druid service. > - > > Key: AMBARI-21138 > URL: https://issues.apache.org/jira/browse/AMBARI-21138 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra > Attachments: AMBARI-21138.patch > > > Currently we append the java_bin to the shell variable PATH, that will not > work if there another java path before hand. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21138) Uncorrect setting of java path for druid service.
[ https://issues.apache.org/jira/browse/AMBARI-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21138: Attachment: AMBARI-21138.patch > Uncorrect setting of java path for druid service. > - > > Key: AMBARI-21138 > URL: https://issues.apache.org/jira/browse/AMBARI-21138 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra > Attachments: AMBARI-21138.patch > > > Currently we append the java_bin to the shell variable PATH, that will not > work if there another java path before hand. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21138) Uncorrect setting of java path for druid service.
[ https://issues.apache.org/jira/browse/AMBARI-21138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-21138: Status: Patch Available (was: Open) > Uncorrect setting of java path for druid service. > - > > Key: AMBARI-21138 > URL: https://issues.apache.org/jira/browse/AMBARI-21138 > Project: Ambari > Issue Type: Bug >Reporter: slim bouguerra > > Currently we append the java_bin to the shell variable PATH, that will not > work if there another java path before hand. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21138) Uncorrect setting of java path for druid service.
slim bouguerra created AMBARI-21138: --- Summary: Uncorrect setting of java path for druid service. Key: AMBARI-21138 URL: https://issues.apache.org/jira/browse/AMBARI-21138 Project: Ambari Issue Type: Bug Reporter: slim bouguerra Currently we append the java_bin to the shell variable PATH, that will not work if there another java path before hand. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19885) Druid broker component need to be downscalable.
[ https://issues.apache.org/jira/browse/AMBARI-19885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876672#comment-15876672 ] slim bouguerra commented on AMBARI-19885: - [~avijayan] we can push it out to later version Thanks > Druid broker component need to be downscalable. > --- > > Key: AMBARI-19885 > URL: https://issues.apache.org/jira/browse/AMBARI-19885 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Priority: Minor > Fix For: 2.5.0 > > > Currently druid broker component is declared as MASTER. This makes down > scaling nodes containing Broker impossible via API calls. The only way to do > it is to move the broker somewhere else first then kill the actual target. To > avoid this will declare broker as slave (like druid historical). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19885) Druid broker component need to be downscalable.
slim bouguerra created AMBARI-19885: --- Summary: Druid broker component need to be downscalable. Key: AMBARI-19885 URL: https://issues.apache.org/jira/browse/AMBARI-19885 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: slim bouguerra Priority: Minor Fix For: 2.5.0 Currently druid broker component is declared as MASTER. This makes down scaling nodes containing Broker impossible via API calls. The only way to do it is to move the broker somewhere else first then kill the actual target. To avoid this will declare broker as slave (like druid historical). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMABARI-17981.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMABARI-17981.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMABARI-17981.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch, AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15770216#comment-15770216 ] slim bouguerra commented on AMBARI-19278: - [~amagyar] your patch is exactly the same to mine not sure what you mean by created inside an ambari-server ? > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Status: Patch Available (was: Open) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
slim bouguerra created AMBARI-19278: --- Summary: Typo in the PostgreSQL database name for druid service Key: AMBARI-19278 URL: https://issues.apache.org/jira/browse/AMBARI-19278 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: slim bouguerra Typo in the value of postgresql metadata storage. it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15590257#comment-15590257 ] slim bouguerra commented on AMBARI-17981: - this is suppose to go against ambari stack 2.6 not 2.5 thought ? > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa > Labels: features > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
