[Spread-users] Bug in SP_connect_timeout?

[John Lane Schultz]

Arkady,

This is not a bug.  This is a limitation of the current events system’s implementation that is properly enforced.  Some platforms (e.g. - win32) allow you to redefine FD_SETSIZE before select() is declared to allow select to handle more file descriptors.  If you want to try that, then you can do it in libspread-util/src/arch.h  However, if your maximum fd number is very high, then select and the event system may not perform very well.

Not all platforms have epoll.  If you want to contribute your code to the project for consideration for inclusion in Spread, then you can follow the instructions here:

http://www.spread.org/devel.html

Cheers!

-----
John Lane Schultz
Spread Concepts LLC
Cell: 443 838 2200

On Dec 8, 2016, at 2:43 AM, Arkady Lipovetsky <arkady at peerapp.com> wrote:

Hi, guys I have encountered a BUG in spread user interface that is intended for asynchronous working (event system). The mechanism is implemented on "select" call, but this call has some limitation such as a max file descriptor that is 1024. The spread check this value and generate an error if file descriptor more than 1024. In my local version I has solved this issue by using epoll system call instead select. We are using a huge number for file descriptors, so if  number of used file descriptors is more than 1024 (it happens at spread reconnection time we get an Error). I checked all previous version and found that this BUG exists in all of them.

Thanks