diff options
author | Vadim Chekan <kot.begemot@gmail.com> | 2014-06-17 22:03:50 -0700 |
---|---|---|
committer | Patrick Wendell <pwendell@gmail.com> | 2014-06-17 22:04:06 -0700 |
commit | 889f7b7624689444ecdb4f0ca16ef78f9bfc8430 (patch) | |
tree | 4df606d84546e1ab5a4c27e58c6cc86c8c6856e8 /sql | |
parent | 9e4b4bd0837cfc4ef1af1edcbc56290821e49e92 (diff) | |
download | spark-889f7b7624689444ecdb4f0ca16ef78f9bfc8430.tar.gz spark-889f7b7624689444ecdb4f0ca16ef78f9bfc8430.tar.bz2 spark-889f7b7624689444ecdb4f0ca16ef78f9bfc8430.zip |
[STREAMING] SPARK-2009 Key not found exception when slow receiver starts
I got "java.util.NoSuchElementException: key not found: 1401756085000 ms" exception when using kafka stream and 1 sec batchPeriod.
Investigation showed that the reason is that ReceiverLauncher.startReceivers is asynchronous (started in a thread).
https://github.com/vchekan/spark/blob/master/streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala#L206
In case of slow starting receiver, such as Kafka, it easily takes more than 2sec to start. In result, no single "compute" will be called on ReceiverInputDStream before first batch job is executed and receivedBlockInfo remains empty (obviously). Batch job will cause ReceiverInputDStream.getReceivedBlockInfo call and "key not found" exception.
The patch makes getReceivedBlockInfo more robust by tolerating missing values.
Author: Vadim Chekan <kot.begemot@gmail.com>
Closes #961 from vchekan/branch-1.0 and squashes the following commits:
e86f82b [Vadim Chekan] Fixed indentation
4609563 [Vadim Chekan] Key not found exception: if receiver is slow to start, it is possible that getReceivedBlockInfo will be called before compute has been called
(cherry picked from commit 26f6b989312a9a48a27a23ecc68702bd14032e55)
Signed-off-by: Patrick Wendell <pwendell@gmail.com>
Diffstat (limited to 'sql')
0 files changed, 0 insertions, 0 deletions