• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ipfs / ipfs-cluster / 213
77%
master: 65%

Build:
Build:
LAST BUILD BRANCH: feat/expvar
DEFAULT BRANCH: master
Ran 02 Mar 2017 01:58PM UTC
Jobs 1
Files 20
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
213

push

travis-ci

hsanjuan
Issue #45: Detect expired metrics and trigger re-pins

An initial, simple approach to this. The PeerMonitor will
check it's metrics, compare to the current set of peers and put
an alert in the alerts channel if the metrics for a peer have expired.

Cluster reads this channel looking for "ping" alerts. The leader
is in charge of triggering repins in all the Cids allocated to
a given peer.

Also, metrics are now broadcasted to the cluster instead of pushed only
to the leader. Since they happen every few seconds it should be okay
regarding how it scales. Main problem was that if the leader is the node
going down, the new leader will not now about it as it doesn't have any
metrics for it, so it won't trigger an alert. If it acted on that then
the component needs to know it is the leader, or cluster needs to
handle alerts in complicated ways when leadership changes. Detecting
leadership changes or letting a component know who is the leader is another
dependency from the consensus algorithm that should be avoided. Therefore
we broadcast, for the moment.

License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>

159 of 159 new or added lines in 3 files covered. (100.0%)

2715 of 3532 relevant lines covered (76.87%)

1707.95 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
2
100.0
config.go
5
100.0
peer_monitor.go
6
100.0
cluster.go
Jobs
ID Job ID Ran Files Coverage
1 213.1 02 Mar 2017 01:58PM UTC 0
76.87
Travis Job 213.1
Source Files on build 213
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #213
  • cd09b702 on github
  • Prev Build on 45-peer-failure (#202)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc