Лучше по частям собрать.
http://www.newegg.com/Product/Product.aspx?Item=N82E16813157497
Пассивное охлаждение, 16Гб памяти можно поставить. А на то что ты прислал
4Гб максимум, это не годиться.
Выбрать малый корпус и дело с концом.
On Tue, Jun 3, 2014 at 4:35 PM, Vadim Chekan wrote:
> Ok, it's
Ok, it's a bug in spark. I've submitted a patch:
https://issues.apache.org/jira/browse/SPARK-2009
On Mon, Jun 2, 2014 at 8:39 PM, Vadim Chekan wrote:
> Thanks for looking into this Tathagata.
>
> Are you looking for traces of ReceiveInputDStream.clearMetadata call?
> Here is the log: http://wep
Thanks for looking into this Tathagata.
Are you looking for traces of ReceiveInputDStream.clearMetadata call?
Here is the log: http://wepaste.com/vchekan
Vadim.
On Mon, Jun 2, 2014 at 5:58 PM, Tathagata Das
wrote:
> Can you give all the logs? Would like to see what is clearing the key "
> 14
Can you give all the logs? Would like to see what is clearing the key
" 1401754908000
ms"
TD
On Mon, Jun 2, 2014 at 5:38 PM, Vadim Chekan wrote:
> Ok, it seems like "Time ... is invalid" is part of normal workflow, when
> window DStream will ignore RDDs at moments in time when they do not matc
Ok, it seems like "Time ... is invalid" is part of normal workflow, when
window DStream will ignore RDDs at moments in time when they do not match
to the window sliding interval. But why am I getting exception is still
unclear. Here is the full stack:
14/06/02 17:21:48 INFO WindowedDStream: Time 1
I am assuming that you are referring to the "OneForOneStrategy: key not
found: 1401753992000 ms" error, and not to the previous "Time 1401753992000
ms is invalid ...". Those two seem a little unrelated to me. Can you give
us the stacktrace associated with the key-not-found error?
TD
On Mon, Jun
