ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <>
Subject [jira] [Updated] (AMBARI-20562) Perf: Asynchronous event handling server/agent
Date Fri, 24 Mar 2017 17:06:41 GMT


Siddharth Wagle updated AMBARI-20562:
    Component/s: ambari-server

> Perf: Asynchronous event handling server/agent
> ----------------------------------------------
>                 Key: AMBARI-20562
>                 URL:
>             Project: Ambari
>          Issue Type: Epic
>          Components: ambari-agent, ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>              Labels: performance
> Ambari's internal event model is heavily fragmented with some of the events that result
in state transitions being synchronous in nature. The proposal of this Epic is to standardize
event handling on the server-side and utilize its asynchronous nature to make architecture
changes that are geared to towards scaling up the performance of Ambari server. The goal is
to support 5K active nodes with this new architecture.
> To summarize the entailment:
> - Write a Global Event Observer to allow clients to subscribe to server side events
> - Use websocket protocol to reduce network chatter between agent and server
> - Reduce the work server has to do to generate STATUS commands for heartbeats.
> - Make execution commands leaner replacing the need for providing topology info and configs
with every command, instead rely on event model.
> - Re-architect the agent to make it more intelligent towards maintaining daemon status
and configs.
> - Reduce computation requirements for every heartbeat and allow for parallel processing
of agent side events

This message was sent by Atlassian JIRA

View raw message