Ruidong Li created FLINK-8617:
-
Summary: Fix code generation bug while accessing Map type
Key: FLINK-8617
URL: https://issues.apache.org/jira/browse/FLINK-8617
Project: Flink
Issue Type: Bug
Cliff Resnick created FLINK-8616:
Summary: Missing null check in OperatorChain#pushToOperator masks
ClassCastException
Key: FLINK-8616
URL: https://issues.apache.org/jira/browse/FLINK-8616
Project: Fl
-->
On Thu, Feb 8, 2018 at 2:16 AM, Tzu-Li (Gordon) Tai
wrote:
> Regarding the two hooks you would like to be available:
>
>
>- Provide hook to override discovery (not to hit Kinesis from every
>subtask)
>
> Yes, I think we can easily provide a way, for example setting -1 for
> SHARD_DIS
Karrtik Iyer created FLINK-8615:
---
Summary: Configuring Apache Flink Local Set up with Pseudo
distributed Yarn
Key: FLINK-8615
URL: https://issues.apache.org/jira/browse/FLINK-8615
Project: Flink
Till Rohrmann created FLINK-8614:
Summary: Enable Flip-6 per default
Key: FLINK-8614
URL: https://issues.apache.org/jira/browse/FLINK-8614
Project: Flink
Issue Type: Sub-task
Compon
Till Rohrmann created FLINK-8613:
Summary: Return excess container in YarnResourceManager
Key: FLINK-8613
URL: https://issues.apache.org/jira/browse/FLINK-8613
Project: Flink
Issue Type: Impr
Till Rohrmann created FLINK-8612:
Summary: Add non-detached job mode
Key: FLINK-8612
URL: https://issues.apache.org/jira/browse/FLINK-8612
Project: Flink
Issue Type: Improvement
Com
Till Rohrmann created FLINK-8611:
Summary: Add result future to JobManagerRunner
Key: FLINK-8611
URL: https://issues.apache.org/jira/browse/FLINK-8611
Project: Flink
Issue Type: Improvement
Till Rohrmann created FLINK-8610:
Summary: Remove RestfulGateway from JobMasterGateway
Key: FLINK-8610
URL: https://issues.apache.org/jira/browse/FLINK-8610
Project: Flink
Issue Type: Improve
Till Rohrmann created FLINK-8609:
Summary: Add support to deploy detached job mode clusters
Key: FLINK-8609
URL: https://issues.apache.org/jira/browse/FLINK-8609
Project: Flink
Issue Type: Ne
Till Rohrmann created FLINK-8608:
Summary: Add MiniDispatcher for job mode
Key: FLINK-8608
URL: https://issues.apache.org/jira/browse/FLINK-8608
Project: Flink
Issue Type: New Feature
Timo Walther created FLINK-8607:
---
Summary: Add a basic embedded SQL CLI client
Key: FLINK-8607
URL: https://issues.apache.org/jira/browse/FLINK-8607
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-8606:
---
Summary: Clean up Table API for Java users
Key: FLINK-8606
URL: https://issues.apache.org/jira/browse/FLINK-8606
Project: Flink
Issue Type: Improvement
Till Rohrmann created FLINK-8605:
Summary: Enable job cancellation from the web UI
Key: FLINK-8605
URL: https://issues.apache.org/jira/browse/FLINK-8605
Project: Flink
Issue Type: Improvement
Till Rohrmann created FLINK-8604:
Summary: Move JobTerminationHandler to WebMonitorEndpoint
Key: FLINK-8604
URL: https://issues.apache.org/jira/browse/FLINK-8604
Project: Flink
Issue Type: Im
Till Rohrmann created FLINK-8603:
Summary: Split RestClusterClient#submitJob into submitJob and
requestJobResult
Key: FLINK-8603
URL: https://issues.apache.org/jira/browse/FLINK-8603
Project: Flink
Yes this is how it works. The TaskExecutor gets polled for its heartbeat
response if you wish. Of course, if it does not get polled often enough,
then the JobMaster or RM can also time out.
On Thu, Feb 8, 2018 at 1:22 PM, mingleizhang wrote:
> Thanks Till. But sorry, what what! The TaskExecutor
Thanks Till. But sorry, what what! The TaskExecutor is only responding to
heartbeat requests but not actively sending them out ? ? ? I think taskexecutor
should report it's status to jobmanager and resourcemanager by heartbeat. And
TaskExecutor is like a slave and jobmanager and resourcemanager
The RPC methods `heartbeatFromXYZ` are the incoming heartbeats from the
JobMaster and ResourceManager, respectively. That's why they are called
heartbeatFrom. The TaskExecutor is only responding to heartbeat requests
but not actively sending them out.
Cheers,
Till
On Thu, Feb 8, 2018 at 1:06 PM,
Attached is the taskmanager design picture. And from the picturen, I know
taskmanager send heartbeat to jobmanager ( also called jobmaster in flip6 now)
and resourcesmanager periodically. But when I watched the source code below in
TaskExecutor.java. I feel confused about the function name. Shou
Hi,
The job is not explicitly stopped, bringing down the cluster will also bring
down the job. (Which is maybe not the nicest way of doing things but it works.)
Sources can trigger pipeline termination by returning from their run() method.
Best,
Aljoscha
> On 7. Feb 2018, at 21:15, Thomas Weis
Regarding the two hooks you would like to be available:
Provide hook to override discovery (not to hit Kinesis from every subtask)
Yes, I think we can easily provide a way, for example setting -1 for
SHARD_DISCOVERY_INTERVAL_MILLIS, to disable shard discovery.
Though, the user would then have to
Hi Thomas,
It’s great that you’ve brought out these issues, which IMO are all very valid.
They have also been in my head for a while.
Here’s a list of things, out of the top of my head, that I would really like to
improve as part of a major Kafka / Kinesis connector rework.
Some have JIRAs for
Local state recovery is almost completely done. Only some reviews and
merging of the final PRs is pending.
The network stack improvements are on a good way to be finished by the end
of this week or beginning of next week. To my knowledge we got recently
green Travis builds :-) The network stack ch
A full build incl. tests takes on my machine about 40 to 50 mins (if all
dependencies are locally cached).
Locally, I only run tests on the modules that I modified as Chesnay said.
2018-02-08 8:05 GMT+01:00 Chesnay Schepler :
> Generally we run the full test suite on travis for every pull request
Sihua Zhou created FLINK-8602:
-
Summary: Accelerate recover from failover when use incremental
checkpoint
Key: FLINK-8602
URL: https://issues.apache.org/jira/browse/FLINK-8602
Project: Flink
Iss
26 matches
Mail list logo