I've found commit 9b9a682fe035c985e416ee1c112fa58f9045a27c and I see
that when 'osd heartbeat use min delay socket = true' it will mark the
packet with DSCP CS6. Based on the setting of the socket in
msg/simple/Pipe.cc is it possible that this can apply to both OSD and
monitor? I don't understand
Jian,
Thanks for the clarification. I'll mark traffic destined for the
monitors as well. We are getting ready to put our first cluster into
production. If you are interested we will be testing the heartbeat
priority to see if we can saturate the network (not an easy task for
40 Gb) and keep the
Only OSD calls set_socket_priority().
See https://github.com/ceph/ceph/pull/3353
On Tue, Mar 10, 2015 at 3:36 AM, Robert LeBlanc rob...@leblancnet.us wrote:
I've found commit 9b9a682fe035c985e416ee1c112fa58f9045a27c and I see
that when 'osd heartbeat use min delay socket = true' it will mark
Judging by the commit, this ought to do the trick:
osd heartbeat use min delay socket = true
On 07/03/15 01:20, Robert LeBlanc wrote:
I see that Jian Wen has done work on this for 0.94. I tried looking
through the code to see if I can figure out how to configure this new
option, but it all
I see that Jian Wen has done work on this for 0.94. I tried looking through
the code to see if I can figure out how to configure this new option, but
it all went over my head pretty quick.
Can I get a brief summary on how to set the priority of heartbeat packets
or where to look in the code to
I'm looking for a way to prioritize the heartbeat traffic higher than the
storage and replication traffic. I would like to keep the ceph.conf as
simple as possible by not adding the individual osd IP addresses and ports,
but it looks like the listening ports are pretty random. I'd like to use
On Wed, 27 Aug 2014, Robert LeBlanc wrote:
I'm looking for a way to prioritize the heartbeat traffic higher than the
storage and replication traffic. I would like to keep the ceph.conf as
simple as possible by not adding the individual osd IP addresses and ports,
but it looks like the
On Wed, Aug 27, 2014 at 4:15 PM, Sage Weil sw...@redhat.com wrote:
On Wed, 27 Aug 2014, Robert LeBlanc wrote:
I'm looking for a way to prioritize the heartbeat traffic higher than the
storage and replication traffic. I would like to keep the ceph.conf as
simple as possible by not adding
- Sage Weil sw...@redhat.com wrote:
What would be best way for us to mark which sockets are heartbeat
related?
Is there some setsockopt() type call we should be using, or should we
perhaps use a different port range for heartbeat traffic?
Would be be plausible to have hb messengers
