This looks like a bug in elasticsearch-analysis-combo, I'd post it as an issue there
-- Itamar Syn-Hershko http://code972.com | @synhershko <https://twitter.com/synhershko> Freelance Developer & Consultant Lucene.NET committer and PMC member On Fri, Mar 13, 2015 at 1:35 PM, Angel Cross <niegi...@gmail.com> wrote: > Hello. > Recently in our test system we started to notice the following exception. > Googling and investigation of setup itself didn't make it more clear. Still > have no idea why is this happening. Maybe somebody already faced the issue > and knows the reason? Or have any ideas? > > > java.lang.IllegalArgumentException: State contains AttributeImpl of type > org.apache.lucene.analysis.tokenattributes.PayloadAttributeImpl that is not > in in this AttributeSource > at > org.apache.lucene.util.AttributeSource.restoreState(AttributeSource.java:313) > at > org.apache.lucene.analysis.ComboTokenStream.incrementToken(ComboTokenStream.java:106) > at > org.apache.lucene.index.DefaultIndexingChain$PerField.invert(DefaultIndexingChain.java:618) > at > org.apache.lucene.index.DefaultIndexingChain.processField(DefaultIndexingChain.java:359) > at > org.apache.lucene.index.DefaultIndexingChain.processDocument(DefaultIndexingChain.java:318) > at > org.apache.lucene.index.DocumentsWriterPerThread.updateDocument(DocumentsWriterPerThread.java:239) > at > org.apache.lucene.index.DocumentsWriter.updateDocument(DocumentsWriter.java:457) > at > org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1511) > at > org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:1246) > at > org.elasticsearch.index.engine.internal.InternalEngine.innerIndex(InternalEngine.java:594) > at > org.elasticsearch.index.engine.internal.InternalEngine.index(InternalEngine.java:522) > at > org.elasticsearch.index.shard.service.InternalIndexShard.index(InternalIndexShard.java:425) > at > org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(TransportShardBulkAction.java:439) > at > org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:150) > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:512) > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:419) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > > elastic configuration > elasticsearch 1.4.3 > plugins > elasticsearch-analysis-baseform > <https://github.com/jprante/elasticsearch-analysis-baseform> - version > 1.4.0 > elasticsearch-analysis-kuromoji > <https://github.com/elasticsearch/elasticsearch-analysis-kuromoji> - > version 2.4.2 > elasticsearch-analysis-combo/ > <https://github.com/yakaz/elasticsearch-analysis-combo/> -version 1.5.1 > elasticsearch-analysis-decompound > <https://github.com/jprante/elasticsearch-analysis-decompound> - version > for 1.0.0RC1 > elasticsearch-analysis-icu > <https://github.com/elasticsearch/elasticsearch-analysis-icu> - version > 2.4.2 > elasticsearch-analysis-smartcn > <https://github.com/elasticsearch/elasticsearch-analysis-smartcn> > -version 2.4.3 > elasticsearch-head/ <http://mobz.github.io/elasticsearch-head/> - the > last one > server(1 machine) works with 2 nodes. One of then is data node, another is > tribe node. Nodes are running on different ports and differs in > configuration. > Server OS ir RedHat 6.5 > > Exception appears when we try to reindex of document containing nested > documents. Indexing is happening via bulks. So this is not update but > actually another index request for the existing document with the same id. > This exception doesn't appear on another Centos machine and another RedHat > machine with similar setup. We reinstalled Elastic on test machine, still > no difference. > > Thanks, Liuba > > > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/d3f18bae-4df7-4563-9fc4-59d87cd1a50b%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/d3f18bae-4df7-4563-9fc4-59d87cd1a50b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZutRPS6bGNHQrQ5dU6BEnSoqnwz%3D_7zT4G0qAO%2BzcVniQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
