Member since
12-20-2015
5
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
18795 | 03-10-2017 01:00 AM |
03-10-2017
01:00 AM
Worked after increaing the Java Heap size of name node Name node process was exiting while loading the inodes. Since my last restart, I had created a lot of files on hdfs which lead to significant increase in inodes. But since my java heap size was not comaprable to that so JVM was pausing.
... View more
03-07-2017
04:05 AM
Name node process is crashing few moments after restarting with the following exception 2017-03-07 11:54:15,997 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1013ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=1445ms 2017-03-07 11:54:17,877 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1229ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=1409ms 2017-03-07 11:54:19,913 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1535ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=1870ms 2017-03-07 11:54:23,297 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1266ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=1658ms 2017-03-07 11:54:26,528 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1382ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=1861ms 2017-03-07 11:54:29,996 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1345ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=1837ms 2017-03-07 11:54:34,016 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 1142ms GC pool 'ConcurrentMarkSweep' had collection(s): count=2 time=1640ms A few days back, the machine got shut down forcefully due to power failure. getting this issue after that. Please suggest or let me know if any further details are required.
... View more
Labels:
- Labels:
-
HDFS
10-20-2016
09:27 AM
you can follow following page : http://bigdatafan.blogspot.in/2016/05/upgrade-java-to-jdk-8-on-cloudera-cdh.html additionally, update the symbolic link that from which java runs. For my cluster it was /usr/bin/java which I got from which java. You can remove the same and create a new link from the location where you will place new java version
... View more
10-19-2016
04:07 AM
Downgrade the java. I did it to 1.8.0_60 and it worked for me
... View more
09-28-2016
02:50 AM
I have installed Cloudera Enterprise Data Hub Edition Trial 5.5.1 recently. After this I am getting following error while opening oozie web console : type Exception report message Unable to compile class for JSP: description The server encountered an internal error that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 1 in the generated java file
The type java.io.ObjectInputStream cannot be resolved. It is indirectly referenced from required .class files
Stacktrace:
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:460)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:356)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:321)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:589)
org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:552)
org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.44 logs. After googling a bit, I found out that it is coming after java8-upg 91. I have java8 upg-101 installed on my machine which came by default with this version of cloudera.
... View more
Labels: