Reputation
233
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 3 9
Impact
~24k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Apr
25
comment Connection refused to local port
I'm so embarrassed....
Apr
25
accepted Connection refused to local port
Apr
25
comment Connection refused to local port
Oh god, I see that typo now... I kind of hope that's the issue, but also not the issue. :( I'll check.
Apr
25
revised Connection refused to local port
edited body
Apr
24
revised Connection refused to local port
added 345 characters in body
Apr
24
asked Connection refused to local port
Nov
17
awarded  Famous Question
Dec
8
awarded  Popular Question
Jul
2
awarded  Curious
Jan
28
awarded  Yearling
Sep
24
revised Graphite/Carbon cluster returning incomplete data
added 4 characters in body
Sep
24
answered Graphite/Carbon cluster returning incomplete data
Sep
24
comment Graphite/Carbon cluster returning incomplete data
Being able to scale out is a requirement; our Graphite cluster is running in the cloud, and if we lose an instance, we lose our data, so scaling-out for redundancy (replication) is necessary (even if only to two small nodes.) This cluster is designed exactly how you described in your last paragraph: ELB pointing to two nodes with consistent hashing. Actually, as it turns out, there was a typo in the configuration, and each relay was pointing to the caches and not the other relays. Having fixed that, it is now actually doing what is in the diagram above, storing and replicating properly.
Sep
24
revised Graphite/Carbon cluster returning incomplete data
added 158 characters in body
Sep
24
comment How do you delete a counter in graphite whisper?
Did you ever find an answer for this? Suffering from the same problem.
Sep
23
asked Graphite/Carbon cluster returning incomplete data
Mar
27
awarded  Notable Question
Mar
27
awarded  Popular Question
Mar
27
awarded  Scholar
Mar
27
awarded  Supporter