Hi Nikolai, By saying:
> This exception means that in during data streaming, topology was changed. Do you mean major topology or minor topology? And also what is minor topology? We have encountered same issue without no change in topology version no new nodes added or left but with different minorTopVer. On Mon, Apr 3, 2017 at 5:39 PM, Nikolai Tikhonov <ntikho...@apache.org> wrote: > Hi, > > It's looks that you have long gc pause in your application. Did you see in > logs any message related with changing topology (node fail, node left, node > join and etc)? Could you enable gc logs and check it (for example > -Xloggc:./gc.log -XX:+PrintGCDetails -verbose:gc)? > > On Sun, Apr 2, 2017 at 1:36 PM, rishi007bansod <rishi007ban...@gmail.com> > wrote: > >> Hi, >> I am running 3 instances of ignite per machine(total 3 machines). Data is >> inserted in partitioned cache continuously and I am running query against >> this cache. After query I am getting above error. Is there any way I can >> make topology stable before querying data? For example, how can I query >> data >> up to certain snapshot of cache when data is continuously getting added >> and >> I am querying data to avoid this error(As this error only occurs during >> run >> time query against data i.e. when cache is getting populated and not when >> cache is completely loaded) >> >> Thanks. >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Error-while-running-query-against-Ignite- >> Server-Node-tp11030p11643.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > -- Alper Tekinalp Software Developer Evam Streaming Analytics Atatürk Mah. Turgut Özal Bulv. Gardenya 5 Plaza K:6 Ataşehir 34758 İSTANBUL Tel: +90 216 455 01 53 Fax: +90 216 455 01 54 www.evam.com.tr <http://www.evam.com>
