Hi Satya,
Sorry for my jumping in the conversation, after I came across your post when giving myself some routines on Google Groups. Although I cannot speak for anyone in Sparrow team (with the current state of her existence), I would love to share you with something based off of my understanding, which might be helpful for tackling your concern as indicated by both of your posts.
As shown, Sparrow has provided a strong and solid base for some other pieces of work appearing its side out-of-the-blue, such as Apollo (from MSFT), KMN (from UC Berkeley), in which you can just find the answer to your question about the advantages and disadvantages of decentralised job schedulers (including Sparrow). Another piece of work, i.e. Omega (from Google, which has two versions featured with the published one and the one in use at the company), and the Sparrow paper together with the pertaining source code available online may also raise your great attention if interested.
About the roadmap of Sparrow, my educated guess based upon the given answer from somebody is: Sparrow is intimately tied with Spark, and Spark is having a sweet marriage with Yarn, about which I guess we all have known for quite a while. Further, how far Sparrow can keep moving forward in the right direction, only time (and money) can tell. ;)
I hope the little above would make some sense to you, and as always, everything comes with a price, which is especially true for something beautiful. Good luck with your business, so goes with ours. ;)
King days.
Dr. Lu