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

Long cannot be cast to String in UpdateLog$LogReplayer

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Information Provided
    • 6.6
    • None
    • replication (java)
    • None

    Description

      A node could not recover last night due to it running out of diskspace. The node tried to pull the entire index over the wire but that failed. Just now i simply removed all index.YYYYMMDD... directories and restarted, this is what i got:

      java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.String
      	at org.apache.solr.common.util.JavaBinCodec.readSolrInputDocument(JavaBinCodec.java:571)
      	at org.apache.solr.common.util.JavaBinCodec.readObject(JavaBinCodec.java:310)
      	at org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:251)
      	at org.apache.solr.common.util.JavaBinCodec.readArray(JavaBinCodec.java:712)
      	at org.apache.solr.common.util.JavaBinCodec.readObject(JavaBinCodec.java:267)
      	at org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:251)
      	at org.apache.solr.update.TransactionLog$LogReader.next(TransactionLog.java:684)
      	at org.apache.solr.update.UpdateLog$LogReplayer.doReplay(UpdateLog.java:1591)
      	at org.apache.solr.update.UpdateLog$LogReplayer.run(UpdateLog.java:1513)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:229)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      

      Recovery was not a problem, it is running again.

      Attachments

        Activity

          People

            Unassigned Unassigned
            markus17 Markus Jelsma
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: