flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From burgesschen <tchen...@bloomberg.net>
Subject sanity check in production
Date Wed, 12 Jul 2017 18:22:35 GMT
Hello everyone, 

Our team ran into an issue that testing new deployment of flink job is
difficult as explained below 

When we are deploying new version of a flink job in production. we want to
be able to have the job process some test messages and verify the output to
make sure that the job is running correctly. (sanity check) 

The tests messages interfere with the watermark of the flink job,
potentially causing it dropping real messages. 

Possible solutions: 
1. have a separate watermark for the test messages 
  (looks not supported by the current framework) 

2. run a separate Flink job (same code) in production for sanity check
before actual deployment 
  (high operational costs) 

3. cancel the running production job with a save point, run a new job with
the save point, do sanity check and mess up the watermark of the new job,
kill the new job, do actual deployment with the same save point. 
  (high operational costs) 

Any idea is appreciated, thanks! 

View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/sanity-check-in-production-tp14229.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.

View raw message