You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2019/10/21 22:22:00 UTC
[jira] [Created] (SOLR-13856) 8.x
HdfsWriteToMultipleCollectionsTest jenkins failures due to TImeoutException
Chris M. Hostetter created SOLR-13856:
-----------------------------------------
Summary: 8.x HdfsWriteToMultipleCollectionsTest jenkins failures due to TImeoutException
Key: SOLR-13856
URL: https://issues.apache.org/jira/browse/SOLR-13856
Project: Solr
Issue Type: Test
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Chris M. Hostetter
I've noticed a trend in jenkins failures where HdfsWriteToMultipleCollectionsTest...
* does _NOT_ ever seem to fail on master even w/heavy beasting
* fails on 8.x (28c1049a258bbd060a80803c72e1c6cadc784dab) and 8.3 (25968e3b75e5e9a4f2a64de10500aae10a257bdd) easily
** failing seeds frequently reproduce, but not 100%
** seeds reproduce even when tested using newer (ie: java11) JVMs
** doesn't fail when commenting out HDFS aspects of test
*** suggests failure cause is somehow specific to HDFS, not differences in the 8x/master HTTP/solr indexing stack...
*However:* There are currently zero differences between the *.hdfs.* packaged solr code (src or test) on branch_8x vs master; likewise 8x and master also use the exact same hadoop jars.
So what the hell is different?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org