Hi, Santhoosh, Overall looks good to me now. There are still some minor issues / errors in the design doc - in YARN, are you sure that we persist the JobModel to coordinator stream? I checked the code and didn't find that. The JobModel was simply generated and served from the memory in the JobCoordinator. - In YARN, we don't run stream processor yet. We are still running SamzaContainer as for now. - When describing the differences between YARN and standalone model, item 3 and 4 are not basic facts this design depends on. Instead, those seem to be detailed design choices already. Suggest to move to requirements in the design, not the difference between YARN and standalone model - A further question on systems that provides VM and file system isolation (Locker G3): in this case, even two processors are on a single physical host, if they are in two different VMs, they can not share file system, which means that their state stores can not be shared. And in addition, if the system provides some common shared directory, then, what's the locationId in such case?
-Yi On Tue, Feb 20, 2018 at 6:32 PM, santhosh venkat < santhoshvenkat1...@gmail.com> wrote: > Hi everyone, > > This is a voting thread for SEP-11: Host affinity in standalone. > For reference, here is the wiki link: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75957309 > > Link to discussion mail thread: > http://mail-archives.apache.org/mod_mbox/samza-dev/201802.mbox/% > 3CCAFvExu2hrUhnjknWoH3er=q4agh3pzqjtbqwrp9xpdijawv...@mail.gmail.com%3E > > Thanks. >