Consul vs Pacemaker

797 views
Skip to first unread message

Chaman Bagga

unread,
Jan 29, 2016, 6:32:38 AM1/29/16
to Consul

Hello,

Looking at consul documentation, there is comparison with etcd, zookeeper etc. However, its not clear how consul and pacemaker differ.

Can someone point out please?

---Chaman.

Armon Dadgar

unread,
Jan 29, 2016, 8:20:20 PM1/29/16
to consu...@googlegroups.com, Chaman Bagga
Chaman,

The two differ in scope. Pacemaker is really only designed to do membership and failure detection
at small scale (< 50 nodes). Consul provides a much broader scope of features including
service discovery, key value, and coordination (including leader election and failure detection),
but is designed to operate at much larger scale. 

Hope that helps!

Best Regards,
Armon Dadgar
--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/consul/issues
IRC: #consul on Freenode
---
You received this message because you are subscribed to the Google Groups "Consul" group.
To unsubscribe from this group and stop receiving emails from it, send an email to consul-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/consul-tool/79014b33-946e-4ea8-98fc-a960d340fffb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Chaman Bagga

unread,
Feb 27, 2016, 6:16:31 AM2/27/16
to Consul, chama...@gmail.com

Thanks.

Does Consul also offer failover support like pacemaker does (e.g. using Virtual IP for failover)?

I have a few services that use VIP for failover today, and my clients use hardcoded IP, so VIP is a necessity. 

Armon Dadgar

unread,
Feb 28, 2016, 1:50:25 PM2/28/16
to consu...@googlegroups.com, Chaman Bagga, chama...@gmail.com
Chaman,

Take a look at the “consul lock” command (https://www.consul.io/docs/commands/lock.html) for easily
doing fail over between services. That is based on the Consul implementation of leader election under

Consul does not implement it at the VIP layer however, it is implemented much higher up the stack,
as it is designed to work in environments without VIP (e.g. public cloud environments).

Hope that helps!

Best Regards,
Armon Dadgar

Reply all
Reply to author
Forward
0 new messages