You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a lot of replication tests I get "No buffer space available" error. Path I have is not so long really, but the path added by test-run is quite big. Here is an example: unix/:/Users/gerold/Work/Repositories/tarantool/test/var/010_replication/replica-applier-rollback.socket-admin. This exceeds 108 bytes path limit (there is 110 symbols). Maybe we at least could stop adding script name to the socket name, or make socket-admin part shorter somehow.
The text was updated successfully, but these errors were encountered:
However we can do some tricks: say, chdir into a directory and fill sun_path with just name w/o a full path. It works at least on Linux. This looks weird, however will be helpful in some cases.
That is getting worse - when run tests from ee, it adds tarantool-ee/ into the path making it even longer. As a result, I get this warning:
WARGING: unix sockets can become longer than 107 symbols:
WARNING: for example: "/Users/gerold/Work/Repositories/tarantool-ee/tarantool/test/var/???_replication/autobootstrap_guest3.control" has length 108
For a lot of replication tests I get "No buffer space available" error. Path I have is not so long really, but the path added by test-run is quite big. Here is an example:
unix/:/Users/gerold/Work/Repositories/tarantool/test/var/010_replication/replica-applier-rollback.socket-admin
. This exceeds 108 bytes path limit (there is 110 symbols). Maybe we at least could stop adding script name to the socket name, or makesocket-admin
part shorter somehow.The text was updated successfully, but these errors were encountered: