Introduction 

Runtime monitor will monitor and collect program states, metadata, lineage, workflow token..

Approaches

Approach #1

In order to collect all the monitoring data, Runtime Monitor will poll heartbeat messages from Heartbeat Handler periodically using single rest endpoint:

1. Runtime Monitor polls for next batch of heartbeat messages along with last persisted offset for each for each topic.
2. Heartbeat Handler will fetch heartbeat messages from each topic (status, lineage, metadata..) using last persisted offset provided by Runtime Monitor
3. Heartbeat Handler will gathers gather all the heartbeat messages and sends in a batch to Runtime Monitor along with processed offsets for each topic.
   
   1.  If the Runtime Monitor fails, it will start from last persisted offset for each topic and ask for heartbeat messages after that.
   2.  If the Runtime Monitor fails while it is making changes to the corresponding stores, it may reprocess some heartbeat messages depending on what last offset is.

Pros:

• Less number of http requests.Runtime Monitor will poll periodically, so having  
• Having single rest endpoint helps in terms of there will be less requests to be served would reduce number of requests handled by web server running in Heartbeat Handler.
• Adding more monitoring data would be easier since we do not need rest endpoint for each type of data we collect

Cons:

• Load balance among all the topics such that recent information needs to be provided to Runtime Monitor with very little delay. So 

• . Should we read same number of messages from each topic? Or we can have only one topic for all the monitoring data and read messages from there. 

Approach #2

In order to collect all the monitoring data, Runtime Monitor will poll heartbeat messages from Heartbeat Handler periodically using multiple rest endpoints:

1. Runtime Monitor polls for next batch of heartbeat messages along with last persisted offset for each topic. Depending on implementation can be done serially or simultaneously for each topic.
2. Heartbeat Handler will fetch heartbeat messages from topic using last persisted offset provided by Runtime Monitor
3. Heartbeat Handler will gather all the heartbeat messages and sends in a batch to Runtime Monitor along with processed offsets for each topic.
   
   1.  If the Runtime Monitor fails, it will start from last persisted offset for each topic and ask for heartbeat messages after that.
   2.  If the Runtime Monitor fails while it is making changes to the corresponding stores, it may reprocess some heartbeat messages depending on what last offset is.

Pros:

• We can poll for more data concurrently from different topics which will reduce delay.

Cons:

• More number of http requests 
• At a time, more number of requests handled by web server running in Heartbeat Handler if the implementation is parallel.
• Adding more monitoring data would mean adding more rest endpoints to Runtime Handler and more http requests to web server.

API changes

New Programmatic APIs

New Java APIs introduced (both user facing and internal)

Deprecated Programmatic APIs

New REST APIs

Deprecated REST API

CLI Impact or Changes

• Impact #1
• Impact #2
• Impact #3

UI Impact or Changes

• Impact #1
• Impact #2
• Impact #3

Security Impact 

What's the impact on Authorization and how does the design take care of this aspect

Impact on Infrastructure Outages 

System behavior (if applicable - document impact on downstream [ YARN, HBase etc ] component failures) and how does the design take care of these aspect

Test Scenarios

Releases

Release X.Y.Z

Release X.Y.Z

Related Work

• Work #1
• Work #2
• Work #3

Future work