server.channels.ch1.transactioncapacity indicates the transaction size, that is, the number of events that the current channel supports transaction processing, which can be set to the same size as…

Question

Options

• ATrue
• BFalse

• A
  72% (42)
• B
  28% (16)

Explanation

Option A is correct because in Apache Flume, transactionCapacity defines the maximum number of events a channel can handle within a single transaction. The source writes events in batches, and the channel must be able to accommodate at least as many events per transaction as the source sends per batch - otherwise the transaction will fail because the channel cannot process all the events the source is trying to commit at once.

Option B is incorrect because setting transactionCapacity smaller than the source's batch size would cause transaction failures: the source attempts to put more events into a transaction than the channel can handle, resulting in errors or data loss.

Memory tip: Think of it like a shopping cart (transactionCapacity) and a supplier truck (batch size). The cart must hold at least as many items as the truck delivers in one trip - if the truck drops off 100 items but your cart only fits 50, the delivery fails. Set the cart size equal to or larger than the delivery batch.

No community discussion yet for this question.