[ https://issues.apache.org/jira/browse/AMBARI-16828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297339#comment-15297339 ]
Siddharth Wagle commented on AMBARI-16828: ------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] ambari-metrics .................................... SUCCESS [1.197s] [INFO] Ambari Metrics Common ............................. SUCCESS [13.315s] [INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [4.951s] [INFO] Ambari Metrics Flume Sink ......................... SUCCESS [6.694s] [INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [4.056s] [INFO] Ambari Metrics Storm Sink ......................... SUCCESS [1.328s] [INFO] Ambari Metrics Collector .......................... SUCCESS [4:11.410s] [INFO] Ambari Metrics Monitor ............................ SUCCESS [4.129s] [INFO] Ambari Metrics Grafana ............................ SUCCESS [6.550s] [INFO] Ambari Metrics Assembly ........................... SUCCESS [23.462s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5:17.293s [INFO] Finished at: Mon May 23 16:23:49 PDT 2016 [INFO] Final Memory: 68M/494M [INFO] ------------------------------------------------------------------------ > Support round-robin scheduling with failover for Sinks with distributed > collector > --------------------------------------------------------------------------------- > > Key: AMBARI-16828 > URL: https://issues.apache.org/jira/browse/AMBARI-16828 > Project: Ambari > Issue Type: Task > Components: amvari-me > Affects Versions: 2.4.1 > Reporter: Siddharth Wagle > Assignee: Siddharth Wagle > Fix For: 2.4.1 > > Attachments: AMBARI-16828.patch > > > - Initial set of collectors is configured in the configuration files > - Find available collectors by connecting to zookeeper thereafter > - Remember available collectors, refresh this information only when one > collector cannot be reached with a very low frequency of checks, example: > random interval between 10-12 minutes, check if a new collector is available. > Set a low client side zk timeout. > - Round robin the write between the collector choosing the first one at random > - If a write timed out, choose the next available collector, remember the > attempts with the first one > - Set a configurable attempt count for failed connector (default = 3), after > which the failed connector is no longer in the available collectors list. > - The next retry will be triggered after refresh with zookeeper is successful > - If no failed collectors available, zk refresh interval should be chosen > randomly between 1-2 minutes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)