Leaked port range from global sorting activities in child queries causing port clashes

Description

There could be various symptoms, but this is the kind of error seen relating to this issue:

ERROR: -7: tsortmp.cpp(518) : SortSlaveMP::marshall : port in use Target: S>192.168.253.50:20120, port = 20120, Raised in: jsocket.cpp, line 978

Conclusion

None

Activity

Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Created June 19, 2019 at 12:56 PM
Updated June 19, 2019 at 3:08 PM
Resolved June 19, 2019 at 3:08 PM

Flag notifications