Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Jaql Users
Home
+ new post
About this group
Join this group
RuntimeException: Inconsistent state
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jonathan Herzig  
View profile  
 More options Apr 6 2011, 3:45 am
From: Jonathan Herzig <jher...@gmail.com>
Date: Wed, 6 Apr 2011 00:45:18 -0700 (PDT)
Local: Wed, Apr 6 2011 3:45 am
Subject: RuntimeException: Inconsistent state
Print | Individual message | Show original | Report this message | Find messages by this author
Hi, i keep getting these kind of exceptions when i'm running a jaql
script. My setup is a 5 machine cluster. The output data seems to be
created, although i can't say if it's valid.

What is the source of this exception? Does it affect the success of
map/reduce tasks?

Thanks,
Jonathan

The exception:

java.lang.RuntimeException: Inconsistent state!!! JVM Manager reached
an unstable state while reaping a JVM for task:
attempt_201104040919_0010_m_000078_0 Number of active JVMs:16
  JVMId jvm_201104040919_0010_m_-1251807990 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000073_0
  JVMId jvm_201104040919_0010_m_610431499 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000079_0
  JVMId jvm_201104040919_0010_m_-1304554900 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000069_0
  JVMId jvm_201104040919_0010_m_-1041527252 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000070_0
  JVMId jvm_201104040919_0010_m_1189860270 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000071_0
  JVMId jvm_201104040919_0010_m_2121084436 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000066_0
  JVMId jvm_201104040919_0010_m_127073814 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000077_0
  JVMId jvm_201104040919_0010_m_-735738118 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000074_0
  JVMId jvm_201104040919_0010_m_919925725 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000067_0
  JVMId jvm_201104040919_0010_m_-1410481599 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000072_0
  JVMId jvm_201104040919_0009_m_293172846 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0009_m_000641_0
  JVMId jvm_201104040919_0010_m_-530484892 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000076_0
  JVMId jvm_201104040919_0010_m_-2129997690 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000064_0
  JVMId jvm_201104040919_0010_m_-1487849752 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000075_0
  JVMId jvm_201104040919_0010_m_335014281 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000068_0
  JVMId jvm_201104040919_0010_m_1308298857 #Tasks ran: 0 Currently
busy? true Currently running: attempt_201104040919_0010_m_000065_0
        at org.apache.hadoop.mapred.JvmManager
$JvmManagerForType.reapJvm(JvmManager.java:253)
        at org.apache.hadoop.mapred.JvmManager$JvmManagerForType.access
$000(JvmManager.java:111)
        at
org.apache.hadoop.mapred.JvmManager.launchJvm(JvmManager.java:74)
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:404)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Vuk Erecegovac  
View profile  
 More options Apr 6 2011, 10:59 pm
From: Vuk Erecegovac <vuk.ercego...@gmail.com>
Date: Wed, 6 Apr 2011 19:59:04 -0700
Local: Wed, Apr 6 2011 10:59 pm
Subject: Re: RuntimeException: Inconsistent state
Print | Individual message | Show original | Report this message | Find messages by this author

Not sure what the exact cause is, but a Google search with bits of your
exception show that Hadoop
had this issue in older versions ( <= 0.19 ?).


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google