Member since
03-04-2019
11
Posts
0
Kudos Received
0
Solutions
11-10-2019
05:27 PM
I had to install Java 8 and set JAVA_HOME to this
... View more
06-18-2019
05:58 PM
Hi Istvan, I had managed to carry out the changes successfully. Am grateful for your assistance.
... View more
05-28-2019
02:57 AM
Hi Istvan, Thank you for your reply and apologies for the delay. I have carried out the changes you adviced, including changing the following: Solr HTTP Port (default 8983) to 8986 Solr Admin Port (default 8984) to 8987 Solr HTTPs Port (default 8985) to 8988 ZK Client Port (default 2181) to 2182 Quorum Port (default 3181) to 3182 Election Port (default 4181) to 4182 JMX Remote Port (default 9010) to 9011 I then started Cloudera becuase it was not running since I shut it down months prior. Everything worked normally. The Banana dahsboard I mentioned earlier worked fine, indicating that there is no conflict with Cloudera Search, as had happened much earlier. However, in trying to create a collection in Cloudera Search as a means of testing my installation, I ran into the solr-env.sh file, where SOLR_ZK_ENSEMBLE still points to port 2181. Since you had stated that Cloudera Manager would update the affected client configurations on starting /restarting, I am at a loss as to how this could be. Should I change these configurations manually? If so, what should I change, and what is the process for this? Thank you
... View more
05-09-2019
07:28 PM
I have completed the installation of CDH 5.16.1 on Ubuntu 16.04 LTS with OpenJDK 8.
My employer has developed a UI using Banana (currently packaged with Fusion) that I am required to run on a VM hosted in my machine. The Banana UI needs Solr both to operate and to store data collections that can be visualised. In this case, the Solr instance within the VM uses ports 8983 and 7574. The Banana UI also has a unique security feature developed by my employer (which I have to familirise myself with) that does not yet allow me to host the entire contents of the VM on my server which also hosts the Cloudera CDH instance.
Due to the above arrangement, it is not possible for me to startup Cloudera CDH (though Cloudera Manager is still running). This has proven to be a difficulty since I need to use Solr and also use the various tools (Spark etc).
Could you tell me how I could change the default port for Cloudera Solr (from 8983 to an appropriate port) and for Cloudera Zookeeper (from 2181 to an appropriate port)? I hma not very familiar with the layout or intricacies of the Cloudera Manager on CDH 5.16.1. Thank you.
... View more
Labels:
05-09-2019
06:47 PM
My apologies for the delay. I was occupied with an urgent, unrelated project. I have used your advice and Sqoop works fine now. Thank you.
... View more
03-10-2019
09:10 PM
I run a PC with Ubuntu 16.04 LTS. I have installed CDH 5.16.1 (installation by parcels) and had accidentally allowed it to install Oracle Java 7 into my default Java directory (/usr/lib/jvm). Prior to my CDH installation I had installed OpenJDK 8 on my PC in the same location.
I then downloaded the JDBC for Postgresql for Java 8 and higher postgresql-42.2.5.jar and placed it in the recommended directory (/var/lib/sqoop).
In attempting to connect to my database and list the tables present, I got the following error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:190) at org.apache.sqoop.manager.SqlManager.makeConnection(SqlManager.java:872) at org.apache.sqoop.manager.GenericJdbcManager.getConnection(GenericJdbcManager.java:52) at org.apache.sqoop.manager.CatalogQueryManager.listTables(CatalogQueryManager.java:102) at org.apache.sqoop.tool.ListTablesTool.run(ListTablesTool.java:49) at org.apache.sqoop.Sqoop.run(Sqoop.java:147) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:183) at org.apache.sqoop.Sqoop.runTool(Sqoop.java:234) at org.apache.sqoop.Sqoop.runTool(Sqoop.java:243) at org.apache.sqoop.Sqoop.main(Sqoop.java:252)
I understand that it points to a conflict in the JDK versions that are present in my PC. I then replaced the JDBC with postgresql-42.2.5.jre7.jar but still received the same error.
I then changed the Java Home Directory on Cloudera Manager to that of my OpenJDK 8, followed up with replacing the JDBC once again with postgresql-42.2.5.jar in the same location, but the error remains.
I have checked if it were possible that the error may be with Sqoop, and have removed the JDBC driver from /var/lib/sqoop, but I receive the same error.
Please help.
... View more
Labels:
- Labels:
-
Apache Sqoop
-
Cloudera Manager