MINOR: Standardize controller log4j output for replaying records
Standardize controller log4j output for replaying important records. The log message should include
word "replayed" to make it clear that this is a record replay. Log the replay of records for ACLs,
client quotas, and producer IDs, which were previously not logged. Also fix a case where we weren't
logging changes to broker registrations.
AclControlManager, ClientQuotaControlManager, and ProducerIdControlManager didn't previously have a
log4j logger object, so this PR adds one. It also converts them to using Builder objects. This
makes junit tests more readable because we don't need to specify paramaters where the test can use
the default (like LogContexts).
Throw an exception in replay if we get another TopicRecord for a topic which already exists.
@ -1850,7 +1850,10 @@ public final class QuorumController implements Controller {
@@ -1850,7 +1850,10 @@ public final class QuorumController implements Controller {
@ -1872,7 +1875,11 @@ public final class QuorumController implements Controller {
@@ -1872,7 +1875,11 @@ public final class QuorumController implements Controller {
@ -1892,10 +1899,14 @@ public final class QuorumController implements Controller {
@@ -1892,10 +1899,14 @@ public final class QuorumController implements Controller {