Could not clear historyMap due to WAL reservation on cp

[shivakumar]

Hi 
I have deployed 5 node Ignite cluster on K8S with persistence enabled
(version 2.9.0 on java 11)
I started ingesting data to 3 tables and after ingesting large amount of
data using JDBC batch insertion (around 20 million records to each of 3
tables with backup set to 1), now i connected to visor shell (from one of
the pod which i deployed just to use as visor shell) using the same ignite
config file which is used for ignite servers and after visor shell connects
to ignite cluster the unwanted wal record cleanup stopped (which should run
post checkpoint ) and WAL started growing linearly as there is continuous
data ingestion. This is making WAL disk run out of space and pods crashes.

when i see logs there are continuous warning messages saying 
Could not clear historyMap due to WAL reservation on cp: CheckpointEntry
[id=e8bb9c22-0709-416f-88d6-16c5ca534024, timestamp=1606979158669,
ptr=FileWALPointer [idx=1468, fileOff=45255321, len=9857]], history map size
is 4


and if i see checkpoint finish messages 
 
Checkpoint finished [cpId=ca254956-5550-45d6-87c5-892b7e07b13b,
pages=494933, markPos=FileWALPointer [idx=1472, fileOff=72673736, len=9857],
walSegmentsCleared=0, walSegmentsCovered=[1470 - 1471], markDuration=464ms,
pagesWrite=8558ms, fsync=3597ms, total=14027ms]

here you can see walSegmentsCleared=0   means there are no WAl segments
cleared even after checkpoint, not sure what is causing this behaviour.

we are ingesting very large data (~25mb/s)
please someone help in this issue 


regards,
Shiva





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

Re: C# CacheStoreAdapter - Customizing Load, LoadCache methods

[vtchernyi]

Hi,I do not use SQL because my interest is to get max performance, I use key-value API instead. The same reason is why I use Java - it is native for Ignite. I think there should be wrappers forBinaryObject and Affinity in c#.Vladimir 4:39, 3 декабря 2020 г., adumalagan :I see, thanks for the clarification! I also have another question - are there C# equivalencies to the Javainterfaces BinaryObject and Affinity?-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/-- Отправлено из мобильного приложения Яндекс.Почты

Re: C# CacheStoreAdapter - Customizing Load, LoadCache methods

[adumalagan]

I see, thanks for the clarification! 

I also have another question - are there C# equivalencies to the Java
interfaces BinaryObject and Affinity?



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

Re: C# CacheStoreAdapter - Customizing Load, LoadCache methods

[Denis Magda]

Yes, once the data is loaded into Ignite you can query it with SQL.

-
Denis


On Wed, Dec 2, 2020 at 9:41 AM adumalagan  wrote:

> Hi Vlad, I've started to read through your link and I just wanted to know
> that, if I were to implement your tutorial, could I perform SQL queries on
> the cache after loading?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: ThinClient issues

[akorensh]

Hi, 
  The connection parameters are set by the thin client connector.
see:
https://ignite.apache.org/docs/latest/thin-clients/getting-started-with-thin-clients#configuring-thin-client-connector

 all attributes are listed here:

https://ignite.apache.org/releases/2.9.0/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html
see:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#getThreadPoolSize--
(this specifies the number of threads set to process client requests)

Simple C++ put/get example:
https://github.com/apache/ignite/blob/master/modules/platforms/cpp/examples/thin-client-put-get-example/src/thin_client_put_get_example.cpp

connection resources should released when you destroy the IgniteClient
object.

monitor the Server logs to see what is happening.
see if the app is still connected using netstat.

try to connect via other thin clients to see if connection requests are
honored or not.

Thanks, Alex



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

Re: Using different versions of serializable objects

[Surkov.Aleksandr]

no, because we use third party classes and cannot change them



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

ThinClient issues

[Wolfgang Meyerle]

Hi,

today I tried to use the thin client to connect to two server nodes and 
test the performance.


Basically I tried to push random data from nodes where the Ignite 
database is not running.


I used the put_all method of the c++ thin client api to do that with 
concurrent threads.


However after a short amount of time I get connection problems and there 
does not seem to be a disconnect or close connection method available by 
the API.


Therefore I tried to create the thin client and the configuration as a 
pointer with new and deleted them in case of errors safely.


Each thread has its own client and configuration instance.

For some reason the client is however unable to reconnect.

Can somebody explain me why?

Is there a connection limit set by the default configuration so that the 
number of nodes and threads is limited in some way?

What am I doing wrong?
As there are no examples online available for the thinclient where I can 
further dig in this is very difficult.


I tried to look at the thin client c++ code and there is indeed a close 
function but this is not visible to the outside world for usage


Regards,

Wolfgang

Re: Using different versions of serializable objects

[Surkov.Aleksandr]

If I delete only methods (leave the interface), then there are no errors.



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

Re: C# CacheStoreAdapter - Customizing Load, LoadCache methods

[adumalagan]

Hi Vlad, I've started to read through your link and I just wanted to know
that, if I were to implement your tutorial, could I perform SQL queries on
the cache after loading?



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

Re: Using different versions of serializable objects

[Ilya Kasnacheev]

Hello!

Does it solve your issue?

Regards,
-- 
Ilya Kasnacheev


ср, 2 дек. 2020 г. в 16:50, Surkov.Aleksandr :

> If I delete only methods (leave the interface), then there are no errors.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Why does TextQuery failed to find result

[siva]

Hi,
Thanks for the reply.
I am already using Thick client.But not able to get result from Cache
Query.And it's returning empty result.

Quite i didn't understand wrap TextQuery call in a Service or Compute Task
from the above refrence.

can you please provide little bit more context on this.

Thanks.



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

Using different versions of serializable objects

[Surkov.Aleksandr]

Hi igniters!

We use third party classes and store them objects in key-value cache.
This class implements the Serializable interface and defines the readObject
and writeObject methods.

After we decided to switch to a new version of the class and tried to read
from the cache, we received an error:

Exception in thread "main" javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Failed to unmarshal object with
optimized marshaller
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1317)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2066)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1093)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:676)
at
com.client.SerializableTest.main(SerializableTest.java:27)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
unmarshal object with optimized marshaller
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7510)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:191)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4972)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4931)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1486)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1090)
... 2 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:1785)
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1991)
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1816)
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1807)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.unmarshal(GridBinaryMarshaller.java:268)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.unmarshal(CacheObjectBinaryProcessorImpl.java:1100)
at
org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:89)
at
org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:176)
at
org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:136)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1808)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1796)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:747)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:624)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:374)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1400(GridDhtAtomicCache.java:141)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$15.apply(GridDhtAtomicCache.java:429)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$15.apply(GridDhtAtomicCache.java:424)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager

Re: Using different versions of serializable objects

[Ilya Kasnacheev]

Hello!

Does this still happen if you get rid of Serializable, readObject,
writeObject?

Regards,
-- 
Ilya Kasnacheev


ср, 2 дек. 2020 г. в 09:58, Surkov.Aleksandr :

> Hi igniters!
>
> We use third party classes and store them objects in key-value cache.
> This class implements the Serializable interface and defines the readObject
> and writeObject methods.
>
> After we decided to switch to a new version of the class and tried to read
> from the cache, we received an error:
>
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to unmarshal object with
> optimized marshaller
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1317)
> at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2066)
> at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1093)
> at
>
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:676)
> at
> com.client.SerializableTest.main(SerializableTest.java:27)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7510)
> at
>
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
>
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:191)
> at
>
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4972)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4931)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1486)
> at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1090)
> ... 2 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:1785)
> at
>
> org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1991)
> at
>
> org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1816)
> at
>
> org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1807)
> at
>
> org.apache.ignite.internal.binary.GridBinaryMarshaller.unmarshal(GridBinaryMarshaller.java:268)
> at
>
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.unmarshal(CacheObjectBinaryProcessorImpl.java:1100)
> at
>
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:89)
> at
>
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:176)
> at
>
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
> at
>
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:136)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1808)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1796)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:747)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:624)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:374)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1400(GridDhtAtomicCache.java:141)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$15.apply(GridDhtAtomicCache.java:429)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$15.apply(GridDhtAtomicCache.java:424)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(Grid

Re: Why does TextQuery failed to find result

[Ilya Kasnacheev]

Hello!

This answer seems relevant: https://stackoverflow.com/a/65069605/36498

Regards,
-- 
Ilya Kasnacheev


вт, 1 дек. 2020 г. в 20:23, siva :

> Hi All,
> I have .Net ClientServerIgnitePersistenceApp v2.7.6 to create Ignite caches
> and data loading using DataStreamer.And for TextQuery i am using thick
> client here is the cache configuration and Model class details.
> *Model class:*Person model class contains both fields marked as
> QuerySqlField and QueryTextField.
>
>
>
>
> *TextQuery search sample code:*
>
>
> *Search Text:*
> Person Model class Payload property contains json string.
>
>
> It's doesn't returning result.How to get search text result from cache?
> Please any further details needed let me know.
> Thanks.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Failing to cluster correctly

[Ilya Kasnacheev]

Hello!

I'm not sure. If you're using Spring you can also annotate such fields with
@SpringResource.

Regards,
-- 
Ilya Kasnacheev


пн, 30 нояб. 2020 г. в 13:35, RENDLE, ANDY (Insurance Finance
Transformation Portfolio) :

> Classification: Public
>
>
>
> Thanks for the update.
>
>
>
> Is there a Spring Ignite example available to demonstrate your suggested
> techniques?
>
>
>
> Thanks
>
>
>
> *Andy Rendle*
>
> Hadoop Technical Architect
>
> *Insurance Finance Transformation Portfolio | Group Transformation*
> --
>
> *M: *07973 878454  *| E: andy.ren...@lloydsbanking.com
> *
>
> *A: *Lloyds Banking Group, Harbourside, 10 Canons Way, Bristol, BS1 5LF
>
> *MM: *0203 770  *CP: *79299155# *PP: *77395220#
>
>
>
> *[image: cid:image001.png@01D327DF.B322F800]*
> 
>
> *Absence Note* :
>
>
>
> *From:* Ilya Kasnacheev 
> *Sent:* 27 November 2020 10:02
> *To:* user@ignite.apache.org
> *Subject:* Re: Failing to cluster correctly
>
>
>
>
> *-- This email has reached the Bank via an external source -- *
>
> Hello!
>
>
>
> It seems that you are sending compute tasks from one node to another
> with kafkaEventProcessor field set. However, you can't really send a Kafka
> instance to a different node that way. You need to remove this field / mark
> as transient, and instead inject a local Kafka on remote node before doing
> computations. Maybe remove kafkaEventProcessor with
> static kafkaEventProcessor().
>
>
>
> Regards,
>
> --
>
> Ilya Kasnacheev
>
>
>
>
>
> вт, 24 нояб. 2020 г. в 22:50, RENDLE, ANDY (Insurance Finance
> Transformation Portfolio) :
>
> Classification: Public
>
>
>
> All
>
>
>
> We have developed a Spring Ignite Kafka producer application, utilising
> Ignites caches and failover capabilities.
>
>
>
> This runs perfectly in standalone mode but when configured with another
> host we get many serialisation errors. We have obviously made some
> fundamental mistake, can anyone give us a clue as to where to look?
>
>
>
> java-1.8.0-openjdk-1.8.0.222.b10-0.el7_6.x86_64
>
> Ignite v2.7.6 & v2.9.0
>
> spring-boot 2.0.6.RELEASE
>
>
>
> Most of our processes are invoked like this:
>
> ignite.compute().withExecutor(SCANNER_POOL).callAsync(IgniteCallable)
>
>
>
> It seems to serializing many classes that are not expected, even when both
> nodes have exactly the same deployment. We have many Autowired variables
> but all are correct and working in standalone mode. In clustered mode and
> we end up with a huge exceptions in the file attached:
>
>
>
> Many thanks in advance,
>
>
>
> *Andy Rendle*
>
>
>
> Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ.
> Registered in Scotland no. SC95000. Telephone: 0131 225 4555.
>
> Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN.
> Registered in England and Wales no. 2065. Telephone 0207626 1500.
>
> Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ.
> Registered in Scotland no. SC327000. Telephone: 03457 801 801.
>
> Lloyds Bank Corporate Markets plc. Registered office: 25 Gresham Street,
> London EC2V 7HN. Registered in England and Wales no. 10399850.
>
> Scottish Widows Schroder Personal Wealth Limited. Registered Office: 25
> Gresham Street, London EC2V 7HN. Registered in England and Wales no.
> 11722983.
>
> Lloyds Bank plc, Bank of Scotland plc and Lloyds Bank Corporate Markets
> plc are authorised by the Prudential Regulation Authority and regulated by
> the Financial Conduct Authority and Prudential Regulation Authority.
>
> Scottish Widows Schroder Personal Wealth Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> Lloyds Bank Corporate Markets Wertpapierhandelsbank GmbH is a wholly-owned
> subsidiary of Lloyds Bank Corporate Markets plc. Lloyds Bank Corporate
> Markets Wertpapierhandelsbank GmbH has its registered office at
> Thurn-und-Taxis Platz 6, 60313 Frankfurt, Germany. The company is
> registered with the Amtsgericht Frankfurt am Main, HRB 111650. Lloyds Bank
> Corporate Markets Wertpapierhandelsbank GmbH is supervised by the
> Bundesanstalt für Finanzdienstleistungsaufsicht.
>
> Halifax is a division of Bank of Scotland plc.
>
> HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in
> Scotland no. SC218813.
>
>
>
> This e-mail (including any attachments) is private and confidential and
> may contain privileged material. If you have received this e-mail in error,
> please notify the sender and delete it (including any attachments)
> immediately. You must not copy, distribute, disclose or use any of the
> information in it or any attachments. Telephone calls may be monitored or
> recorded.
>
> Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ.
> Registered in Scotland no. SC95000. Telephone: 0131 225 4555.
>
> Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN.
> Registered in England and Wales no. 2065. Telephone 0207626 15