hmmmm stopping it and starting it again has got it outputting more destination logs again, but that defeats the point a bit!
Do I have a conflict here?
recv_timestamp is the originating source time of the msg
ingest_timestamp is added by Elasticsearch to the index at the time the doc is indexed
and after the restart, it only reached the first checkpoint.
so I've stopped and restarted again, and I expect it will pause at the next checkpoint again
I still have a problem here.
The status will be indexing, but no data is coming out. Then after a few hours there are a splurge of new destination documents output
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.