[jira] [Commented] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
[ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754916#comment-17754916 ] D M Murali Krishna Reddy commented on AMBARI-25950: --- [~vjasani] I just checked on the 2.6 based cluster and was not able to reproduce this issue. Looks this issue is induced by AMBARI-23493 Can you review the changes on the PR? Thanks > Exclude hosts getting erased when RM, NN are restarted > -- > > Key: AMBARI-25950 > URL: https://issues.apache.org/jira/browse/AMBARI-25950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > After decommissioning a Node Manager or a Data node, if Resource Manager or > Namenode are restarted, the exclude hosts file is getting overwritten with > empty contents, causing the NM, DN to get recommisioned. > > During NN, RM restart all_decommissioned_hosts is not set due to which in > params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25982) Fix incorrect description of yarn.timeline-service.enabled in tez-site.xml
D M Murali Krishna Reddy created AMBARI-25982: - Summary: Fix incorrect description of yarn.timeline-service.enabled in tez-site.xml Key: AMBARI-25982 URL: https://issues.apache.org/jira/browse/AMBARI-25982 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: trunk, 2.8.0 Reporter: D M Murali Krishna Reddy Assignee: D M Murali Krishna Reddy Update description of yarn.timeline-service.enabled in tez-site.xml of BIGTOP stack - 3.2.0 to "Indicate to clients whether timeline service is enabled or not. If enabled, clients will put entities and events to the timeline server." When we hover on the text-box of the above config on ambari-server TEZ configs misleading description is shown. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737436#comment-17737436 ] D M Murali Krishna Reddy commented on AMBARI-25956: --- [~jonathanhurley], [~srimanth] Can you have a look on this? [~vjasani], [~yaolei], [~houyu] Can you review the changes, and see if you have faced this issue during upgrades. For 2.6 stack upgrades the HS2's get shutdown but on the UI they still show green and an alert is displayed saying unable to connect to HS2, For 3.1 stack upgrades the HS2's are shown as stopped on UI post upgrade. > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736192#comment-17736192 ] D M Murali Krishna Reddy commented on AMBARI-25956: --- I too have observed this behaviour during rolling, express upgrades. Once the upgrade is completed I can see only one hiveserver2 running. On Checking the upgrade logs I can see that during restarting HiveServer2, deregister is being executed with the target version of upgrade. Due to this the HiveServer2 which restarts currently is stopping the HiveServer's that have restarted earlier. I feel the change done in hive_server_upgrade.py from https://issues.apache.org/jira/browse/AMBARI-21722 has induced this issue of deregistering target version instead of source version. As, In few earlier tickets AMBARI-12195 , AMBARI-12280 It's mentioned that expected behaviour is deregistering source version. > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Assigned] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] D M Murali Krishna Reddy reassigned AMBARI-25956: - Assignee: D M Murali Krishna Reddy > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
[ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732212#comment-17732212 ] D M Murali Krishna Reddy commented on AMBARI-25950: --- I have two working approaches # Just before sending the ExecutionCommand to agents update CommandParams for all_decommisioned_hosts in AgentsCommandPublisher#populateExecutionCommandsClusters using the AmbariCustomCommandExecutionHelper#calculateDecommissionedNodes based on the executionCommand Role(RM or NN) # Update CommandParams for all_decommisioned_hosts in a similar way as above ## For Custom Commands update CommandParams in AmbariCustomCommandExecutionHelper#addExecutionCommandsToStage, only for valid custom commands(except for service check and decommission commands) ## In AmbariManagementControllerImpl#createHostAction just before setting the commandParams for the executionCommand. [~brahmareddy], [~vjasani] , [~vishalsuvagia] [~eub] Can you suggest which approach to choose, I am inclined to approach 2 as the commandParams get added to stages. > Exclude hosts getting erased when RM, NN are restarted > -- > > Key: AMBARI-25950 > URL: https://issues.apache.org/jira/browse/AMBARI-25950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > > After decommissioning a Node Manager or a Data node, if Resource Manager or > Namenode are restarted, the exclude hosts file is getting overwritten with > empty contents, causing the NM, DN to get recommisioned. > > During NN, RM restart all_decommissioned_hosts is not set due to which in > params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
D M Murali Krishna Reddy created AMBARI-25950: - Summary: Exclude hosts getting erased when RM, NN are restarted Key: AMBARI-25950 URL: https://issues.apache.org/jira/browse/AMBARI-25950 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: D M Murali Krishna Reddy Assignee: D M Murali Krishna Reddy After decommissioning a Node Manager or a Data node, if Resource Manager or Namenode are restarted, the exclude hosts file is getting overwritten with empty contents, causing the NM, DN to get recommisioned. During NN, RM restart all_decommissioned_hosts is not set due to which in params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Assigned] (AMBARI-25827) Not able to tune the config 'hbase.regionserver.global.memstore.size' from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] D M Murali Krishna Reddy reassigned AMBARI-25827: - Assignee: D M Murali Krishna Reddy > Not able to tune the config 'hbase.regionserver.global.memstore.size' from > Ambari > - > > Key: AMBARI-25827 > URL: https://issues.apache.org/jira/browse/AMBARI-25827 > Project: Ambari > Issue Type: Bug >Reporter: Anoop Sam John >Assignee: D M Murali Krishna Reddy >Priority: Major > > In old Ambari versions, in HBase config area, there is a slider to change > this config (Write buffer cache) along with the slider for changing read > cache %. > We have noticed issue in 2.7.3 > I checked master branch and there also issue seems to be there. > In > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/HBASE/themes/theme.json, > there is a configuration-layout placement and this config entry is missing > there. > As this is a default added/considered config by Ambari , we wont be able to > set/change this value using the Custom configs pane as well. > So always end up using default 40% what HBase internally having -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25884) Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
[
https://issues.apache.org/jira/browse/AMBARI-25884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716731#comment-17716731
]
D M Murali Krishna Reddy commented on AMBARI-25884:
---
Apologies for delayed response, I have raised PR against branch-2.7
> Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
> -
>
> Key: AMBARI-25884
> URL: https://issues.apache.org/jira/browse/AMBARI-25884
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: D M Murali Krishna Reddy
>Assignee: D M Murali Krishna Reddy
>Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> On large clusters while enabling kerberos or on running kerberos service
> check, NPE is thrown on for CHECK_KEYTABS, REMOVE_KEYTAB, SET_KEYTAB
>
> {code:java}
> 2023-03-06 07:22:00,538 INFO [agent-command-publisher-0]
> AgentCommandsPublisher:174 - CHECK_KEYTABS called
> 2023-03-06 07:22:00,538 ERROR [ambari-action-scheduler]
> AgentCommandsPublisher:126 - Exception on sendAgentCommand
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.sendAgentCommand(AgentCommandsPublisher.java:124)
> at
> org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:555)
> at
> org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:347)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
> ... 4 more
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at
> java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
> at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$sendAgentCommand$1(AgentCommandsPublisher.java:103)
> at
> java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> at
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:163)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.prepareExecutionCommandsClusters(AgentCommandsPublisher.java:214)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.populateExecutionCommandsClusters(AgentCommandsPublisher.java:192)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:122)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
> at
>
[jira] [Commented] (AMBARI-25884) Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
[
https://issues.apache.org/jira/browse/AMBARI-25884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700819#comment-17700819
]
D M Murali Krishna Reddy commented on AMBARI-25884:
---
Yes, we have AMBARI-25719 on top of the ambari-2.7.6 codebase.
> Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
> -
>
> Key: AMBARI-25884
> URL: https://issues.apache.org/jira/browse/AMBARI-25884
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: D M Murali Krishna Reddy
>Assignee: D M Murali Krishna Reddy
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On large clusters while enabling kerberos or on running kerberos service
> check, NPE is thrown on for CHECK_KEYTABS, REMOVE_KEYTAB, SET_KEYTAB
>
> {code:java}
> 2023-03-06 07:22:00,538 INFO [agent-command-publisher-0]
> AgentCommandsPublisher:174 - CHECK_KEYTABS called
> 2023-03-06 07:22:00,538 ERROR [ambari-action-scheduler]
> AgentCommandsPublisher:126 - Exception on sendAgentCommand
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.sendAgentCommand(AgentCommandsPublisher.java:124)
> at
> org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:555)
> at
> org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:347)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
> ... 4 more
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at
> java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
> at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$sendAgentCommand$1(AgentCommandsPublisher.java:103)
> at
> java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> at
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:163)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.prepareExecutionCommandsClusters(AgentCommandsPublisher.java:214)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.populateExecutionCommandsClusters(AgentCommandsPublisher.java:192)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:122)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
> at
>
[jira] [Updated] (AMBARI-25884) Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
[
https://issues.apache.org/jira/browse/AMBARI-25884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
D M Murali Krishna Reddy updated AMBARI-25884:
--
Description:
On large clusters while enabling kerberos or on running kerberos service check,
NPE is thrown on for CHECK_KEYTABS, REMOVE_KEYTAB, SET_KEYTAB
{code:java}
2023-03-06 07:22:00,538 INFO [agent-command-publisher-0]
AgentCommandsPublisher:174 - CHECK_KEYTABS called
2023-03-06 07:22:00,538 ERROR [ambari-action-scheduler]
AgentCommandsPublisher:126 - Exception on sendAgentCommand
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.sendAgentCommand(AgentCommandsPublisher.java:124)
at
org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:555)
at
org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:347)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
... 4 more
Caused by: java.lang.NullPointerException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
at
java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
at
java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$sendAgentCommand$1(AgentCommandsPublisher.java:103)
at
java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at
java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at
java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:163)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.prepareExecutionCommandsClusters(AgentCommandsPublisher.java:214)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.populateExecutionCommandsClusters(AgentCommandsPublisher.java:192)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:122)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
at
com.google.common.collect.CollectSpliterators$1.forEachRemaining(CollectSpliterators.java:116)
at
com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.lambda$forEachRemaining$1(CollectSpliterators.java:247)
at
java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1699)
at
com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.forEachRemaining(CollectSpliterators.java:247)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
... 4 more {code}
This might be due to the using the Treemap for executionCommandsClusters
multithreading operations, so we need to
[jira] [Commented] (AMBARI-25884) Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
[
https://issues.apache.org/jira/browse/AMBARI-25884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697546#comment-17697546
]
D M Murali Krishna Reddy commented on AMBARI-25884:
---
[~brahmareddy] , I would like to work on this issue, can you add me as a
contributor.
Thanks
> Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
> -
>
> Key: AMBARI-25884
> URL: https://issues.apache.org/jira/browse/AMBARI-25884
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: D M Murali Krishna Reddy
>Priority: Major
>
> On large clusters while enabling kerberos or on running kerberos service
> check, NPE is thrown on for CHECK_KEYTABS, REMOVE_KEYTAB, SET_KEYTAB
>
> {code:java}
> 2023-03-06 07:22:00,538 INFO [agent-command-publisher-0]
> AgentCommandsPublisher:174 - CHECK_KEYTABS called
> 2023-03-06 07:22:00,538 ERROR [ambari-action-scheduler]
> AgentCommandsPublisher:126 - Exception on sendAgentCommand
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.sendAgentCommand(AgentCommandsPublisher.java:124)
> at
> org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:555)
> at
> org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:347)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
> ... 4 more
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at
> java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
> at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$sendAgentCommand$1(AgentCommandsPublisher.java:103)
> at
> java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> at
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:163)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.prepareExecutionCommandsClusters(AgentCommandsPublisher.java:214)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.populateExecutionCommandsClusters(AgentCommandsPublisher.java:192)
> at
> org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:122)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
> at
> com.google.common.collect.CollectSpliterators$1.forEachRemaining(CollectSpliterators.java:116)
> at
>
[jira] [Created] (AMBARI-25884) Set Keytab, Check keytab and Remove Keytab operations failing on few clusters
D M Murali Krishna Reddy created AMBARI-25884:
-
Summary: Set Keytab, Check keytab and Remove Keytab operations
failing on few clusters
Key: AMBARI-25884
URL: https://issues.apache.org/jira/browse/AMBARI-25884
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.6
Reporter: D M Murali Krishna Reddy
On large clusters while enabling kerberos or on running kerberos service check,
NPE is thrown on for CHECK_KEYTABS, REMOVE_KEYTAB, SET_KEYTAB
{code:java}
2023-03-06 07:22:00,538 INFO [agent-command-publisher-0]
AgentCommandsPublisher:174 - CHECK_KEYTABS called
2023-03-06 07:22:00,538 ERROR [ambari-action-scheduler]
AgentCommandsPublisher:126 - Exception on sendAgentCommand
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.sendAgentCommand(AgentCommandsPublisher.java:124)
at
org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:555)
at
org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:347)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
... 4 more
Caused by: java.lang.NullPointerException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
at
java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
at
java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$sendAgentCommand$1(AgentCommandsPublisher.java:103)
at
java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at
java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at
java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:163)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.prepareExecutionCommandsClusters(AgentCommandsPublisher.java:214)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.populateExecutionCommandsClusters(AgentCommandsPublisher.java:192)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:122)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
at
com.google.common.collect.CollectSpliterators$1.forEachRemaining(CollectSpliterators.java:116)
at
com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.lambda$forEachRemaining$1(CollectSpliterators.java:247)
at
java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1699)
at
com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.forEachRemaining(CollectSpliterators.java:247)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
at
