Hi,
Flink (or some of its services) listens on three random TCP ports
during the local[1] execution, e.g., 39951, 41009 and 42849.
[1]:
https://ci.apache.org/projects/flink/flink-docs-stable/dev/local_execution.html#local-environment
The sockets listens on `0.0.0.0` and since I need to run some
Hi Chandu,
Maybe you can use a custom trigger:
* .trigger(**ContinuousEventTimeTrigger.of(Time.minutes(15)))*
This would continuously trigger your aggregate every period of time.
Thanks,
Rafi
On Thu, Dec 5, 2019 at 1:09 PM Andrey Zagrebin wrote:
> Hi Chandu,
>
> I am not sure whether usi
Dear community,
happy to share this week's community digest with an update on Flink 1.8.3,
a revival of the n-ary stream operator, a proposal to move our build
infrastructure to Azure pipelines, and quite a few other topics. Enjoy.
Flink Development
==
* [releases] The feature freeze
Anyone?
On Fri, 6 Dec 2019 at 19:07, Komal Mariam wrote:
> Hello everyone,
>
> I want to get some insights on the KeyBy (and Rebalance) operations as
> according to my understanding they partition our tasks over the defined
> parallelism and thus should make our pipeline faster.
>
> I am reading
Hi Robert and Roman,
Yeah, letting users know System.exit() is called would be much more
appropriate than just intercepting and ignoring.
Best,
Dongwon
On Sat, Dec 7, 2019 at 11:29 PM Robert Metzger wrote:
> I guess we could manage the security only when calling the user's main()
> method.
>
>
Hello,
Using Flink on Yarn, I could not understand the documentation for how to
read the default metrics via code. In particular, I want to read
throughput, i.e. CPU usage, Task/Operator's numRecordsOutPerSecond, and
Memory.
Is there any sample code for how to read such default metrics? Is there
Hi Komal,
KeyBy(Hash Partition, logically partition) and rebalance(physical
partition) are both one of the partitions been supported by Flink.[1]
Generally speaking, partitioning may cause network communication(network
shuffles) costs which may cause more time cost. The example provided by you
ma
Thanks Yangze for starting this discussion.
Just share my thoughts.
If the mesos official docker image could not meet our requirement, i
suggest to build the image locally.
We have done the same things for yarn e2e tests. This way is more flexible
and easy to maintain. However,
i have no idea how
Hi,
I have checked the logs with this keyword *StaticFileServerHandler *in
it, But there were no logs coming for "Flink Job Cluster".
Then i checked for Flink Session Cluster, i was able to find the logs for
the *StaticFileServerHandler *keyword.
Can i raise this as bug ?
Best Regards,
Jatin
Hi dev,
The time of the window may have different semantics.
In the session window, it's only a time gap, the size of the window is
driven via activity events.
In the tumbling or sliding window, it means the size of the window.
For more details, please see the official documentation.[1]
Best,
Vi
11 matches
Mail list logo