Hey @mkala1, good questions.
Oozie is really an orchestration framework. A common use case being, at 2am wake up and launch a MapReduce job, which then launches a Hive query, which then runs a bash script, which then sends out a completion email. Blox is a scheduling framework for Docker containers on ECS. A common use case being, schedule a metrics daemon across all instances in your ECS cluster. Blox would then monitor your metrics daemon ensuring it stays up, and automatically schedule the daemon as new instances come online.
So I would say they are similar in that they both schedule things. But Oozie is more focused on workflows, whereas Blox is more focused on launching long-lived Docker daemons right now.
scheduler_1 | 2017-10-04T15:08:20Z [CRITICAL] Could not start etcd: grpc: timed out when dialing
css_1 | 2017-10-04T15:08:19Z [CRITICAL] Error starting event stream handler: grpc: timed out when dialing
etcd_1 | 2017-10-04 15:08:13.321397 C | etcdserver: create wal error: rename /var/lib/etcd/wal.tmp /var/lib/etcd/wal: permission denied
etcd_1 | 2017-10-05 11:29:06.271677 I | v3rpc/grpc: grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp [::]:2379: connect: cannot assign requested address"; Reconnecting to {"[::]:2379" <nil>}