Cloudera Spark2 Installation - cloudera

I'm trying to install Spark2 in my cloudera cluster (evaluation version) following the cloudera's instructions to install this component. I downloaded the CSD, installed it and using the parcel downloaded the component, distribute it but when I try to activate it I'm having this message:
CDH (5.8 and higher) parcel required for SPARK2
(2.2.0.cloudera1-1.cdh5.12.0.p0.142354) is not available.
This is the information of the cluster:
Version: Cloudera Enterprise Data Hub Edition Trial 5.12.1 (#6 built
by jenkins on 20170818-0807 git:
9bdee611802535491d400e03c98ef694a2c77d0a)
Java VM Name: Java HotSpot(TM) 64-Bit Server VM
Java VM Vendor: Oracle Corporation
Java Version: 1.7.0_67
CSD
SPARK2_ON_YARN-2.2.0.cloudera1.jar
Parcel
http://archive.cloudera.com/spark2/parcels/2.2.0.cloudera1/
I'm thinking it could be because my CDH version (5.12.1) and the version of the last spark2 parcel (cdh5.12.0) but I don't find any other package for cdh5.12.1 and my next question is: for cdh5.13.0 which is the spark2 parcel?

The error message is misleading. The real issue is that your cluster is running on Java 1.7. Spark 2.2 is only supported on Java 1.8. Upgrade Java on your cluster and you should be able to install the Spark 2.2 parcel.

Finally solved. The problem was that I need to update de cdh core, after update, spark 2 just works fine.

Related

Installing nexus error: The version of the JVM must be at least 1.8 and at most 1.8

I have installed Nexus on Ubuntu 18.04 LTS. When I want to start Nexus service I get this error:
nexus[24049]: No suitable Java Virtual Machine could be found on your system.
nexus[24049]: The version of the JVM must be at least 1.8 and at most 1.8.
nexus[24049]: Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
systemd[1]: nexus.service: Control process exited, code=exited status=83
systemd[1]: nexus.service: Failed with result 'exit-code'.
systemd[1]: Failed to start LSB: nexus.
I have Open JDK version 10.0.2 installed in my system:
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4, mixed mode)
My question is why Nexus uses ONLY JDK8? and am I able to have both JDK versions alongside?
INSTALL4J_JAVA_HOME is not an environment variable setting. It is configured in the nexus installation directory. You'll need to edit "/bin/nexus" file.
You'll find near the top of that configuration script a commented out line:
# INSTALL4J_JAVA_HOME_OVERRIDE=
remove the comment tag and set the value to your jdk location. I set mine to a java 1.8 jdk that I installed. (Not the JDK 11.0.4 default dir that some linux installations are prepackaged with. I read somewhere that you must use the Java 1.8 with nexus version 3.x and that other versions will fail. I don't know the truth to that claim, you certainly can try other version to see if they work.)
After doing that, the nexus service was able to start.
I still haven't been able to get access to the nexus manager through a browser via port 8082. I'm just now trying to track that issue down. Probably a configuration issue or something else I need to set up.

Nexus Repo Migration and updating.

Trying to upgrade Nexus 2.1.4 Repo to 3.X. This is what i have done till now and what what went wrong!
-- installed the 3.0.2 version on the same machine in a different port (8090) Then opened the UI and tried doing the upgrade agent and there was no upgrade agent in 3.0.2.
-- so i installed 3.1 on the different port and came across a java exception error in nexus Repo UI while migrating stuff from 2.1.4 (installed on port 80). I found out that one need to be at-least on 3.2.4 V to migrate.
-- now i installed 3.6 on a different port (8082)in the same machine. couldn't start nexus service now. which i was able to for other nexus version in other ports.

CDH Installation Issues On Centos 7.3

I have created Virtual Machine using Hyper V manager and wanted to install cloudera 5.11 on the VM.
I followed the steps mentioned in cloudera website.But whenever I check the status of cloudera-scm-server its active in exited state.
Can someone help me out to resolve with this issue ?

upgrading cloudera manager from cdh 5.4.9 to 5.6.0

when i'm trying to upgrade cloudera manager via CM parcel page (at: http://hostname:7180/cmf/parcel/status) i get the flowing errors:
Local parcel error for parcel CDH-5.6.0-1.cdh5.6.0.p0.45-el6.parcel : The version 5.6.0-1.cdh5.6.0.p0.45 is too new to be supported. Please upgrade Cloudera Manager to at least 5.6.0 before using this parcel..
when trying to activate the parcel i get the following error:
The new version of CDH: '5.6.0-1.cdh5.6.0.p0.45' is newer than the running Cloudera Manager version: '5.4.8'.
how can i fix that?
It seems your cloudera manager is older version. So first update your manager then try to upgrade your cluster. Refer below link for more details
http://www.cloudera.com/documentation/enterprise/latest/topics/install_upgrade_to_cdh56.html

Configuring Cloudera Connector for MicroStrategy

I have installed ClouderaHiveODBCSetup_v2_00 on my windows XP and I am following instructions as per the following page
https://ccp.cloudera.com/display/con/Cloudera+Connector+for+Tableau
I am get the following error
the setup routine for the cloudera ODBC driver for APACHE hive ODBC driver could not be loaded due to system error code 127
What could be the problem . I have tried with all privileges as an admin
Thanks
Cloudera had updated the Hive ODBC driver. Have you try their latest version of the driver? The latest version runs fine on XP.
Here is the download link:
http://www.cloudera.com/content/support/en/downloads/download-components/download-products/downloads-listing/connectors/cloudera-odbc-drivers.html

Resources