MENU
What is the risk of increasing max.in.flight.requests.per.connection while also enabling retries in a producer?
Suggested Answer: B
Get Premium CCDAK Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Some messages may require multiple retries. If there are more than 1 requests in flight, it may result in messages received out of order. Note an exception to this rule is if you enable the producer settingenable.idempotence=true which takes care of the out of ordering case on its own. Seehttps://issues.apache.org/jira/browse/KAFKA-5494
25 comments · newest first
ME
Melvin
10 months ago
Wait, so retries can actually cause more problems?
AJ
Aja
10 months ago
Totally agree, message order can get messed up too!
TY
Tyisha
10 months ago
I thought increasing requests would boost throughput, not reduce it?
KI
Kirby
10 months ago
Less resilient? That sounds risky!
ER
Erasmo
11 months ago
A higher max in-flight requests can lead to at least once delivery issues.
EM
Emmanuel
11 months ago
Less resilient sounds familiar, but I’m not confident if that’s the main risk here. I need to think back to the examples we went over in class.
LA
Laticia
11 months ago
I feel like reducing throughput might be a concern, but I can't recall the specifics. It seems like it could be related to how many requests are being processed at once.
BR
Brice
11 months ago
I think there was a practice question that mentioned message order not being preserved when retries are enabled. That could be a risk too.
GW
Gwenn
12 months ago
I remember something about how increasing max.in.flight.requests.per.connection can lead to at least once delivery issues, but I'm not entirely sure.
RO
Ronny
12 months ago
I'm feeling pretty confident about this one. Increasing the max in-flight requests while enabling retries is likely to reduce the overall reliability of the system, potentially leading to at least once delivery and message order issues. I'll make sure to select the best answer.
BE
Belen
12 months ago
Okay, I think I've got a handle on this. Increasing the max in-flight requests could reduce throughput, while enabling retries might impact message order. I'll need to be careful to balance these factors to ensure the system remains resilient.
KA
Katlyn
1 year ago
Hmm, this seems like a tricky one. Increasing the max in-flight requests could help improve throughput, but enabling retries might introduce some risks around message order and delivery guarantees. I'll need to weigh the pros and cons.
LA
Lashawnda
1 year ago
I'm a bit confused about how increasing max.in.flight.requests.per.connection and enabling retries in a producer could impact the system. I'll need to think through the potential tradeoffs carefully.
LA
Lauran
1 year ago
I think D is the way to go. 'Less resilient' sounds like the perfect recipe for a system that's as sturdy as a house of cards in a hurricane.
WI
Winfred
1 year ago
Ooh, C for sure! Reducing throughput is the way to go if you want to slow down your message delivery like a snail on a treadmill.
DE
Denae
1 year ago
D) Less resilient
JA
Jaleesa
1 year ago
A) At least once delivery is not guaranteed
AN
Antione
1 year ago
C) Reduce throughput
FA
Fannie
1 year ago
Increasing max.in.flight.requests.per.connection with retries? That's like putting a turbocharger on a tricycle - you're just asking for trouble!
SH
Shawna
1 year ago
C) Reduce throughput
FI
Filiberto
1 year ago
B) Message order not preserved
WI
Wilbert
1 year ago
A) At least once delivery is not guaranteed
CA
Carri
1 year ago
But increasing max.in.flight.requests.per.connection can also improve throughput, so it's a trade-off.
LO
Lottie
1 year ago
I agree with Jame. Enabling retries in a producer can lead to duplicate messages being sent.
JA
Jame
2 years ago
I think the risk is that at least once delivery is not guaranteed.