So there are three ways. 1. make your model as stream source 2. let master read the model once, distribute it via constructor, and update it periodically 3. let worker read the model and update it periodically(you mentioned)
option 3 would be problematic if you scale a lot and use many parallelisms because there are too many connections. option 2 is the best, if you don't have to update your model. otherwise you have to restart your flink job to get the new model, or implement this update logic your own. option 1 for me is the best if you need to update the model. so you can control how often you read Best, Sendoh -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
