About vpoornalingam

vpoornalingam · ‎03-10-2016

@Harshal Joshi How many nodes are in the cluster? Is it a sandbox? Please check if the ambari-agent is indeed coming up. Compare /var/run/ambari-agent/ambari-agent.pid with the process running. Take a look at this article.

vpoornalingam · ‎03-09-2016

@seungho han The nodes can have multiple IP addresses and that is alright. But the configurations used should be correctly setup and its better to use the same series of IP addresses. If the cluster is setup with Ambari and the FQDN's are correctly specified and if the FQDN's resolve to expected IP address, then you would not face a problem with configurations. If this is a manual installation, then please ensure that all the associated configuration files [hbase / zookeeper / hdfs] all point to correct IP addresses.

vpoornalingam · ‎03-08-2016

@Ram D Once accepted, did it start a job in the Ambari Ops? Please check for any errors in the Ambari Opts listing for this job. Also tail ambari-server.log for this period and observe if any error is reported related to this curl command.

vpoornalingam · ‎03-08-2016

@CS User We seem to be off for node ambdevtestdc2host-group-51.node.example. Please check hosts / hoststate and other hosts table for this node and look for discrepancy. It is possible one of the prior API calls to delete / add nodes might have messed up the db.

vpoornalingam · ‎03-08-2016

@Mark Petronic Thanks for the feedback. I would check this and get it fixed as appropriate.

vpoornalingam · ‎03-08-2016

@Gonzalo Herreros Yes - for now, it has to be done manually. You could list all the packages for a given repo [older repo] and remove them manually in all the nodes. Typically the folders are well demarcated and hence chances of losing a current version file is rare. May be you could post this in 'Post idea' section.

vpoornalingam · ‎03-07-2016

Also, many times the terminal's stty erase isn't good for the curl commands, and hence a backspace etc introduces unexpected characters for curl. I would recommend typing it in a notepad like application and then copy paste the whole line.

vpoornalingam · ‎03-07-2016

@Mark Petronic Step 15 isn't a configuration setting script. It is the step to update HiveMetastore with the NameService URI. Hence it's not expected to change when the services are restarted using Ambari. If it already lists the correct NameService URI, there is no need to re-run this command.

vpoornalingam · ‎03-07-2016

@Ali Gouta Yes it isn't possible to do this directly. But you could use Ambari API to check the current status of services in a given node and restart them if required using the API's.

vpoornalingam · ‎03-05-2016

@wayne2chicago There is no need to shutdown the DB related services. The jar's are used only by the Client services like Ambari or Hive. You might have to restart Ambari / Hive or anything that uses the Oracle 12c database.

Online	Offline
Last Visited	‎06-24-2019 04:30 PM

Member Since	‎09-29-2015 12:30 PM
Last Visited	‎06-24-2019 04:30 PM
Posts	140
Kudos received	87

Cloudera Community

Re: Changing zookeeper client port in Ambari is no...

Re: How does ambari display service state

Re: How can I change the AMS hbase.rootdir in embe...

Re: While trying to start Hbase getting the follow...

Re: error ambari-action-scheduler

Re: HeartBeat Lost loss for all services

Re: Is it the correct configuration for hosts with...

Re: I tried to stop Node manager through REST API,...

Re: Ambari - error 500 - getAllRequests after upgr...

Re: How to configure namenode high availability

Re: How to remove an old HDP version

Re: I am getting error when i use the curl command...

Re: How to configure namenode high availability

Re: Restarting Components/services after rebooting...

Re: Oracle 12c upgrade steps using Ambari 2.1.2.1