Open jagafirst opened 7 years ago
Thanks for including the version, but this is not a lot of information to go on. Perhaps you could elaborate with the following information:
Updating to the current release wouldn't hurt.
I'm seeing this as well. I am using 1.8.0 GO on linux, transport is ssh://. To test, I created a repo on the server and populated it with about 2GB data. When I git clone this repo on 3 machines concurrently, they are serviced in the order in which the git clone were started.
@mmahann Try increasing the value of git.sshCommandStartThreads
.
Default appears to be 2. Set to 4. Then started two concurrent git clone. First one starts clone, second one waits for first. If I stop first, second continues with clone. Set to 400, same result.
I did the same experiment but used the http:// transport; both clones execute concurrently so this must be centered around ssh:// transport.
Right, it should be that setting (requires a restart to apply). Are you sure your config file is being properly loaded?
Agreed that a restart is required. I've set it in both gitblit.properties and defaults.properties (just in case). I have rebooted and I know that my config files are being properly loaded because I assigned different http/https port numbers in gitblit.properties and I can reach the service on those ports.
Could be related or the same issue as in #1285.
Gitblit is not responding when clone a repository until clone finished I am using gitblit version v1.6.0