aph.getEdges().getType())
>>> .distinct(0, 1);
>>> }
>>>
>>> Note: the edges inside the graph originalGraph edge
>>> DataSet are much greater in number than the elements of
>>> the verti
w also blocks T3.
>>>>>>
>>>>>> There are multiple possible explanations i can come up with:
>>>>>> * the preceding operators are blocked on something or *really *slow
>>>>>> * the preceding operators are actually finished, but aren'
t;>>
>>>>> A deadlock in the network stack should appear as all existing operator
>>>>> threads being blocked.
>>>>> We can probably rule out a problem with the join logic by removing the
>>>>> second join and trying again.
>>>
t;>>> ExecutionEnvironment.createLocalEnvironmentWithWebUI(conf);
>>>>
>>>> Regarding the preceding operators, the thread dumps I got were pointing
>>>> to a specific set of operations over DataSet instances that were
>>>> passed into my
inalGraph.getEdges())
>>> .where(0).equalTo(0)
>>> *.with((source, edge) -> edge)* *// Thread 1 is blocked
>>> here*
>>> .returns(originalGraph.getEdges().getType())
>>> .join(vertices)
>>> .where(1
DataSet, so I
>> believe that function is being used correctly.
>>
>> I will try testing with remote (cluster) mode to have access to the web
>> front-end, but I have some questions for now:
>>
>> - The fact that they are blocked in different JoinOperator in
: miguel.e.coim...@gmail.com
<mailto:miguel.e.coim...@ist.utl.pt>
-- Forwarded message --
From: Chesnay Schepler mailto:ches...@apache.org>>
To: user@flink.apache.org <mailto:user@flink.apache.org>
Cc:
Bcc:
D
in this code), and they produced correct values
> (non-empty files), so I don't have a clue what the threads inside Flink's
> runtime are waiting on.
>
> Thanks for the help so far Chesnay.
>
>
> Miguel E. Coimbra
> Email: miguel.e.coim...@gmail.com
>
> ---
Hello,
Thread #1-3 are waiting for input, Thread #4 is waiting for the job to
finish.
To further debug this I would look into what the preceding operators are
doing, whether they are blocked on something or are emitting records
(which you can check in the UI/metrics).
On 15.04.2018 18:40,
Hello,
I am running into a situation where the Flink threads responsible for my
operator execution are all stuck on WAITING mode.
Before anything else, this is my machine's spec:
Linux 4.4.88 #1 SMP x86_64 Intel(R) Xeon(R) CPU E7- 4830 @ 2.13GHz
GenuineIntel GNU/Linux
256 GB RAM
I am running i
10 matches
Mail list logo
