Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[yfernando]

The above error appears to be an issue in
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot in a
mismatch between the readExternal() and writeExternal() methods.

I've made a change locally and it fixed the error and also the testing so
far seems to show that the queries return the correct results (so it's
likely that the cause may have been
https://issues.apache.org/jira/browse/IGNITE-8900)

If you would like me to contribute the fix back to the ignite codebase
please let me know and i'll be happy to do it



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[yfernando]

Thanks Vlad / Dmitry, I was able to download the nightly build from teamcity
as a guest.

However I'm now getting the following error when trying to add data to the
cache. Any ideas?

class org.apache.ignite.IgniteException: Failed to get affinity mapping from
node: TcpDiscoveryNode [id=eeef1e32-db85-4425-8718-29884d9af6d0,
addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 10.32.50.59, 127.0.0.1],
sockAddrs=HashSet [/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500,
appl183-stc.global.tudor.com/10.32.50.59:47500], discPort=47500, order=3,
intOrder=3, lastExchangeTime=1534414697561, loc=false,
ver=2.7.0#19691231-sha1:, isClient=false]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityRunAsync0(IgniteComputeImpl.java:186)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityRun(IgniteComputeImpl.java:145)
at
com.tudor.datagridI.client.TradeOrderStoreHelper.processOrderHolders(TradeOrderStoreHelper.java:30)
at
com.tudor.datagridI.TradingDataAccessImpl.saveOrders(TradingDataAccessImpl.java:294)
at
orderserver.client.GridClient.updatePreparedOrderHoldersInGrid(GridClient.java:180)
at
orderserver.client.GridClient.updateOrderHoldersInGrid(GridClient.java:135)
at orderserver.OrderFactory.saveOrders(OrderFactory.java:6705)
at orderserver.OrderFactory.saveOrders(OrderFactory.java:6620)
at
com.tudor.test.performancetest.PerformanceTester$CurrencyBooker.run(PerformanceTester.java:286)
at
java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
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)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get
affinity mapping from node: TcpDiscoveryNode
[id=eeef1e32-db85-4425-8718-29884d9af6d0, addrs=ArrayList
[0:0:0:0:0:0:0:1%lo, 10.32.50.59, 127.0.0.1], sockAddrs=HashSet
[/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500,
appl183-stc.global.tudor.com/10.32.50.59:47500], discPort=47500, order=3,
intOrder=3, lastExchangeTime=1534414697561, loc=false,
ver=2.7.0#19691231-sha1:, isClient=false]
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:515)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:342)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityRunAsync0(IgniteComputeImpl.java:176)
... 12 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
unmarshal object with optimized marshaller
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10025)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:830)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1077)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1312)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
... 3 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
unmarshal object with optimized marshaller
at
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1765)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1964)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:102)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10019)
... 10 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
deserialize object with given class loader:
[clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, err=Failed to deserialize
object [typeName=org.apache.ignite.internal.util.lang.GridTuple3]]
at

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[Vladimir Ozerov]

Dmitriy,

I wanted to suggest this, but looks like we do not have direct links for
regular distribution. User can download it from TeamCity, but
username/password is needed for this. May be I missing something.

On Thu, Aug 16, 2018 at 11:44 AM Dmitriy Setrakyan 
wrote:

> I also want to point out that Ignite has nightly builds, so you can try
> them instead of doing your own build as well.
>
> https://ignite.apache.org/download.cgi#nightly-builds
>
> D.
>
> On Thu, Aug 16, 2018 at 1:38 AM, Vladimir Ozerov 
> wrote:
>
>> Hi,
>>
>> There were a lot of changes in the product since 2.3 which may affect it.
>> Most important change was baseline topology, as already mentioned.
>> I am aware of a case when incorrect result might be returned [1], which
>> is already fixed in *master*. Not sure if this is the same issue, but
>> you may try to build Ignite from recent master and check if the problem is
>> still there.
>>
>> Is it possible to create isolated reproducer for this issue?
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-8900
>>
>> On Wed, Aug 15, 2018 at 11:34 PM bintisepaha 
>> wrote:
>>
>>> Thanks for getting back, but we do not use Ignite's native persistence.
>>> Anything else changed from 2.3 to 2.4 to cause this around SQL Queries?
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>
>

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[Dmitriy Setrakyan]

I also want to point out that Ignite has nightly builds, so you can try
them instead of doing your own build as well.

https://ignite.apache.org/download.cgi#nightly-builds

D.

On Thu, Aug 16, 2018 at 1:38 AM, Vladimir Ozerov 
wrote:

> Hi,
>
> There were a lot of changes in the product since 2.3 which may affect it.
> Most important change was baseline topology, as already mentioned.
> I am aware of a case when incorrect result might be returned [1], which is
> already fixed in *master*. Not sure if this is the same issue, but you
> may try to build Ignite from recent master and check if the problem is
> still there.
>
> Is it possible to create isolated reproducer for this issue?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8900
>
> On Wed, Aug 15, 2018 at 11:34 PM bintisepaha 
> wrote:
>
>> Thanks for getting back, but we do not use Ignite's native persistence.
>> Anything else changed from 2.3 to 2.4 to cause this around SQL Queries?
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[Vladimir Ozerov]

Hi,

There were a lot of changes in the product since 2.3 which may affect it.
Most important change was baseline topology, as already mentioned.
I am aware of a case when incorrect result might be returned [1], which is
already fixed in *master*. Not sure if this is the same issue, but you may
try to build Ignite from recent master and check if the problem is still
there.

Is it possible to create isolated reproducer for this issue?

[1] https://issues.apache.org/jira/browse/IGNITE-8900

On Wed, Aug 15, 2018 at 11:34 PM bintisepaha  wrote:

> Thanks for getting back, but we do not use Ignite's native persistence.
> Anything else changed from 2.3 to 2.4 to cause this around SQL Queries?
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[bintisepaha]

Thanks for getting back, but we do not use Ignite's native persistence.
Anything else changed from 2.3 to 2.4 to cause this around SQL Queries? 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[akurbanov]

Hi,

Do you use persistence? If so, please check and set up  Baseline topology
   for your cluster
which describes a set of server nodes that are used to store data. The
reason for this behaviour may be a simple fact that some of your nodes are
out of baseline topology.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[bintisepaha]

Hi, we have used this query in ignite 2.3 for a while now. But we had some
data streamer exceptions that seemed to have been resolved on 2.4, so we
decided to upgrade. However, in 2.6 and also downgrading to 2.4 we have been
seeing this issue, that a SQL query does not return the data that is in
cache. when we go back to 2.3, it works as expected.

Here is the cache config for that cache.



 










































traderId

orderId






SORTED









traderId

insIid

clearAgent

strategy






SORTED




  




parentId






SORTED











and here is the query

public List getTradeOrdersForPSGroup(Integer traderId, Short
psRuleId, Integer tid, String clearAgent, String strategy, Integer pvId,
Date settlementDate, Date psTime) {
logger.info(String.format("Getting TradeOrders from the cache 
for
traderId: %s, tid: %s, clearAgent: %s, strategy: %s, pvId: %s, settlement:
%s, psTime: %s", traderId, tid, clearAgent, strategy, pvId, settlementDate,