Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-8049

MorphlineGoLiveMiniMRTest is failing about 50% of the time on my local Jenkins machine.

    XMLWordPrintableJSON

    Details

      Description

      I am seeing two fails:

      java.lang.AssertionError: expected:<0> but was:<-1>
      	at __randomizedtesting.SeedInfo.seed([7AEAA2B65C8B6219:F2BE9D6CF2770FE1]:0)
      	at org.junit.Assert.fail(Assert.java:93)
      	at org.junit.Assert.failNotEquals(Assert.java:647)
      	at org.junit.Assert.assertEquals(Assert.java:128)
      	at org.junit.Assert.assertEquals(Assert.java:472)
      	at org.junit.Assert.assertEquals(Assert.java:456)
      	at org.apache.solr.hadoop.MorphlineGoLiveMiniMRTest.test(MorphlineGoLiveMiniMRTest.java:551)

      and

      java.io.IOException: java.net.ConnectException: Call From fullmetal/127.0.1.1 to fullmetal:0 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused
      	at __randomizedtesting.SeedInfo.seed([D236ECA21D1ECF9C:5A62D378B3E2A264]:0)
      	at org.apache.hadoop.mapred.ClientServiceDelegate.invoke(ClientServiceDelegate.java:337)
      	at org.apache.hadoop.mapred.ClientServiceDelegate.getJobStatus(ClientServiceDelegate.java:422)
      	at org.apache.hadoop.mapred.YARNRunner.getJobStatus(YARNRunner.java:575)
      	at org.apache.hadoop.mapreduce.Job$1.run(Job.java:325)
      	at org.apache.hadoop.mapreduce.Job$1.run(Job.java:322)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at javax.security.auth.Subject.doAs(Subject.java:422)
      	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
      	at org.apache.hadoop.mapreduce.Job.updateStatus(Job.java:322)
      	at org.apache.hadoop.mapreduce.Job.isComplete(Job.java:610)
      	at org.apache.solr.hadoop.MorphlineGoLiveMiniMRTest.test(MorphlineGoLiveMiniMRTest.java:404)
      

      The first issue requires digging into the job logs to see what is actually going wrong.

      The second may mean we need to raise the connect timeout YARN is using if possible.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                markrmiller@gmail.com Mark Miller
                Reporter:
                markrmiller@gmail.com Mark Miller
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: