[jira] [Commented] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300457#comment-16300457
]
Nishant Bangarwa commented on AMBARI-22306:
---
committed to trunk 6a37985bcdab81a9c5f48b7275b951662856fa91
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300457#comment-16300457
]
Nishant Bangarwa edited comment on AMBARI-22306 at 12/21/17 7:10 PM:
-
committed to trunk
was (Author: nishantbangarwa):
committed to trunk 6a37985bcdab81a9c5f48b7275b951662856fa91
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285767#comment-16285767
]
Nishant Bangarwa commented on AMBARI-22306:
---
[~swapanshridhar] please let me know when the 3.0 branch is open for changes.
Will commit this.
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22306:
--
Status: Patch Available (was: Open)
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22306:
--
Fix Version/s: trunk
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22306:
--
Attachment: AMBARI-22306.patch
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa reassigned AMBARI-22306:
-
Assignee: Nishant Bangarwa
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22274) "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize service page>Druid when superset is also selected to install
[ https://issues.apache.org/jira/browse/AMBARI-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-22274: -- Resolution: Fixed Status: Resolved (was: Patch Available) > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install > --- > > Key: AMBARI-22274 > URL: https://issues.apache.org/jira/browse/AMBARI-22274 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Kishor Ramakrishnan >Assignee: Nishant Bangarwa >Priority: Blocker > Labels: deployment > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22274.patch > > > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install. > STR: > 1. Navigate to Ambari admin page and start install wizard > 2. Select Druid and Superset to be installed from Choose Services page along > with other required services > 3. Navigate to Customize services page step in the wizard > 4. "META DATA STORAGE CONFIG" tab in Druid config tab should be enabled but > is disabled now. > Note: This behavior is only when Superset is chosen, and works fine without > Superset. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22274) "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize service page>Druid when superset is also selected to install
[ https://issues.apache.org/jira/browse/AMBARI-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211661#comment-16211661 ] Nishant Bangarwa commented on AMBARI-22274: --- committed fix to trunk and branch-2.6 > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install > --- > > Key: AMBARI-22274 > URL: https://issues.apache.org/jira/browse/AMBARI-22274 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Kishor Ramakrishnan >Assignee: Nishant Bangarwa >Priority: Blocker > Labels: deployment > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22274.patch > > > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install. > STR: > 1. Navigate to Ambari admin page and start install wizard > 2. Select Druid and Superset to be installed from Choose Services page along > with other required services > 3. Navigate to Customize services page step in the wizard > 4. "META DATA STORAGE CONFIG" tab in Druid config tab should be enabled but > is disabled now. > Note: This behavior is only when Superset is chosen, and works fine without > Superset. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22274) "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize service page>Druid when superset is also selected to install
[ https://issues.apache.org/jira/browse/AMBARI-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-22274: -- Fix Version/s: trunk Status: Patch Available (was: Open) > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install > --- > > Key: AMBARI-22274 > URL: https://issues.apache.org/jira/browse/AMBARI-22274 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Kishor Ramakrishnan >Assignee: Nishant Bangarwa >Priority: Blocker > Labels: deployment > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22274.patch > > > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install. > STR: > 1. Navigate to Ambari admin page and start install wizard > 2. Select Druid and Superset to be installed from Choose Services page along > with other required services > 3. Navigate to Customize services page step in the wizard > 4. "META DATA STORAGE CONFIG" tab in Druid config tab should be enabled but > is disabled now. > Note: This behavior is only when Superset is chosen, and works fine without > Superset. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22274) "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize service page>Druid when superset is also selected to install
[ https://issues.apache.org/jira/browse/AMBARI-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-22274: -- Attachment: AMBARI-22274.patch > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install > --- > > Key: AMBARI-22274 > URL: https://issues.apache.org/jira/browse/AMBARI-22274 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Kishor Ramakrishnan >Assignee: Nishant Bangarwa >Priority: Blocker > Labels: deployment > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22274.patch > > > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install. > STR: > 1. Navigate to Ambari admin page and start install wizard > 2. Select Druid and Superset to be installed from Choose Services page along > with other required services > 3. Navigate to Customize services page step in the wizard > 4. "META DATA STORAGE CONFIG" tab in Druid config tab should be enabled but > is disabled now. > Note: This behavior is only when Superset is chosen, and works fine without > Superset. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22274) "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize service page>Druid when superset is also selected to install
[ https://issues.apache.org/jira/browse/AMBARI-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa reassigned AMBARI-22274: - Assignee: Nishant Bangarwa > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install > --- > > Key: AMBARI-22274 > URL: https://issues.apache.org/jira/browse/AMBARI-22274 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Kishor Ramakrishnan >Assignee: Nishant Bangarwa >Priority: Blocker > Labels: deployment > Fix For: 2.6.0 > > > "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize > service page>Druid when superset is also selected to install. > STR: > 1. Navigate to Ambari admin page and start install wizard > 2. Select Druid and Superset to be installed from Choose Services page along > with other required services > 3. Navigate to Customize services page step in the wizard > 4. "META DATA STORAGE CONFIG" tab in Druid config tab should be enabled but > is disabled now. > Note: This behavior is only when Superset is chosen, and works fine without > Superset. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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
]
Nishant Bangarwa updated AMBARI-22235:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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: 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)
> ~[?:?]
>
[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&focusedCommentId=16203816#comment-16203816
]
Nishant Bangarwa commented on AMBARI-22235:
---
pushed to 2.6 and master.
> 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: 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)
>
[jira] [Assigned] (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
]
Nishant Bangarwa reassigned AMBARI-22235:
-
Assignee: slim bouguerra (was: Robert Levas)
> 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: 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.
[jira] [Updated] (AMBARI-22222) Switch druid to use /var/druid directory instead of /apps/druid on local disk
[ https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-2: -- Attachment: AMBARI-2.patch > Switch druid to use /var/druid directory instead of /apps/druid on local disk > - > > Key: AMBARI-2 > URL: https://issues.apache.org/jira/browse/AMBARI-2 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 2.6.0 > > Attachments: AMBARI-2.patch > > > Druid requires directories be created at /apps/druid. If the /apps directory > is read only, Druid installation will fail. Since /apps directory does not > have any industry wide standards, use a more standard location such as /var > or /usr. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22222) Switch druid to use /var/druid directory instead of /apps/druid on local disk
Nishant Bangarwa created AMBARI-2: - Summary: Switch druid to use /var/druid directory instead of /apps/druid on local disk Key: AMBARI-2 URL: https://issues.apache.org/jira/browse/AMBARI-2 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa Fix For: 2.6.0 Druid requires directories be created at /apps/druid. If the /apps directory is read only, Druid installation will fail. Since /apps directory does not have any industry wide standards, use a more standard location such as /var or /usr. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-1:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-1.patch
>
>
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/broker.py",
> line 28, in
> DruidBroker().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/druid_node.py",
> line 38, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 793, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in format_package_name
> self.load_available_packages()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 756, in load_available_packages
> if self.available_packages_in_repos:
> AttributeError: 'DruidBroker' object has no attribute
> 'available_packages_in_repos'
> {code}
> This issue is due to Ambari trying to install indivifual "Druid Componennt"
> package which is not part of repo, Druid has single
> druid-[version].noarch.rpm.
> Seems there is change in Ambari deploy code to search for each component that
> exist and trying to install the package with component name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202300#comment-16202300
]
Nishant Bangarwa commented on AMBARI-1:
---
committed to trunk and branch-2.6
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-1.patch
>
>
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/broker.py",
> line 28, in
> DruidBroker().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/druid_node.py",
> line 38, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 793, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in format_package_name
> self.load_available_packages()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 756, in load_available_packages
> if self.available_packages_in_repos:
> AttributeError: 'DruidBroker' object has no attribute
> 'available_packages_in_repos'
> {code}
> This issue is due to Ambari trying to install indivifual "Druid Componennt"
> package which is not part of repo, Druid has single
> druid-[version].noarch.rpm.
> Seems there is change in Ambari deploy code to search for each component that
> exist and trying to install the package with component name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202143#comment-16202143
]
Nishant Bangarwa commented on AMBARI-1:
---
this was a always a bug from the beginning, Got uncovered by recent changes in
script.py that started relying on available_packages_in_repos attribute.
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-1.patch
>
>
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/broker.py",
> line 28, in
> DruidBroker().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/druid_node.py",
> line 38, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 793, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in format_package_name
> self.load_available_packages()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 756, in load_available_packages
> if self.available_packages_in_repos:
> AttributeError: 'DruidBroker' object has no attribute
> 'available_packages_in_repos'
> {code}
> This issue is due to Ambari trying to install indivifual "Druid Componennt"
> package which is not part of repo, Druid has single
> druid-[version].noarch.rpm.
> Seems there is change in Ambari deploy code to search for each component that
> exist and trying to install the package with component name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-1:
--
Status: Patch Available (was: Open)
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-1.patch
>
>
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/broker.py",
> line 28, in
> DruidBroker().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/druid_node.py",
> line 38, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 793, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in format_package_name
> self.load_available_packages()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 756, in load_available_packages
> if self.available_packages_in_repos:
> AttributeError: 'DruidBroker' object has no attribute
> 'available_packages_in_repos'
> {code}
> This issue is due to Ambari trying to install indivifual "Druid Componennt"
> package which is not part of repo, Druid has single
> druid-[version].noarch.rpm.
> Seems there is change in Ambari deploy code to search for each component that
> exist and trying to install the package with component name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-1:
--
Attachment: AMBARI-1.patch
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-1.patch
>
>
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/broker.py",
> line 28, in
> DruidBroker().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/druid_node.py",
> line 38, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 793, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in format_package_name
> self.load_available_packages()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 756, in load_available_packages
> if self.available_packages_in_repos:
> AttributeError: 'DruidBroker' object has no attribute
> 'available_packages_in_repos'
> {code}
> This issue is due to Ambari trying to install indivifual "Druid Componennt"
> package which is not part of repo, Druid has single
> druid-[version].noarch.rpm.
> Seems there is change in Ambari deploy code to search for each component that
> exist and trying to install the package with component name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa reassigned AMBARI-1:
-
Assignee: Nishant Bangarwa
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: 2.6.0
>
>
> Druid Components install fails with AttributeError: 'DruidBroker' object has
> no attribute 'available_packages_in_repos'.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/broker.py",
> line 28, in
> DruidBroker().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/druid_node.py",
> line 38, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 793, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in format_package_name
> self.load_available_packages()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 756, in load_available_packages
> if self.available_packages_in_repos:
> AttributeError: 'DruidBroker' object has no attribute
> 'available_packages_in_repos'
> {code}
> This issue is due to Ambari trying to install indivifual "Druid Componennt"
> package which is not part of repo, Druid has single
> druid-[version].noarch.rpm.
> Seems there is change in Ambari deploy code to search for each component that
> exist and trying to install the package with component name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22191) Druid stack advisor for memory does not account number of merge buffers while calculating processing buffer size
[
https://issues.apache.org/jira/browse/AMBARI-22191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22191:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Druid stack advisor for memory does not account number of merge buffers while
> calculating processing buffer size
>
>
> Key: AMBARI-22191
> URL: https://issues.apache.org/jira/browse/AMBARI-22191
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22191.patch
>
>
> This is leading to OOME with default configs on a 16 core machine with 16G of
> ram.
> {code}
> 5) Error in custom provider, java.lang.OutOfMemoryError
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> while locating io.druid.collections.BlockingPool
> annotated with @io.druid.guice.annotations.Merging()
> for the 4th parameter of
> io.druid.query.groupby.strategy.GroupByStrategyV2.(GroupByStrategyV2.java:97)
> while locating io.druid.query.groupby.strategy.GroupByStrategyV2
> for the 3rd parameter of
> io.druid.query.groupby.strategy.GroupByStrategySelector.(GroupByStrategySelector.java:43)
> while locating io.druid.query.groupby.strategy.GroupByStrategySelector
> for the 1st parameter of
> io.druid.query.groupby.GroupByQueryQueryToolChest.(GroupByQueryQueryToolChest.java:104)
> at
> io.druid.guice.QueryToolChestModule.configure(QueryToolChestModule.java:95)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.QueryRunnerFactoryModule)
> while locating io.druid.query.groupby.GroupByQueryQueryToolChest
> while locating io.druid.query.QueryToolChest annotated with
> @com.google.inject.multibindings.Element(setNa
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22191) Druid stack advisor for memory does not account number of merge buffers while calculating processing buffer size
[
https://issues.apache.org/jira/browse/AMBARI-22191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200993#comment-16200993
]
Nishant Bangarwa commented on AMBARI-22191:
---
committed to trunk and branch-2.6.
> Druid stack advisor for memory does not account number of merge buffers while
> calculating processing buffer size
>
>
> Key: AMBARI-22191
> URL: https://issues.apache.org/jira/browse/AMBARI-22191
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22191.patch
>
>
> This is leading to OOME with default configs on a 16 core machine with 16G of
> ram.
> {code}
> 5) Error in custom provider, java.lang.OutOfMemoryError
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> while locating io.druid.collections.BlockingPool
> annotated with @io.druid.guice.annotations.Merging()
> for the 4th parameter of
> io.druid.query.groupby.strategy.GroupByStrategyV2.(GroupByStrategyV2.java:97)
> while locating io.druid.query.groupby.strategy.GroupByStrategyV2
> for the 3rd parameter of
> io.druid.query.groupby.strategy.GroupByStrategySelector.(GroupByStrategySelector.java:43)
> while locating io.druid.query.groupby.strategy.GroupByStrategySelector
> for the 1st parameter of
> io.druid.query.groupby.GroupByQueryQueryToolChest.(GroupByQueryQueryToolChest.java:104)
> at
> io.druid.guice.QueryToolChestModule.configure(QueryToolChestModule.java:95)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.QueryRunnerFactoryModule)
> while locating io.druid.query.groupby.GroupByQueryQueryToolChest
> while locating io.druid.query.QueryToolChest annotated with
> @com.google.inject.multibindings.Element(setNa
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22191) Druid stack advisor for memory does not account number of merge buffers while calculating processing buffer size
[
https://issues.apache.org/jira/browse/AMBARI-22191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22191:
--
Attachment: AMBARI-22191.patch
> Druid stack advisor for memory does not account number of merge buffers while
> calculating processing buffer size
>
>
> Key: AMBARI-22191
> URL: https://issues.apache.org/jira/browse/AMBARI-22191
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22191.patch
>
>
> This is leading to OOME with default configs on a 16 core machine with 16G of
> ram.
> {code}
> 5) Error in custom provider, java.lang.OutOfMemoryError
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> while locating io.druid.collections.BlockingPool
> annotated with @io.druid.guice.annotations.Merging()
> for the 4th parameter of
> io.druid.query.groupby.strategy.GroupByStrategyV2.(GroupByStrategyV2.java:97)
> while locating io.druid.query.groupby.strategy.GroupByStrategyV2
> for the 3rd parameter of
> io.druid.query.groupby.strategy.GroupByStrategySelector.(GroupByStrategySelector.java:43)
> while locating io.druid.query.groupby.strategy.GroupByStrategySelector
> for the 1st parameter of
> io.druid.query.groupby.GroupByQueryQueryToolChest.(GroupByQueryQueryToolChest.java:104)
> at
> io.druid.guice.QueryToolChestModule.configure(QueryToolChestModule.java:95)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.QueryRunnerFactoryModule)
> while locating io.druid.query.groupby.GroupByQueryQueryToolChest
> while locating io.druid.query.QueryToolChest annotated with
> @com.google.inject.multibindings.Element(setNa
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22191) Druid stack advisor for memory does not account number of merge buffers while calculating processing buffer size
[
https://issues.apache.org/jira/browse/AMBARI-22191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22191:
--
Status: Patch Available (was: Open)
> Druid stack advisor for memory does not account number of merge buffers while
> calculating processing buffer size
>
>
> Key: AMBARI-22191
> URL: https://issues.apache.org/jira/browse/AMBARI-22191
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22191.patch
>
>
> This is leading to OOME with default configs on a 16 core machine with 16G of
> ram.
> {code}
> 5) Error in custom provider, java.lang.OutOfMemoryError
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> while locating io.druid.collections.BlockingPool
> annotated with @io.druid.guice.annotations.Merging()
> for the 4th parameter of
> io.druid.query.groupby.strategy.GroupByStrategyV2.(GroupByStrategyV2.java:97)
> while locating io.druid.query.groupby.strategy.GroupByStrategyV2
> for the 3rd parameter of
> io.druid.query.groupby.strategy.GroupByStrategySelector.(GroupByStrategySelector.java:43)
> while locating io.druid.query.groupby.strategy.GroupByStrategySelector
> for the 1st parameter of
> io.druid.query.groupby.GroupByQueryQueryToolChest.(GroupByQueryQueryToolChest.java:104)
> at
> io.druid.guice.QueryToolChestModule.configure(QueryToolChestModule.java:95)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.QueryRunnerFactoryModule)
> while locating io.druid.query.groupby.GroupByQueryQueryToolChest
> while locating io.druid.query.QueryToolChest annotated with
> @com.google.inject.multibindings.Element(setNa
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22191) Druid stack advisor for memory does not account number of merge buffers while calculating processing buffer size
[
https://issues.apache.org/jira/browse/AMBARI-22191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22191:
--
Priority: Critical (was: Major)
> Druid stack advisor for memory does not account number of merge buffers while
> calculating processing buffer size
>
>
> Key: AMBARI-22191
> URL: https://issues.apache.org/jira/browse/AMBARI-22191
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk, 2.6.0
>
>
> This is leading to OOME with default configs on a 16 core machine with 16G of
> ram.
> {code}
> 5) Error in custom provider, java.lang.OutOfMemoryError
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.DruidProcessingModule)
> while locating io.druid.collections.BlockingPool
> annotated with @io.druid.guice.annotations.Merging()
> for the 4th parameter of
> io.druid.query.groupby.strategy.GroupByStrategyV2.(GroupByStrategyV2.java:97)
> while locating io.druid.query.groupby.strategy.GroupByStrategyV2
> for the 3rd parameter of
> io.druid.query.groupby.strategy.GroupByStrategySelector.(GroupByStrategySelector.java:43)
> while locating io.druid.query.groupby.strategy.GroupByStrategySelector
> for the 1st parameter of
> io.druid.query.groupby.GroupByQueryQueryToolChest.(GroupByQueryQueryToolChest.java:104)
> at
> io.druid.guice.QueryToolChestModule.configure(QueryToolChestModule.java:95)
> (via modules: com.google.inject.util.Modules$OverrideModule ->
> com.google.inject.util.Modules$OverrideModule ->
> io.druid.guice.QueryRunnerFactoryModule)
> while locating io.druid.query.groupby.GroupByQueryQueryToolChest
> while locating io.druid.query.QueryToolChest annotated with
> @com.google.inject.multibindings.Element(setNa
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22191) Druid stack advisor for memory does not account number of merge buffers while calculating processing buffer size
Nishant Bangarwa created AMBARI-22191:
-
Summary: Druid stack advisor for memory does not account number of
merge buffers while calculating processing buffer size
Key: AMBARI-22191
URL: https://issues.apache.org/jira/browse/AMBARI-22191
Project: Ambari
Issue Type: Bug
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
Fix For: trunk, 2.6.0
This is leading to OOME with default configs on a 16 core machine with 16G of
ram.
{code}
5) Error in custom provider, java.lang.OutOfMemoryError
at
io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
(via modules: com.google.inject.util.Modules$OverrideModule ->
com.google.inject.util.Modules$OverrideModule ->
io.druid.guice.DruidProcessingModule)
at
io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:124)
(via modules: com.google.inject.util.Modules$OverrideModule ->
com.google.inject.util.Modules$OverrideModule ->
io.druid.guice.DruidProcessingModule)
while locating io.druid.collections.BlockingPool
annotated with @io.druid.guice.annotations.Merging()
for the 4th parameter of
io.druid.query.groupby.strategy.GroupByStrategyV2.(GroupByStrategyV2.java:97)
while locating io.druid.query.groupby.strategy.GroupByStrategyV2
for the 3rd parameter of
io.druid.query.groupby.strategy.GroupByStrategySelector.(GroupByStrategySelector.java:43)
while locating io.druid.query.groupby.strategy.GroupByStrategySelector
for the 1st parameter of
io.druid.query.groupby.GroupByQueryQueryToolChest.(GroupByQueryQueryToolChest.java:104)
at
io.druid.guice.QueryToolChestModule.configure(QueryToolChestModule.java:95)
(via modules: com.google.inject.util.Modules$OverrideModule ->
com.google.inject.util.Modules$OverrideModule ->
io.druid.guice.QueryRunnerFactoryModule)
while locating io.druid.query.groupby.GroupByQueryQueryToolChest
while locating io.druid.query.QueryToolChest annotated with
@com.google.inject.multibindings.Element(setNa
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs
[
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22125:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.6 and trunk
> Druid process fails to start with OOME on small machines with default ambari
> configs
>
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22125.patch
>
>
> Druid fails to start with ambari default configs when all the druid processes
> are allocated on a single node.
> stack trace -
> {code}
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs
[
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22125:
--
Status: Patch Available (was: Open)
> Druid process fails to start with OOME on small machines with default ambari
> configs
>
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22125.patch
>
>
> Druid fails to start with ambari default configs when all the druid processes
> are allocated on a single node.
> stack trace -
> {code}
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs
[
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22125:
--
Attachment: AMBARI-22125.patch
> Druid process fails to start with OOME on small machines with default ambari
> configs
>
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22125.patch
>
>
> Druid fails to start with ambari default configs when all the druid processes
> are allocated on a single node.
> stack trace -
> {code}
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs
[
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22125:
--
Description:
Druid fails to start with ambari default configs when all the druid processes
are allocated on a single node.
stack trace -
{code}
Caused by: java.lang.OutOfMemoryError
at sun.misc.Unsafe.allocateMemory(Native Method)
at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
at
io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
at
io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
at
io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
at
io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
at
io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
at
com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
at
com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
at
com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
{code}
was:
stack trace -
{code}
Caused by: java.lang.OutOfMemoryError
at sun.misc.Unsafe.allocateMemory(Native Method)
at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
at
io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
at
io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
at
io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
at
io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
at
io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
at
com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
at
com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
at
com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
{code}
> Druid process fails to start with OOME on small machines with default ambari
> configs
>
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
>
> Druid fails to start with ambari default configs when all the druid processes
> are allocated on a single node.
> stack trace -
> {code}
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs
Nishant Bangarwa created AMBARI-22125:
-
Summary: Druid process fails to start with OOME on small machines
with default ambari configs
Key: AMBARI-22125
URL: https://issues.apache.org/jira/browse/AMBARI-22125
Project: Ambari
Issue Type: Bug
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
Priority: Blocker
Fix For: trunk, 2.6.0
stack trace -
{code}
Caused by: java.lang.OutOfMemoryError
at sun.misc.Unsafe.allocateMemory(Native Method)
at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
at
io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
at
io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
at
io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
at
io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
at
io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
at
com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
at
com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
at
com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22087) Druid start component via ambari doesn't wait to check if the component is successfully started
[
https://issues.apache.org/jira/browse/AMBARI-22087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-22087:
--
Fix Version/s: trunk
> Druid start component via ambari doesn't wait to check if the component is
> successfully started
> ---
>
> Key: AMBARI-22087
> URL: https://issues.apache.org/jira/browse/AMBARI-22087
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
> Labels: druid
> Fix For: trunk, 2.6.0
>
>
> Druid start component via ambari doesn't wait to check if the component is
> successfully started.
> Any component start for Druid service will just execute the start command
> and comes out with exit status 0. It will not further check if the process is
> running, or any port if its listening.
> say for example Druid Coordinator
> {code}
> 2017-09-19 18:48:47,076 - Execute['/usr/lib/jvm/java-openjdk/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/druid-coordinator/extensions/mysql-metadata-storage/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://ctr-e134-1499953498516-160569-01-07.hwx.site:3306/druid?createDatabaseIfNotExist=true'
> druid [PROTECTED] com.mysql.jdbc.Driver'] {'tries': 5, 'user': 'druid',
> 'try_sleep': 10}
> 2017-09-19 18:48:47,554 - Execute['source
> /usr/hdp/current/druid-coordinator/conf/druid-env.sh ;
> /usr/hdp/current/druid-coordinator/bin/node.sh coordinator start'] {'user':
> 'druid'}
> Command completed successfully!
> {code}
> The start command via Ambari-UI shows as passed on Ambari-ops even if the
> component fails to start. this gives false impression to check the service.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22087) Druid start component via ambari doesn't wait to check if the component is successfully started
[
https://issues.apache.org/jira/browse/AMBARI-22087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa reassigned AMBARI-22087:
-
Assignee: Nishant Bangarwa
> Druid start component via ambari doesn't wait to check if the component is
> successfully started
> ---
>
> Key: AMBARI-22087
> URL: https://issues.apache.org/jira/browse/AMBARI-22087
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
> Labels: druid
> Fix For: 2.6.0
>
>
> Druid start component via ambari doesn't wait to check if the component is
> successfully started.
> Any component start for Druid service will just execute the start command
> and comes out with exit status 0. It will not further check if the process is
> running, or any port if its listening.
> say for example Druid Coordinator
> {code}
> 2017-09-19 18:48:47,076 - Execute['/usr/lib/jvm/java-openjdk/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/druid-coordinator/extensions/mysql-metadata-storage/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://ctr-e134-1499953498516-160569-01-07.hwx.site:3306/druid?createDatabaseIfNotExist=true'
> druid [PROTECTED] com.mysql.jdbc.Driver'] {'tries': 5, 'user': 'druid',
> 'try_sleep': 10}
> 2017-09-19 18:48:47,554 - Execute['source
> /usr/hdp/current/druid-coordinator/conf/druid-env.sh ;
> /usr/hdp/current/druid-coordinator/bin/node.sh coordinator start'] {'user':
> 'druid'}
> Command completed successfully!
> {code}
> The start command via Ambari-UI shows as passed on Ambari-ops even if the
> component fails to start. this gives false impression to check the service.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172058#comment-16172058 ] Nishant Bangarwa commented on AMBARI-21971: --- thanks for the update. Have reverted this in trunk. only committed in branch-2.6 > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Attachment: AMBARI-21971-ADDENDUM.patch > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21937) Ambari server schema upgrade failed while creating DRUID_SUPERSET component
[
https://issues.apache.org/jira/browse/AMBARI-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-21937:
--
Attachment: AMBARI-21937.trunk.patch
> Ambari server schema upgrade failed while creating DRUID_SUPERSET component
> ---
>
> Key: AMBARI-21937
> URL: https://issues.apache.org/jira/browse/AMBARI-21937
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Labels: upgrade
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-21937.patch, AMBARI-21937.trunk.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.0-205
> # Upgrade Ambari packages and then schema (ambari-server upgrade) to target
> Version: 2.6.0.0-77 | Hash: 450aae3dceabb270e0e267c16e2bb198db809541
> *Result*
> Schema upgrade failed with below error:
> {code}
> 12 Sep 2017 01:09:19,339 INFO [Stack Version Loading Thread]
> LatestRepoCallable:106 - Loaded uri
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/hdp_urlinfo.json in 177ms
> 12 Sep 2017 01:09:19,361 ERROR [main] SchemaUpgradeHelper:230 - Upgrade
> failed.
> com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a
> ServiceComponent not recognized in stack info, clusterName=cl1,
> serviceName=DRUID, componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:173)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:95)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> 1 error
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:365)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDMLUpdates(UpgradeCatalog260.java:392)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:228)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:421)
> Caused by: java.lang.RuntimeException: Trying to create a ServiceComponent
> not recognized in stack info, clusterName=cl1, serviceName=DRUID,
> componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.ServiceComponentImpl.updateComponentInfo(ServiceComponentImpl.java:141)
> at
> org.apache.ambari.server.state.ServiceComponentImpl.(ServiceComponentImpl.java:170)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
> at com.sun.proxy.$Proxy19.createExisting(Unknown Source)
> at
> org.apache.ambari.server.state.ServiceImpl.(ServiceImpl.java:162)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
>
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Attachment: AMBARI-21971.2.patch > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Attachment: AMBARI-21971.1.patch handled review comments and uploading new patch. > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Status: Patch Available (was: Open) > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Attachment: AMBARI-21971.patch > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Issue Type: Task (was: Bug) > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
Nishant Bangarwa created AMBARI-21971: - Summary: Add Druid High Availability Check for Rolling Upgrades Key: AMBARI-21971 URL: https://issues.apache.org/jira/browse/AMBARI-21971 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa Fix For: trunk, 2.6.0 For Druid Rolling Upgrades check that each druid component is installed on more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21937) Ambari server schema upgrade failed while creating DRUID_SUPERSET component
[
https://issues.apache.org/jira/browse/AMBARI-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-21937:
--
Fix Version/s: trunk
Status: Patch Available (was: Open)
> Ambari server schema upgrade failed while creating DRUID_SUPERSET component
> ---
>
> Key: AMBARI-21937
> URL: https://issues.apache.org/jira/browse/AMBARI-21937
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Labels: upgrade
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-21937.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.0-205
> # Upgrade Ambari packages and then schema (ambari-server upgrade) to target
> Version: 2.6.0.0-77 | Hash: 450aae3dceabb270e0e267c16e2bb198db809541
> *Result*
> Schema upgrade failed with below error:
> {code}
> 12 Sep 2017 01:09:19,339 INFO [Stack Version Loading Thread]
> LatestRepoCallable:106 - Loaded uri
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/hdp_urlinfo.json in 177ms
> 12 Sep 2017 01:09:19,361 ERROR [main] SchemaUpgradeHelper:230 - Upgrade
> failed.
> com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a
> ServiceComponent not recognized in stack info, clusterName=cl1,
> serviceName=DRUID, componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:173)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:95)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> 1 error
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:365)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDMLUpdates(UpgradeCatalog260.java:392)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:228)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:421)
> Caused by: java.lang.RuntimeException: Trying to create a ServiceComponent
> not recognized in stack info, clusterName=cl1, serviceName=DRUID,
> componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.ServiceComponentImpl.updateComponentInfo(ServiceComponentImpl.java:141)
> at
> org.apache.ambari.server.state.ServiceComponentImpl.(ServiceComponentImpl.java:170)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
> at com.sun.proxy.$Proxy19.createExisting(Unknown Source)
> at
> org.apache.ambari.server.state.ServiceImpl.(ServiceImpl.java:162)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:6
[jira] [Updated] (AMBARI-21937) Ambari server schema upgrade failed while creating DRUID_SUPERSET component
[
https://issues.apache.org/jira/browse/AMBARI-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-21937:
--
Attachment: AMBARI-21937.patch
> Ambari server schema upgrade failed while creating DRUID_SUPERSET component
> ---
>
> Key: AMBARI-21937
> URL: https://issues.apache.org/jira/browse/AMBARI-21937
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21937.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.0-205
> # Upgrade Ambari packages and then schema (ambari-server upgrade) to target
> Version: 2.6.0.0-77 | Hash: 450aae3dceabb270e0e267c16e2bb198db809541
> *Result*
> Schema upgrade failed with below error:
> {code}
> 12 Sep 2017 01:09:19,339 INFO [Stack Version Loading Thread]
> LatestRepoCallable:106 - Loaded uri
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/hdp_urlinfo.json in 177ms
> 12 Sep 2017 01:09:19,361 ERROR [main] SchemaUpgradeHelper:230 - Upgrade
> failed.
> com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a
> ServiceComponent not recognized in stack info, clusterName=cl1,
> serviceName=DRUID, componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:173)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:95)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> 1 error
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:365)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDMLUpdates(UpgradeCatalog260.java:392)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:228)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:421)
> Caused by: java.lang.RuntimeException: Trying to create a ServiceComponent
> not recognized in stack info, clusterName=cl1, serviceName=DRUID,
> componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.ServiceComponentImpl.updateComponentInfo(ServiceComponentImpl.java:141)
> at
> org.apache.ambari.server.state.ServiceComponentImpl.(ServiceComponentImpl.java:170)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
> at com.sun.proxy.$Proxy19.createExisting(Unknown Source)
> at
> org.apache.ambari.server.state.ServiceImpl.(ServiceImpl.java:162)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
> at com.sun.proxy.$Proxy15.creat
[jira] [Assigned] (AMBARI-21937) Ambari server schema upgrade failed while creating DRUID_SUPERSET component
[
https://issues.apache.org/jira/browse/AMBARI-21937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa reassigned AMBARI-21937:
-
Assignee: Nishant Bangarwa
> Ambari server schema upgrade failed while creating DRUID_SUPERSET component
> ---
>
> Key: AMBARI-21937
> URL: https://issues.apache.org/jira/browse/AMBARI-21937
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21937.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.0-205
> # Upgrade Ambari packages and then schema (ambari-server upgrade) to target
> Version: 2.6.0.0-77 | Hash: 450aae3dceabb270e0e267c16e2bb198db809541
> *Result*
> Schema upgrade failed with below error:
> {code}
> 12 Sep 2017 01:09:19,339 INFO [Stack Version Loading Thread]
> LatestRepoCallable:106 - Loaded uri
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/hdp_urlinfo.json in 177ms
> 12 Sep 2017 01:09:19,361 ERROR [main] SchemaUpgradeHelper:230 - Upgrade
> failed.
> com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a
> ServiceComponent not recognized in stack info, clusterName=cl1,
> serviceName=DRUID, componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:173)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:95)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> 1 error
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:365)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDMLUpdates(UpgradeCatalog260.java:392)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:228)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:421)
> Caused by: java.lang.RuntimeException: Trying to create a ServiceComponent
> not recognized in stack info, clusterName=cl1, serviceName=DRUID,
> componentName=DRUID_SUPERSET, stackInfo=HDP-2.6
> at
> org.apache.ambari.server.state.ServiceComponentImpl.updateComponentInfo(ServiceComponentImpl.java:141)
> at
> org.apache.ambari.server.state.ServiceComponentImpl.(ServiceComponentImpl.java:170)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
> at com.sun.proxy.$Proxy19.createExisting(Unknown Source)
> at
> org.apache.ambari.server.state.ServiceImpl.(ServiceImpl.java:162)
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:260)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at
> com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
> at com.sun.proxy.$Proxy15.cr
[jira] [Commented] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147750#comment-16147750 ] Nishant Bangarwa commented on AMBARI-21076: --- the initial patch committed had issues with file rename, Have attached new patch, the first one is already checked in via - https://github.com/apache/ambari/commit/b96c77a8f9dfd021aa4a0b2f825dc2e270f79050 the second one needs to be checked in. +cc [~swapanshridhar] > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076-ADDENDUM.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076-ADDENDUM.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: (was: AMBARI-21076.patch) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076-ADDENDUM.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: (was: AMBARI-21076.5.patch) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076-ADDENDUM.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: (was: AMBARI-21076.3.patch) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.5.patch, AMBARI-21076-ADDENDUM.patch, > AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: (was: AMBARI-21076.1.patch) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.3.patch, AMBARI-21076.5.patch, > AMBARI-21076-ADDENDUM.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: (was: AMBARI-21076.2.patch) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.3.patch, AMBARI-21076.5.patch, > AMBARI-21076-ADDENDUM.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076-ADDENDUM.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.3.patch, AMBARI-21076.5.patch, > AMBARI-21076-ADDENDUM.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
[ https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21836: -- Fix Version/s: 2.6.0 trunk > 2.6.0 Upgrade Fails Because Of Missing Table > > > Key: AMBARI-21836 > URL: https://issues.apache.org/jira/browse/AMBARI-21836 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21836.patch > > > STR: > Install Ambari 2.5 > Upgrade to Ambari 2.6 > The following code is throwing a table not found exception: > String supersetConfigMappingRemoveSQL = String.format( > "DELETE FROM %s WHERE type_name like '%s%%'", > CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); > This was introduced in AMBARI-21076. The problem is that the > clusterconfigmapping table no longer exists... > Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
[ https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21836: -- Status: Patch Available (was: Open) > 2.6.0 Upgrade Fails Because Of Missing Table > > > Key: AMBARI-21836 > URL: https://issues.apache.org/jira/browse/AMBARI-21836 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21836.patch > > > STR: > Install Ambari 2.5 > Upgrade to Ambari 2.6 > The following code is throwing a table not found exception: > String supersetConfigMappingRemoveSQL = String.format( > "DELETE FROM %s WHERE type_name like '%s%%'", > CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); > This was introduced in AMBARI-21076. The problem is that the > clusterconfigmapping table no longer exists... > Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
[ https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21836: -- Attachment: AMBARI-21836.patch > 2.6.0 Upgrade Fails Because Of Missing Table > > > Key: AMBARI-21836 > URL: https://issues.apache.org/jira/browse/AMBARI-21836 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21836.patch > > > STR: > Install Ambari 2.5 > Upgrade to Ambari 2.6 > The following code is throwing a table not found exception: > String supersetConfigMappingRemoveSQL = String.format( > "DELETE FROM %s WHERE type_name like '%s%%'", > CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); > This was introduced in AMBARI-21076. The problem is that the > clusterconfigmapping table no longer exists... > Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
Nishant Bangarwa created AMBARI-21836: - Summary: 2.6.0 Upgrade Fails Because Of Missing Table Key: AMBARI-21836 URL: https://issues.apache.org/jira/browse/AMBARI-21836 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa STR: Install Ambari 2.5 Upgrade to Ambari 2.6 The following code is throwing a table not found exception: String supersetConfigMappingRemoveSQL = String.format( "DELETE FROM %s WHERE type_name like '%s%%'", CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); This was introduced in AMBARI-21076. The problem is that the clusterconfigmapping table no longer exists... Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.5.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.3.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.2.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123218#comment-16123218 ] Nishant Bangarwa commented on AMBARI-21076: --- rebased and attached new patch. [~swapanshridhar] please check again. > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Status: Patch Available (was: Open) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Status: Open (was: Patch Available) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.1.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Status: Patch Available (was: Open) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.patch > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Issue Type: Task (was: Bug) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21076) Move superset as a top-level module in HDP
Nishant Bangarwa created AMBARI-21076: - Summary: Move superset as a top-level module in HDP Key: AMBARI-21076 URL: https://issues.apache.org/jira/browse/AMBARI-21076 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa Superset is a generic UI which can work with multiple data stores e.g HIVE, DRUID and any other dataStore that supports SQLALCHEMY dialects. Currently superset is installed as a master component under Druid. This task is to move superset out of Druid so that it can be installed and managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20647) Druid Superset Password gets printed in installation logs
[
https://issues.apache.org/jira/browse/AMBARI-20647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20647:
--
Attachment: AMBARI-20647.patch
> Druid Superset Password gets printed in installation logs
> -
>
> Key: AMBARI-20647
> URL: https://issues.apache.org/jira/browse/AMBARI-20647
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Attachments: AMBARI-20647.patch
>
>
> From logs -
> 2017-03-31 16:45:09,507 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username 'admin' --password '[PROTECTED]' --firstname 'admin' --lastname
> 'admin' --email 'ad...@admin.com''] {'logoutput': 'false', 'user': 'druid'}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20647) Druid Superset Password gets printed in installation logs
Nishant Bangarwa created AMBARI-20647:
-
Summary: Druid Superset Password gets printed in installation logs
Key: AMBARI-20647
URL: https://issues.apache.org/jira/browse/AMBARI-20647
Project: Ambari
Issue Type: Bug
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
>From logs -
2017-03-31 16:45:09,507 - Execute['source /etc/superset/conf/superset-env.sh ;
/usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
--username 'admin' --password '[PROTECTED]' --firstname 'admin' --lastname
'admin' --email 'ad...@admin.com''] {'logoutput': 'false', 'user': 'druid'}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20522) Add Stack Upgrade support for Druid components
[ https://issues.apache.org/jira/browse/AMBARI-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-20522: -- Attachment: AMBARI-20522.patch > Add Stack Upgrade support for Druid components > -- > > Key: AMBARI-20522 > URL: https://issues.apache.org/jira/browse/AMBARI-20522 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-20522.patch > > > If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be > upgraded as it is not versionable currently. > This task is to make Druid versionable so that we can do an upgrade from > Druid HDP-2.6.x.y to HDP-2.6.u.v -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20522) Add Stack Upgrade support for Druid components
[ https://issues.apache.org/jira/browse/AMBARI-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934955#comment-15934955 ] Nishant Bangarwa commented on AMBARI-20522: --- +cc [~nc...@hortonworks.com] [~sumitmohanty] > Add Stack Upgrade support for Druid components > -- > > Key: AMBARI-20522 > URL: https://issues.apache.org/jira/browse/AMBARI-20522 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > > If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be > upgraded as it is not versionable currently. > This task is to make Druid versionable so that we can do an upgrade from > Druid HDP-2.6.x.y to HDP-2.6.u.v -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20522) Add Stack Upgrade support for Druid components
Nishant Bangarwa created AMBARI-20522: - Summary: Add Stack Upgrade support for Druid components Key: AMBARI-20522 URL: https://issues.apache.org/jira/browse/AMBARI-20522 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be upgraded as it is not versionable currently. This task is to make Druid versionable so that we can do an upgrade from Druid HDP-2.6.x.y to HDP-2.6.u.v -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20522) Add Stack Upgrade support for Druid components
[ https://issues.apache.org/jira/browse/AMBARI-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-20522: -- Description: If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be upgraded as it is not versionable currently. This task is to make Druid versionable so that we can do an upgrade from Druid HDP-2.6.x.y to HDP-2.6.u.v was:If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be upgraded as it is not versionable currently. This task is to make Druid versionable so that we can do an upgrade from Druid HDP-2.6.x.y to HDP-2.6.u.v > Add Stack Upgrade support for Druid components > -- > > Key: AMBARI-20522 > URL: https://issues.apache.org/jira/browse/AMBARI-20522 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > > If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be > upgraded as it is not versionable currently. > This task is to make Druid versionable so that we can do an upgrade from > Druid HDP-2.6.x.y to HDP-2.6.u.v -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
[
https://issues.apache.org/jira/browse/AMBARI-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20389:
--
Status: Patch Available (was: Open)
> Druid Superset fails to Start when special characters are present in user name
> --
>
> Key: AMBARI-20389
> URL: https://issues.apache.org/jira/browse/AMBARI-20389
> Project: Ambari
> Issue Type: Bug
>Reporter: Sunitha
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20389.patch
>
>
> Install Druid using ambari with special characters in First and Last name
> collected for superset admin details
> Observed:
> Superest fails to start
> {code}
> 2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username admin --password --firstname @$#$$#% --lastname #$W%E$%E
> --email dfdf@bjfkdbv'] {'user': 'druid'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> /usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
> ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
> flask_sqlalchemy instead.
> spec.loader.load_module(spec.name)
> Error: --lastname option requires an argument
> 2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset
> > /tmp/tmpvGGiFl
> Output: druid-superset - 2.6.0.0-554
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
[
https://issues.apache.org/jira/browse/AMBARI-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20389:
--
Attachment: AMBARI-20389.patch
> Druid Superset fails to Start when special characters are present in user name
> --
>
> Key: AMBARI-20389
> URL: https://issues.apache.org/jira/browse/AMBARI-20389
> Project: Ambari
> Issue Type: Bug
>Reporter: Sunitha
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20389.patch
>
>
> Install Druid using ambari with special characters in First and Last name
> collected for superset admin details
> Observed:
> Superest fails to start
> {code}
> 2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username admin --password --firstname @$#$$#% --lastname #$W%E$%E
> --email dfdf@bjfkdbv'] {'user': 'druid'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> /usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
> ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
> flask_sqlalchemy instead.
> spec.loader.load_module(spec.name)
> Error: --lastname option requires an argument
> 2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset
> > /tmp/tmpvGGiFl
> Output: druid-superset - 2.6.0.0-554
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
[
https://issues.apache.org/jira/browse/AMBARI-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20389:
--
Fix Version/s: (was: 2.5.0)
trunk
> Druid Superset fails to Start when special characters are present in user name
> --
>
> Key: AMBARI-20389
> URL: https://issues.apache.org/jira/browse/AMBARI-20389
> Project: Ambari
> Issue Type: Bug
>Reporter: Sunitha
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk
>
>
> Install Druid using ambari with special characters in First and Last name
> collected for superset admin details
> Observed:
> Superest fails to start
> {code}
> 2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username admin --password --firstname @$#$$#% --lastname #$W%E$%E
> --email dfdf@bjfkdbv'] {'user': 'druid'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> /usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
> ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
> flask_sqlalchemy instead.
> spec.loader.load_module(spec.name)
> Error: --lastname option requires an argument
> 2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset
> > /tmp/tmpvGGiFl
> Output: druid-superset - 2.6.0.0-554
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding
[ https://issues.apache.org/jira/browse/AMBARI-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896099#comment-15896099 ] Nishant Bangarwa commented on AMBARI-20259: --- [~swapanshridhar] Please review. > Superset not able to start on Ubuntu if ASCII encoding is set as default > encoding > - > > Key: AMBARI-20259 > URL: https://issues.apache.org/jira/browse/AMBARI-20259 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-20259-1.patch, ambari-20259.patch > > > RuntimeError: Click will abort further execution because Python 3 was > configured to use ASCII as encoding for the environment. Consult > http://click.pocoo.org/python3/for mitigation steps. > This system supports the C.UTF-8 locale which is recommended. > You might be able to resolve your issue by exporting the > following environment variables: > export LC_ALL=C.UTF-8 > export LANG=C.UTF-8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding
[ https://issues.apache.org/jira/browse/AMBARI-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-20259: -- Attachment: ambari-20259-1.patch Attached second patch ambari-20259-1.patch > Superset not able to start on Ubuntu if ASCII encoding is set as default > encoding > - > > Key: AMBARI-20259 > URL: https://issues.apache.org/jira/browse/AMBARI-20259 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-20259-1.patch, ambari-20259.patch > > > RuntimeError: Click will abort further execution because Python 3 was > configured to use ASCII as encoding for the environment. Consult > http://click.pocoo.org/python3/for mitigation steps. > This system supports the C.UTF-8 locale which is recommended. > You might be able to resolve your issue by exporting the > following environment variables: > export LC_ALL=C.UTF-8 > export LANG=C.UTF-8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding
[ https://issues.apache.org/jira/browse/AMBARI-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa reopened AMBARI-20259: --- reopening as this lead to failure in centos 7 with below error - The exported locale is \"C.UTF-8\" but it is not supported. > Superset not able to start on Ubuntu if ASCII encoding is set as default > encoding > - > > Key: AMBARI-20259 > URL: https://issues.apache.org/jira/browse/AMBARI-20259 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-20259.patch > > > RuntimeError: Click will abort further execution because Python 3 was > configured to use ASCII as encoding for the environment. Consult > http://click.pocoo.org/python3/for mitigation steps. > This system supports the C.UTF-8 locale which is recommended. > You might be able to resolve your issue by exporting the > following environment variables: > export LC_ALL=C.UTF-8 > export LANG=C.UTF-8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding
[ https://issues.apache.org/jira/browse/AMBARI-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-20259: -- Status: Patch Available (was: Open) > Superset not able to start on Ubuntu if ASCII encoding is set as default > encoding > - > > Key: AMBARI-20259 > URL: https://issues.apache.org/jira/browse/AMBARI-20259 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-20259.patch > > > RuntimeError: Click will abort further execution because Python 3 was > configured to use ASCII as encoding for the environment. Consult > http://click.pocoo.org/python3/for mitigation steps. > This system supports the C.UTF-8 locale which is recommended. > You might be able to resolve your issue by exporting the > following environment variables: > export LC_ALL=C.UTF-8 > export LANG=C.UTF-8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding
[ https://issues.apache.org/jira/browse/AMBARI-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-20259: -- Attachment: ambari-20259.patch > Superset not able to start on Ubuntu if ASCII encoding is set as default > encoding > - > > Key: AMBARI-20259 > URL: https://issues.apache.org/jira/browse/AMBARI-20259 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-20259.patch > > > RuntimeError: Click will abort further execution because Python 3 was > configured to use ASCII as encoding for the environment. Consult > http://click.pocoo.org/python3/for mitigation steps. > This system supports the C.UTF-8 locale which is recommended. > You might be able to resolve your issue by exporting the > following environment variables: > export LC_ALL=C.UTF-8 > export LANG=C.UTF-8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding
Nishant Bangarwa created AMBARI-20259: - Summary: Superset not able to start on Ubuntu if ASCII encoding is set as default encoding Key: AMBARI-20259 URL: https://issues.apache.org/jira/browse/AMBARI-20259 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa Fix For: trunk, 2.5.0 RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system supports the C.UTF-8 locale which is recommended. You might be able to resolve your issue by exporting the following environment variables: export LC_ALL=C.UTF-8 export LANG=C.UTF-8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20075) Druid-Superset: Wrong router host populated in druid configs
[
https://issues.apache.org/jira/browse/AMBARI-20075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20075:
--
Status: Patch Available (was: Open)
> Druid-Superset: Wrong router host populated in druid configs
>
>
> Key: AMBARI-20075
> URL: https://issues.apache.org/jira/browse/AMBARI-20075
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20075.patch
>
>
> Druid-Superset: Wrong router host populated in druid configs
> In params.py
> {code}
> druid_router_hosts = default("/clusterHostInfo/druid_coordinator_hosts", [])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20075) Druid-Superset: Wrong router host populated in druid configs
[
https://issues.apache.org/jira/browse/AMBARI-20075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20075:
--
Attachment: ambari-20075.patch
> Druid-Superset: Wrong router host populated in druid configs
>
>
> Key: AMBARI-20075
> URL: https://issues.apache.org/jira/browse/AMBARI-20075
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20075.patch
>
>
> Druid-Superset: Wrong router host populated in druid configs
> In params.py
> {code}
> druid_router_hosts = default("/clusterHostInfo/druid_coordinator_hosts", [])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20075) Druid-Superset: Wrong router host populated in druid configs
Nishant Bangarwa created AMBARI-20075:
-
Summary: Druid-Superset: Wrong router host populated in druid
configs
Key: AMBARI-20075
URL: https://issues.apache.org/jira/browse/AMBARI-20075
Project: Ambari
Issue Type: Bug
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
Fix For: trunk, 2.5.0
Druid-Superset: Wrong router host populated in druid configs
In params.py
{code}
druid_router_hosts = default("/clusterHostInfo/druid_coordinator_hosts", [])
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20046) Fix druid metric_emitter_type when ambari-metrics-server is installed
[
https://issues.apache.org/jira/browse/AMBARI-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20046:
--
Status: Patch Available (was: Open)
> Fix druid metric_emitter_type when ambari-metrics-server is installed
> -
>
> Key: AMBARI-20046
> URL: https://issues.apache.org/jira/browse/AMBARI-20046
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Attachments: ambari-20046.patch
>
>
> In params.py for Druid -
> {code}
> metric_emitter_type = "ambari-metrics-emitter"
> {code}
> should be spelled correctly as
> {code}
> metric_emitter_type = "ambari-metrics"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20046) Fix druid metric_emitter_type when ambari-metrics-server is installed
[
https://issues.apache.org/jira/browse/AMBARI-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20046:
--
Attachment: ambari-20046.patch
> Fix druid metric_emitter_type when ambari-metrics-server is installed
> -
>
> Key: AMBARI-20046
> URL: https://issues.apache.org/jira/browse/AMBARI-20046
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Attachments: ambari-20046.patch
>
>
> In params.py for Druid -
> {code}
> metric_emitter_type = "ambari-metrics-emitter"
> {code}
> should be spelled correctly as
> {code}
> metric_emitter_type = "ambari-metrics"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20046) Fix druid metric_emitter_type when ambari-metrics-server is installed
Nishant Bangarwa created AMBARI-20046:
-
Summary: Fix druid metric_emitter_type when ambari-metrics-server
is installed
Key: AMBARI-20046
URL: https://issues.apache.org/jira/browse/AMBARI-20046
Project: Ambari
Issue Type: Bug
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
In params.py for Druid -
{code}
metric_emitter_type = "ambari-metrics-emitter"
{code}
should be spelled correctly as
{code}
metric_emitter_type = "ambari-metrics"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20037) Druid-superset install fails with ambari running on python 2.6.6
[
https://issues.apache.org/jira/browse/AMBARI-20037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20037:
--
Fix Version/s: 2.5.0
trunk
Status: Patch Available (was: In Progress)
> Druid-superset install fails with ambari running on python 2.6.6
>
>
> Key: AMBARI-20037
> URL: https://issues.apache.org/jira/browse/AMBARI-20037
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20037.patch
>
>
> StackTrace -
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 153, in
> Superset().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 91, in start
> self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 116, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 71, in configure
> properties=quote_string_values(superset_config),
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 141, in quote_string_values
> rv[key] = quote_string_value(value)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 148, in quote_string_value
> return "'{}'".format(value)
> ValueError: zero length field name in format
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20037) Druid-superset install fails with ambari running on python 2.6.6
[
https://issues.apache.org/jira/browse/AMBARI-20037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-20037:
--
Attachment: ambari-20037.patch
> Druid-superset install fails with ambari running on python 2.6.6
>
>
> Key: AMBARI-20037
> URL: https://issues.apache.org/jira/browse/AMBARI-20037
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Attachments: ambari-20037.patch
>
>
> StackTrace -
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 153, in
> Superset().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 91, in start
> self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 116, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 71, in configure
> properties=quote_string_values(superset_config),
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 141, in quote_string_values
> rv[key] = quote_string_value(value)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 148, in quote_string_value
> return "'{}'".format(value)
> ValueError: zero length field name in format
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20037) Druid-superset install fails with ambari running on python 2.6.6
[
https://issues.apache.org/jira/browse/AMBARI-20037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869492#comment-15869492
]
Nishant Bangarwa commented on AMBARI-20037:
---
Note this only affects installation when python version is 2.6 or prev
> Druid-superset install fails with ambari running on python 2.6.6
>
>
> Key: AMBARI-20037
> URL: https://issues.apache.org/jira/browse/AMBARI-20037
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>
> StackTrace -
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 153, in
> Superset().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 91, in start
> self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 116, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 71, in configure
> properties=quote_string_values(superset_config),
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 141, in quote_string_values
> rv[key] = quote_string_value(value)
> File
> "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
> line 148, in quote_string_value
> return "'{}'".format(value)
> ValueError: zero length field name in format
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20037) Druid-superset install fails with ambari running on python 2.6.6
Nishant Bangarwa created AMBARI-20037:
-
Summary: Druid-superset install fails with ambari running on
python 2.6.6
Key: AMBARI-20037
URL: https://issues.apache.org/jira/browse/AMBARI-20037
Project: Ambari
Issue Type: Bug
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
StackTrace -
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
line 153, in
Superset().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
line 91, in start
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 116, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
line 71, in configure
properties=quote_string_values(superset_config),
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
line 141, in quote_string_values
rv[key] = quote_string_value(value)
File
"/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py",
line 148, in quote_string_value
return "'{}'".format(value)
ValueError: zero length field name in format
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-19965:
--
Status: Patch Available (was: Open)
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-19965:
--
Description:
When enabling kerberos following properties are not set for druid-superset -
{code}
"ENABLE_KERBEROS_AUTHENTICATION": "True",
"KERBEROS_REINIT_TIME_SEC": "3600"
{code}
Found that they are specified at wrong level in the kerberos.json file for
Druid.
was:
When enabling kerberos following properties are not set for druid-superset -
{code}}
"ENABLE_KERBEROS_AUTHENTICATION": "True",
"KERBEROS_REINIT_TIME_SEC": "3600"
{code}
Found that they are specified at wrong level in the kerberos.json file for
Druid.
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-19965:
--
Attachment: ambari-19965.patch
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-19966) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa resolved AMBARI-19966.
---
Resolution: Duplicate
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19966
> URL: https://issues.apache.org/jira/browse/AMBARI-19966
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
