Hello,
I'm trying to upgrade flink from 1.8 to 1.11 and StreamTask's
getcheckpointlock method is removed and the new recommendation is to use
MailboxExecutor. Currently we're using it like:
synchronized(operator.getContainingTask.getCheckpointLock()) {
// perform some operation
}
The pur
articles on how Flink decides on how many
messages will enter into an Async Operator when the capacity is specified as
1000 but available memory is only 4GB.
Thanks,
Sanket Agrawal
Thank you @Piotr Nowojski<mailto:pnowoj...@apache.org> for helping me.
From: Piotr Nowojski
Sent: Wednesday, September 29, 2021 12:53 PM
To: Sanket Agrawal
Cc: Ragini Manjaiah ; user@flink.apache.org
Subject: Re: Event is taking a lot of time between the operators
[**EXTERNAL EMAIL
et me know if you need any other information or if you have any
recommendations on improving the approach.
Thanks,
Sanket Agrawal
From: Ragini Manjaiah
Sent: Wednesday, September 29, 2021 11:17 AM
To: Sanket Agrawal
Cc: Piotr Nowojski ; user@flink.apache.org
Subject: Re: Event is taking a l
c does not uses
multiple threads directly) is available for the next message as soon as it
calls CompletableFuture.supplyAsync on the current message.
Thanks,
Sanket Agrawal
From: Piotr Nowojski
Sent: Tuesday, September 28, 2021 8:02 PM
To: Sanket Agrawal
Cc: user@flink.apache.org
Subject: Re:
* Environment: Amazon KDA. 1 Kinesis Processing Unit (1vCore & 4GB ram),
and 1 parallelism.
* Flink Version: 1.8.0
* Backpressure: Flink dashboard shows that backpressure is OK.
* Input rate: 60 messages per second.
Any kind of pointers/help will be very useful.
Thanks,
Sanket Agrawal
Hi,
We are trying to use Kinesis along with Flink(1.11.2) and JDK 11 on EMR
cluster(6.2). When the application starts we are getting below error:
2021-08-24 12:46:27.980 [INFO] [CONFIGURATION_BROADC] {App-N=app_name,
App-V=3.0.0} {}
org.apache.flink.kinesis.shaded.com.amazonaws.services.kinesi
