test: use unix sockets for iproto connections
Enabled use_unix_sockets_iproto option to use unix sockets iproto provides the new way to handle the problem with 'Address already in use' error. It lets test-run appoint unix sockets for LISTEN environment variable values. Before this change the TcpPortDispatcher was used to eliminate the race condition when two workers trying to use the same port: the idea was that each worker used its own ports range. Really these ports could race with client ports (from, say, net.box or replication), which typically didn't use bind() and so bound to a random available port (despite any dispatched ranges) and could produce 'Address already in use' error. Closes: #4008 (cherry picked from commit 60f84cbf)
Showing
- test/app/suite.ini 1 addition, 0 deletionstest/app/suite.ini
- test/box/suite.ini 1 addition, 0 deletionstest/box/suite.ini
- test/engine/suite.ini 1 addition, 0 deletionstest/engine/suite.ini
- test/engine_long/suite.ini 1 addition, 0 deletionstest/engine_long/suite.ini
- test/long_run-py/suite.ini 1 addition, 0 deletionstest/long_run-py/suite.ini
- test/replication/status.result 5 additions, 5 deletionstest/replication/status.result
- test/replication/status.test.lua 3 additions, 3 deletionstest/replication/status.test.lua
- test/replication/suite.ini 1 addition, 0 deletionstest/replication/suite.ini
- test/vinyl/suite.ini 1 addition, 0 deletionstest/vinyl/suite.ini
- test/wal_off/suite.ini 1 addition, 0 deletionstest/wal_off/suite.ini
- test/xlog-py/suite.ini 1 addition, 0 deletionstest/xlog-py/suite.ini
- test/xlog/suite.ini 1 addition, 0 deletionstest/xlog/suite.ini
Loading
Please register or sign in to comment