cruise
cruise copied to clipboard
Consistency issue in LDA model during worker-side data migration
When migrating worker-side data in LDA app, we have a problem that model is damaged during migration. It's because some of our apps have also partial models in the input table.
However, ET/EM assumes that worker-side table has only immutable input data. As a result, we design them not to care about worker-side table data consistency.
To resolve this problem, we need to provide a consistency mechanism for worker-side tables. Or we may change LDA app to not to use local cache or cope with damage in local model.
Need to fix it, since LDA is a primary workload in multi-job situation.