Audit publishing when Kafka is down
Description
Release Notes
None
relates to
Activity
Show:
Priyanka Nambiar January 27, 2017 at 12:07 AM
Starting CDAP 4.0 we have moved audit publishing via TMS
Russ Savage January 17, 2017 at 5:36 AM
@Poorna Chandra @Priyanka Nambiar is this still valid with the new TMS stuff?
Russ Savage October 25, 2016 at 10:56 PM
Is this still valid with the new messaging platform?
Poorna Chandra August 4, 2016 at 9:54 PM
@Sreevatsan Raman Can we mark the transactional messaging JIRA as a related JIRA to this then?
Sreevatsan Raman August 4, 2016 at 6:48 PM
This will be addressed with transactional messaging.
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Shankar Selvam
Shankar SelvamReporter
Poorna Chandra
Poorna ChandraLabels
Components
Fix versions
Priority
CriticalCreated March 15, 2016 at 6:02 AM
Updated April 27, 2017 at 2:16 AM
Resolved January 27, 2017 at 12:07 AM
Audit publishing to Kafka happens synchronously today, since we want some basic reliability in publishing audit messages. When Kafka server is down this can lead to slower operations and an onslaught of messages in log file. We need to figure out if we can improve this experience.