Kafka Producer: Sync timing issues cause erroneous deletes

If an alarm is created immediately after the synchronization process is started, then the alarm can be erroneously deleted from the ktable.

While the state will be eventually consistent (rectified on the next sync) these deletes can cause problems for other systems integrating with the topics. In the case of OCE, this problem manifested itself by creating duplicate situations.

The following log snippet from karaf.log shows this in in action: