Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 17 Sep 2012 16:31:07 +1100 (NCT)
From: "Mark Miller (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <835131115.86581.1347859867888.JavaMail.jiratomcat@arcas>
In-Reply-To: <990332848.86257.1347847267737.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (SOLR-3846) TestReplicationHandler.test always
 (?) takes many minutes on OS X (lion)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SOLR-3846?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13456=
772#comment-13456772 ]=20

Mark Miller commented on SOLR-3846:
-----------------------------------

Those threads are locked up good - stack traces in the attached stacks.txt =
file.
               =20
> TestReplicationHandler.test always (?) takes many minutes on OS X (lion)
> ------------------------------------------------------------------------
>
>                 Key: SOLR-3846
>                 URL: https://issues.apache.org/jira/browse/SOLR-3846
>             Project: Solr
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 4.0-BETA, 5.0
>         Environment: OS X (Lion). Apparently (see Yonik's notes) this doe=
s NOT happen on other op systems.
> java version "1.6.0_35"
> Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11M3811)
> Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)
> Solr trunk and 4.x from 16-Sep, but it's been happening for a couple of w=
eeks at least.
>            Reporter: Erick Erickson
>             Fix For: 4.0, 5.0
>
>         Attachments: stacks.txt
>
>
> Here's the seed was using, but this is apparently unnecessary:
> <JUnit4> says =C2=A1Hola! Master seed: 6785BB3284A15298
> _eventually_ it seems to complete, but it takes many minutes, for instanc=
e this was reported once, but I usually lose patience and ctrl-c out:
> {code}
> [junit4:junit4] Completed on J2 in 2449.62s, 1 test
> [junit4:junit4]=20
> [junit4:junit4] JVM J0:     1.21 ..   266.67 =3D   265.47s
> [junit4:junit4] JVM J1:     1.21 ..   238.33 =3D   237.12s
> [junit4:junit4] JVM J2:     1.21 ..  2538.60 =3D  2537.39s
> [junit4:junit4] JVM J3:     0.97 ..   267.37 =3D   266.40s
> [junit4:junit4] Execution time total: 42 minutes 18 seconds
> {code}
> and a lot of lines like:
> HEARTBEAT J2: 2012-09-16T17:38:38, no events in:  187s, approx. at: TestR=
eplicationHandler.test
> Yonik reports that he can make this happen 100% of the time on OS X/Lion,=
 which squares with my experience as I recall. Yonik also reports...
> On my linux box (built in '09, PhenomII, HDD) the test takes 50-55 sec.
> On my kids old windows box ('08, athlon64, HDD, Win7) the test takes 88-9=
5 sec.
> On my mac it always takes forever, and I see loops of stuff like this:
> {code}
> SEVERE Master at: http://localhost:62803/solr is not available. Index
> fetch failed. Exception:
> org.apache.solr.client.solrj.SolrServerException: Server refused
> connection at: http://localhost:62803/solr
> [junit4:junit4]   2> 52751 T219 C17 UPDATE [collection1] webapp=3D/solr
> path=3D/update params=3D{wt=3Djavabin&version=3D2} {add=3D[150]} 0 0
> [junit4:junit4]   2> 52755 T219 C17 UPDATE [collection1] webapp=3D/solr
> path=3D/update params=3D{wt=3Djavabin&version=3D2} {add=3D[151]} 0 0
> [junit4:junit4]   2> 62758 T215 oash.SnapPuller.fetchLatestIndex
> SEVERE Master at: http://localhost:62803/solr is not available. Index
> fetch failed. Exception:
> {code}
> And I'm soooo happy it's not happening to others and just being swept und=
er the rug, restores my faith. I should have known better ;)
> See the discussion on the dev list labeled "being a good citizen is hard =
when you can't successfully run tests" for more context.
> I don't know how much time I'll have to dive in to it but I'll certainly =
be happy to test anyone's patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org