# Exception cause unwrapping ran for 10 levels **URL:** \ **Category:** Elasticsearch\ **Created:** [January 6, 2014, 12:55pm UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114 "2014-01-06T12:55:09Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\ **Post date:** [January 6, 2014, 12:55pm UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/1 "2014-01-06T12:55:09Z")
Hi, we are using elasticsearch version 0.90.7 and following are gist file. [https://gist.github.com/jasonwee/8282477](https://gist.github.com/jasonwee/8282477) not sure what is happening "Exception cause unwrapping ran for 10 levels" and if it is a concern? The exception shown after some time. Any idea? Jason -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9d767e9d-33b9-4c36-b725-5aa3bf6d7a09%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9d767e9d-33b9-4c36-b725-5aa3bf6d7a09%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 6, 2014, 1:33pm UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/2 "2014-01-06T13:33:26Z")
ES is unable to transport an exception back to the client, exceptions are thrown, passed back and forth, and the procedure is retried until the Java stack is full (StackOverflowError). Yes, it is a concern, it is a bug, a stack overflow must not happen. Is the gist the whole stack trace? I bet you only posted the first few lines... In the meantime, can you check if you run the same JVM version at server and client side? A transport exception can not be deserialized, and this is typical for a JVM mismatch. Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH37nkrvCOdfqpYP\_sDD-ChmpiipWLb%3DgMe15LfttUv4w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH37nkrvCOdfqpYP_sDD-ChmpiipWLb%3DgMe15LfttUv4w%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\ **Post date:** [January 6, 2014, 4:37pm UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/3 "2014-01-06T16:37:16Z")
> Is the gist the whole stack trace? I bet you only posted the first few > lines... > log filesize is 427MB and total lines 5463550 and if i paste the entire > file into gist, it would break github limit? After gzip the file, it is > 5.9MB. If you have a server, I can upload the gzip log to your server. server and client both running the same version the entire times. $ java -version java version "1.6.0\_25" Java(TM) SE Runtime Environment (build 1.6.0\_25-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode) On Mon, Jan 6, 2014 at 9:33 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<[joergprante@gmail.com](mailto:joergprante@gmail.com) > wrote: > ES is unable to transport an exception back to the client, exceptions are > thrown, passed back and forth, and the procedure is retried until the Java > stack is full (StackOverflowError). Yes, it is a concern, it is a bug, a > stack overflow must not happen. > > Is the gist the whole stack trace? I bet you only posted the first few > lines... > > In the meantime, can you check if you run the same JVM version at server > and client side? A transport exception can not be deserialized, and this is > typical for a JVM mismatch. > > Jörg > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH37nkrvCOdfqpYP\_sDD-ChmpiipWLb%3DgMe15LfttUv4w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH37nkrvCOdfqpYP_sDD-ChmpiipWLb%3DgMe15LfttUv4w%40mail.gmail.com) > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHO4itxSN34myLoEu5ofj3HAi0G18bQpeUECT-rXJ7wq-k5%3DEQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itxSN34myLoEu5ofj3HAi0G18bQpeUECT-rXJ7wq-k5%3DEQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 6, 2014, 7:30pm UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/4 "2014-01-06T19:30:36Z")
I was not speaking of the whole logfile, but the whole stacktrace, just to make sure where the culprit started. If there was no OOM or other things around, it would be surprising. Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFi-T8iiKTULr\_S-7OddJnAoGGF4%3Db6reB3vGejDArgnQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFi-T8iiKTULr_S-7OddJnAoGGF4%3Db6reB3vGejDArgnQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\ **Post date:** [January 7, 2014, 4:16am UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/5 "2014-01-07T04:16:35Z")
Hi Jörg, Sure, my bad. There is no OOM and here is the second gist, [gist:8294514 · GitHub](https://gist.github.com/jasonwee/8294514) . The exceptions are repetitive, so that explains large number of lines in the log file. Does the second gist help to determine the problem? I can get the log if it does not tell where might be the cause. Thank you again for helps. Jason On Tue, Jan 7, 2014 at 3:30 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<[joergprante@gmail.com](mailto:joergprante@gmail.com) > wrote: > I was not speaking of the whole logfile, but the whole stacktrace, just to > make sure where the culprit started. If there was no OOM or other things > around, it would be surprising. > > Jörg > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFi-T8iiKTULr\_S-7OddJnAoGGF4%3Db6reB3vGejDArgnQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFi-T8iiKTULr_S-7OddJnAoGGF4%3Db6reB3vGejDArgnQ%40mail.gmail.com) > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHO4itw2EJvBU2wt1KeXg4xjuPVK6B-7UK8kJMtj56R1E3owcg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itw2EJvBU2wt1KeXg4xjuPVK6B-7UK8kJMtj56R1E3owcg%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 7, 2014, 8:34am UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/6 "2014-01-07T08:34:25Z")
Yes, it looks like two nodes do not agree about an update action and a version conflict is pinging between them, node1 and node4. Not sure if this happens while index recovery or while an update is executed, but it is definitely worth raising an issue at the Elasticsearch github to let the Elasticsearch core team have a look. It might be some kind of a deadlock. Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGKNB-1KXab4eWhDnKpe4szdPsidEWq2his2j%3DfPwU7Zw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGKNB-1KXab4eWhDnKpe4szdPsidEWq2his2j%3DfPwU7Zw%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\ **Post date:** [January 7, 2014, 9:19am UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/7 "2014-01-07T09:19:21Z")
Jörg, Done, [Exception cause unwrapping ran for 10 levels · Issue #4639 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/4639) Today when I investigated this issue, and just do a query to the time stamp when the exceptions is happening, data were indexed though. The reason I query is that, we worry if there is no data index during that period exceptions are happening , thus data lost. Thank you. Jason On Tue, Jan 7, 2014 at 4:34 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<[joergprante@gmail.com](mailto:joergprante@gmail.com) > wrote: > Yes, it looks like two nodes do not agree about an update action and a > version conflict is pinging between them, node1 and node4. > > Not sure if this happens while index recovery or while an update is > executed, but it is definitely worth raising an issue at the Elasticsearch > github to let the Elasticsearch core team have a look. It might be some > kind of a deadlock. > > Jörg > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGKNB-1KXab4eWhDnKpe4szdPsidEWq2his2j%3DfPwU7Zw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGKNB-1KXab4eWhDnKpe4szdPsidEWq2his2j%3DfPwU7Zw%40mail.gmail.com) > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHO4itzoqWdujn713RK83ZZL4iGr19nY9nz34wbRtTKOSzcMNA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itzoqWdujn713RK83ZZL4iGr19nY9nz34wbRtTKOSzcMNA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:58am UTC](https://discuss.elastic.co/t/exception-cause-unwrapping-ran-for-10-levels/15114/8 "2017-07-06T01:58:04Z")