lucene - RCA needs more information, using Hibernate Search -


one of our customers, whom did custom development facing weird issue. though still in pre-uat, see not conforming known lucene behavior.

we using hibernate search 5.5.2, apache lucene 5.3.x; using filesystem index. running inside weblogic 12c container, oracle 12c database.

we have 2 different virtual machines host 2 different weblogic 12c instances (thereby application) point same database (thereby same data); @ start of application, index data on filesystem on each of nodes. same query, yields different results on each of nodes!

has faced similar issue? indexing mechanism in way tied hardware or specific machine? cannot fathom reason behavior.

also, next question if there non-replicated (no form of replication) clustered nodes (weblogic 12c) - ok index on each of nodes separately,the same data? or necessary use master-slave replication? not need answer maintainability point of view, rather view of correctness of results?

see original question on official hibernate search forum at: https://forum.hibernate.org/viewtopic.php?f=9&t=1043314

it appears if store index on each node containing data modified through node. query results vary depending on node executing query.

you should options clustered set-ups, master/slave set-up using jms or infinispan-based backend. both make sure there single index containing data.


Comments

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

scala - 'wrong top statement declaration' when using slick in IntelliJ -