Thanks for the reply,
I would change the default value under /etc/salt/master.
I have also seen that in /etc/salt/minion file one option like
"tcp_keepalive_idle: 300". 5 min is it's default value. When I checked with
TCPdump, all minions sending keep alive request after every 5 min. So I
think when master runs this command "*salt mysql1.dev.example.net
<
http://mysql1.dev.example.net/>' highstate*", then it is responding back
to request (keep-alive) made by specific/all minions.
*About ZeroMQ:*
I have heard that ZeroMQ has higher throughput than TCP even though it's
built on top of TCP. It may be because of technique known as message
batching. If I'm correct then how this technique is used in SALT? OR how
does salt works with zeroMQ?
Master receives all request (keep-alive) on port 4505 and responds back to
minions using port 4506,
I think on port 4505 it en-queue all request came from minions and responds
back to same request using port 4506.
They might be checking file checksum on master as well as minions to check
check any changes occurred, if not then execute the same on minions.
These are all my assumptions. Please let us know these are correct or
wrong.
Best,
--Pankaj
On Tuesday, 19 August 2014 14:43:48 UTC+5:30, Sebastien Wains wrote:I've had the same no output issue. I now run salt with "-t 300", which
changes the timeout to 300 seconds from 5 by default.
You can change the default under /etc/salt/master.
On Monday, August 18, 2014 11:16:01 AM UTC+2, pankaj ghadge wrote:Hi All,
I have few queries related to ZeroMQ and Salt communication.
- How does the bi-directional communication happens between Master
and minions?
- Does Linux system (on minions ) allows bi-directional communication
with master without opening any port with the help of ZeroMQ? so now I'm
wondering how it works?
As it requires to open ports 4505 and 4506 on Master, but not on minions.
Does the minions continuously sends some kind on flag to master and when
master wants to communicate with minions that flag changes to something
'Yes' and minions execute "salt-call state.highstate"?
When I run "*salt mysql1.dev.example.net
<
http://mysql1.dev.example.net>' highstate -l debug"* from master then
sometimes it returns following. It shows no output.
[DEBUG ] get_returns for jid 20140814072556876709 sent to set(['
mysql1.dev.example.net']) will timeout at 07:25:58
[INFO ] jid 20140814072556876709 minions set(['mysql1.dev.example.net'])
did not return in time
How does the salt achieve high-speed with ZeroMQ and as ZeroMQ is used
for high speed. it must have few drawbacks as well?
--Thanks
Pankaj.
--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
