Assertion failed: received sequence number doesn't match request sequence number
See original GitHub issueHi, I use 2.3.2-SNAPSHOT version, running a spark applications shows following error, I am using namespace: “wascl-nam” ,name: “wasclmonitors” Event Hub.
18/05/04 01:45:26 WARN TaskSetManager: Lost task 0.0 in stage 2.0 (TID 75, wn0-lam-ag.ifckrjhhuanelgm1hrygboricd.xx.internal.cloudapp.net, executor 12): java.lang.AssertionError: assertion failed: requestSeqNo 443495453 does not match the received sequence number 443872987
at scala.Predef$.assert(Predef.scala:170)
at org.apache.spark.eventhubs.client.CachedEventHubsReceiver.org$apache$spark$eventhubs$client$CachedEventHubsReceiver$$receive(CachedEventHubsReceiver.scala:89)
at org.apache.spark.eventhubs.client.CachedEventHubsReceiver$.receive(CachedEventHubsReceiver.scala:118)
at org.apache.spark.eventhubs.rdd.EventHubsRDD$EventHubsRDDIterator.next(EventHubsRDD.scala:124)
at org.apache.spark.eventhubs.rdd.EventHubsRDD$EventHubsRDDIterator.next(EventHubsRDD.scala:103)
at scala.collection.Iterator$$anon$12.nextCur(Iterator.scala:434)
at scala.collection.Iterator$$anon$12.hasNext(Iterator.scala:440)
at org.apache.spark.storage.memory.MemoryStore.putIteratorAsBytes(MemoryStore.scala:371)
at org.apache.spark.storage.BlockManager$$anonfun$doPutIterator$1.apply(BlockManager.scala:1055)
at org.apache.spark.storage.BlockManager$$anonfun$doPutIterator$1.apply(BlockManager.scala:1029)
at org.apache.spark.storage.BlockManager.doPut(BlockManager.scala:969)
at org.apache.spark.storage.BlockManager.doPutIterator(BlockManager.scala:1029)
at org.apache.spark.storage.BlockManager.getOrElseUpdate(BlockManager.scala:760)
at org.apache.spark.rdd.RDD.getOrCompute(RDD.scala:334)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:285)
at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:96)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:53)
at org.apache.spark.scheduler.Task.run(Task.scala:108)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:338)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Issue Analytics
- State:
- Created 5 years ago
- Comments:25 (13 by maintainers)
Top Results From Across the Web
10794: RSN Does Not Match or Not All Data Correct, Post Failed
Resolving this error requires assistance from Drake Support, (828) 524-8020, and may involve repairing your local EF database.
Read more >Number sequences overview - Dynamics 365 - Microsoft Learn
Number sequences are used to generate readable, unique identifiers for master data records and transaction records that require identifiers.
Read more >Sequence number and acknowledgement number do not match
I'm pretty sure that what you're seeing is an ACK from the receiver after having received 1 full segment plus 1 IP fragment...
Read more >Acknowledgment Number - an overview | ScienceDirect Topics
The sequence number is the field that allows packets received out of order to be put back in the correct order. The sender...
Read more >Fix errors porting numbers to Voice - Google Help
Then, cancel and restart the port order. This error can also be caused by these less common issues: Unstable internet connection; Duplicate requests...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I tried the solution is working for me. Using Eventhub or IotHub as entrance. I used the following connectors:
Thank you for the release.
Hey @ogidogi - it’s true that the message printing out is similar but the code is all quite different. But, yea, this is the only bug I’ve found in the current release - I’m fixing it now!