Member since
08-28-2015
194
Posts
45
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4102 | 07-05-2017 11:58 PM |
11-15-2019
05:17 AM
Can you more elaborate on "Hostname tied to the actual IP address?" and "Use "ifconfig -a" to see a listing of your network interfaces and choose one that has an actual IP address." How do I know which hostname and ip address to use. Because while installing single node cluster of cloudera how would you know which hosts to specify? Thank you!
... View more
01-14-2019
10:23 PM
Very well explained, thanks for the post~
... View more
02-14-2018
12:37 AM
try add allow port on firewalld on host, this solved my prob $ firewall-cmd --zone=public --add-port=9000/tcp (Centos7) or $ service firewalld disable Hope this may help
... View more
10-19-2017
02:24 AM
in /etc/hosts for all nodes: put ip_adress FQDN DN 10.10.1.230 name.domain.com name the FQDN must be before the name
... View more
09-28-2017
03:02 PM
Thank you so much.
... View more
08-03-2017
02:22 PM
yes, thank you, all working. I missed ';' at end of update statement. thanks again.
... View more
07-07-2017
04:34 AM
Hi, Can u reset the ambari-agent in all servers and try to register. amabri-agent reset <Ambari_host_name>
... View more
07-04-2017
04:15 AM
@Robin Dong
You can check the "/etc/ambari-server/conf/ambari.properties" file to know exactly which DataBase your ambari is using and then accordingly you can login to the DB host and run/check the requested commands or the DB admin can assist with the queries. Example: (In my Case it is Postgres)
# grep 'jdbc' /etc/ambari-server/conf/ambari.properties
custom.postgres.jdbc.name=postgresql-9.3-1101-jdbc4.jar
previous.custom.postgres.jdbc.name=postgresql-9.3-1101-jdbc4.jar
server.jdbc.connection-pool=internal
server.jdbc.database=postgres
server.jdbc.database_name=ambari
server.jdbc.postgres.schema=ambari
server.jdbc.user.name=ambari
server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat
.
... View more
04-23-2018
02:05 PM
1 Kudo
I know this is an old post, but maybe it can still be usefull to someone. To start the standalone you need to pass both the worker config (connect-standalone.properties) and the connectors configurations (mongo_connector_config.properties in Robin's case). For someone with the same problem, bare in mind that for starting the standalone connector you need to pass ".properties" files. To update or add new connectors you would need to pass ".json" files. You can see in the confluent documentation page here. bin/connect-standalone worker.properties connector1.properties [connector2.properties connector3.properties ...] Vicente
... View more
06-09-2017
02:18 AM
thank you so much. even I need more time to digest it, I can tell this is what I need to know. thank you for spending time to help. Robin
... View more