Re: Getting No space left on device exception when persistence is enabled

We don't have any user limitations. And currently out of 300GB, we have 115 GB free space left. What's with having 100 GB free space? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Getting No space left on device exception when persistence is enabled

Hi! Well, the message say no space left on device so you are sure the persistence/WAL data is stored on the drive where you have 100GB free space ? you don't have any user limitations on disk usage or anything like that ? Mikael Den 2020-02-05 kl. 07:18, skrev adipro: Can someone please h

Re: Getting No space left on device exception when persistence is enabled

Can someone please help? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite AtomicLong

Thank you Ilya. I asked above because I got the below exception: org.apache.ignite.transactions.TransactionRollbackException: Failed to finish transaction because it has been rolled back [timeout=0, tx=GridNearTxLocal[xid=dec3274ff61--0b6f-279c--000a, xidVersion=GridCacheVersio

Re: GridGain Web Console is available free of charge for Apache Ignite

Hi Prasad, I've introduced you to the right people at GridGain. - Denis On Mon, Feb 3, 2020 at 11:44 PM Prasad Bhalerao < prasadbhalerao1...@gmail.com> wrote: > Hi Denis/Alexey, > > We have found few more vulnerabilities in Gridgain Web console and due to > which we can't deploy it in producti

Re: Page size for large objects

Hi, This test uses .array().length instead of length() in estimating the size, so I guess that would be the approach to use: https://github.com/apache/ignite/blame/master/modules/core/src/test/java/org/apache/ignite/internal/binary/BinaryMarshallerSelfTest.java Regarding the large objects, you ca

Re: Partition/Fault tolerance and availability of Apache Ignite

Hello! Can you please collect complete logs from all nodes, not just a screenful of logs? Regards, -- Ilya Kasnacheev вт, 4 февр. 2020 г. в 09:20, userx : > Fault_tolerance.zip > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1165/Fault_tolerance.zip> > > > Hi Ilya, > > Thank you fo

Re: DataStreamer as a Service

Understood. Thank you, for the feedback. On Tue, Feb 4, 2020 at 7:09 AM Ilya Kasnacheev wrote: > Hello! > > Data Streamer can be used on server node all right, however, it is still a > "client" operation, i.e., it will batch some data locally and only then > send to server nodes, including itsel

Re: DataStreamer as a Service

Hello! Data Streamer can be used on server node all right, however, it is still a "client" operation, i.e., it will batch some data locally and only then send to server nodes, including itself. Regards, -- Ilya Kasnacheev вт, 4 февр. 2020 г. в 13:58, narges saleh : > Hi, > I am not sure I fol

Re: Different data regions on nodes

Have found that it could be solved with node filters and attributes: mark server with special custom attribute: new IgniteConfiguration().setUserAttributes(Collections.singletonMap("role", "hasRegion")) specify node filter for the cache, which selects only servers with custom attribute mentioned

Re: DataStreamer as a Service

Hi, I am not sure I follow the relationship between per partition batching and client-side capabilities. Does this mean that the data streamer cannot do per partition batching on the server side, for example the service grid? I understand that low intensity streaming defeats the purpose of having

Re: DataStreamer as a Service

Hello! In case of long-lived, low-intensity streaming, Data Streamer will not be able to utilize its client-side per-partition batching capabilities, instead being just a wrapper over cache update operations, which are available as part of Cache API. Regards, -- Ilya Kasnacheev вт, 4 февр. 202