[
https://issues.apache.org/jira/browse/LUCENE-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948067#comment-13948067
]
Steve Rowe commented on LUCENE-5556:
------------------------------------
bq. Thankfully, everything went smoothly the second go-around.
Actually, I misspoke: the remote {{chmod}} command failed after successfully
transferring the files. Maybe we should retry that?
> buildAndPushRelease.py: scp to people.apache.org stalls during transfer
> -----------------------------------------------------------------------
>
> Key: LUCENE-5556
> URL: https://issues.apache.org/jira/browse/LUCENE-5556
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Steve Rowe
> Priority: Minor
>
> When I first tried to build the first RC for 4.7.1 using
> {{dev-tools/scripts/buildAndPushRelease.py}}, after preparing both the Lucene
> and Solr releases, the {{scp}} command to transfer the Lucene release tarball
> to people.apache.org stalled after about 180MB had transferred out of 220MB.
> After an hour or so, I {{kill -9}}'d the {{scp}} process and started over.
> Thankfully, everything went smoothly the second go-around.
> But I'd like to see if we can reduce the likelihood of this happening again.
> I did some searching for causes/solutions to this problem and came across
> this recommendation to use {{scp}}'s {{-l}} option to limit bandwidth in
> order to prevent stalls: [http://www.aixmind.com/?p=1371] - the
> recommendation there limits bandwidth to 1MB/sec ({{-l 8192}} is 8192Kbit/sec
> = 8Mbit/sec = 1MB/sec).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
