If that:
When kafka data to the data collected during the test flume disk, due to bloggers wrote a program based on the system time to generate a log file.
After the cluster is up, but also changed the time of the system, leading flume collect data to kafka failed to find the reasons for a long time, before we know it comes to checking the system time communication between the flume and kafka, after changing the system time will lead them communication failure, resulting in the collection of data to kafka failure. (Date not later change issues)
Solution:
Restart the cluster can be.
Lessons learned:
Do not change the system time, there is always the unknown with this pit