Re: User-defined event

[j_recuerda]

It was my fault. I was not listening to remote events.



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

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

[j_recuerda]

Hello,

Thanks a lot, Ilya. According to this snippet, It should work when a
DefaultDataRegion is configured, as you mention. I have tested and checked
that this function returns true but it doesn't work, the AtomicSequence I am
expecting to be persistent is not persisted.

>From my point of view, it is annoying that not setting a DefaultDataRegion
doesn't behave as setting a default constructed DefaultDataRegion.

Thanks!



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

Re: JVM crashed with SIGSEGV with stack trace to OptimizedObjectOutputStream.writeObject

[tarunk]

Thanks Ilya,

The node is not same always where it comes, and it keep changing.

We got all nodes hardware/OS checked by respective teams, also raised the
case with RedHat and got the response this should be service issue as only
specific service is crashing.

Curios to know why we got this raised as Compiler type crash as per
https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/crashes001.html
This seems to be matching 5.1.2 Crash in Compiled Code from above doc as the
type of problematic frame is "J".

Thanks
Tarun




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

Client Vs Server Configuration

[Victor]

Hi,

I am planning to use oob server nodes (i.e. started via ignite.sh) pass a
configuration xml containing the basic discovery ip only.
In my client code, i plan to define the Cache configuration, query fields
and additionally my custom RDBMS support via implementing the
CacheLoader->load(...) method for cache miss cases.

Given this setup/configuration, I have tried the Cache/Query field
configuration part and that works, i have to yet try out the RDBMS bit via
CacheLoader. Had a couple of basic queries,

1. Is this configuration model doable and will it seamlessly work?
2. Are there any pros/con's with not having the config on the sever end,
performance, n/w hops, etc?

Thanks,
Victor



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

Re: Query performance varying with LIMIT keyword

[nunob]

Also if I fix the LIMIT and vary the OFFSET I get responses of this
magnitude:

  LIMIT 1 OFFSET 0: 50ms
  LIMIT 1 OFFSET 1: 200ms
  LIMIT 1 OFFSET 5: 700ms
  LIMIT 1 OFFSET 10: 1.3s
  LIMIT 1 OFFSET 50: 7.8s

Why is this?



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

Re: Could not create .NET CacheStore

[siva]

Hi, 
Thanks for replaying with example.
I have some query regarding cache store access and registering
configuration.
1.Add or configure cache on evey client node on starting node or access
cache time instead of, 
is there any other way like one time register cache configuration, after
onward any client node can access cache configration? 
2.Is that registering cache configuration on each node calling every factory
and store implemented method or internally searching for existing cache
configuration matches than override matching configuration.or something like
that.








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

Re: JDBC Connectivity

[narges saleh]

Hello Stephan,

I mean using JDBC defined types in the XML file, to define the tables.
Similar to the way  JDBC types are used in defining tables with 3rd party
databases.

thanks.

On Mon, Jan 20, 2020 at 10:04 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> Which JDBC settings? If you use the JDBC thick client, you can define your
> caches there if you like.
>
> On 18 Jan 2020, at 12:01, narges saleh  wrote:
>
> Hello Stephan,
>
> Thanks. I get this working using query entity in my XML config file. I
> assume it is not possible to do the same with JDBC settings in the XML file.
>
> On Fri, Jan 17, 2020 at 2:10 AM Stephen Darlington <
> stephen.darling...@gridgain.com> wrote:
>
>> See the “Configuring Indexes using query entities” section of the
>> documentation:
>> https://www.gridgain.com/docs/latest/developers-guide/SQL/indexes#configuring-indexes-using-query-entities
>>
>> Regards,
>> Stephen
>>
>> On 16 Jan 2020, at 23:14, narges saleh  wrote:
>>
>> 
>> Thanks Stephan.
>>
>> Can you send me an example where the cache and tables are entirely
>> defined in the XML configuration file (and no POJO), with query entity or
>> just JDBC? Let's assume that the sql codes run on a server node or a thick
>> client.
>>
>>
>> On Thu, Jan 16, 2020 at 8:02 AM Stephen Darlington <
>> stephen.darling...@gridgain.com> wrote:
>>
>>> If you create a cache, either in code or XML, using the minimal list of
>>> parameter it won’t be accessible using SQL.
>>>
>>> There are a number of ways you can define what’s visible using SQL. You
>>> can use a POJO with the @QuerySqlField annotation (and the indexTypes
>>> property in the XML file) or define QueryEntities. See the documentarian:
>>> https://www.gridgain.com/docs/latest/developers-guide/SQL/indexes
>>>
>>> Whether you do it on the client or server side is a bit of a religious
>>> debate, but either works. The important thing is that the first definition
>>> to hit the cluster is the one that takes effect.
>>>
>>> The most common pattern I see with JDBC is the caches are defined server
>>> side, and clients connect using the *thin-client* driver. Thin clients
>>> just need a hostname and port.
>>>
>>> However, there is also a thick-client JDBC driver. The XML here is no
>>> different from any other node.
>>>
>>> Regards,
>>> Stephen
>>>
>>> On 16 Jan 2020, at 12:54, narges saleh  wrote:
>>>
>>> Thanks Ilya, Steve.
>>> 1) What do you mean by SQL enabled? Do I still need to define the POJO
>>> classes for the objects/tables?
>>> 2) Can I specify the caches including the table definitions entirely in
>>> XML config file and pass the config file to the JDBC connection? If yes,
>>> I'd greatly appreciate it if you provide some small samples. Please keep in
>>> mind that we have native persistence in place not a third party database.
>>>
>>>
>>>
>>> On Wed, Jan 15, 2020 at 7:29 AM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 Hello!

 4) I actually think that if you specify caches in thick client's config
 file, and they are absent on server, they will be created.

 (However, they will not be changed if configuration differs)

 Regards,
 --
 Ilya Kasnacheev


 ср, 15 янв. 2020 г. в 15:59, narges saleh :

> Hi All,
>
> I am trying to use ignite's cache grid with native persistence and
> prefer to use JDBC for cache/db connectivity.
>
> 1) Is this possible, in either client or server mode?
> 2) If yes, I assume, I'd need one JDBC connection per cache, as I see
> it is possible to specify only one cache per JDBC connection. Is this 
> right?
> 3) Is this also true if I need to join multiple tables/caches?
> 4) Can I specify my caches in XML config file and just pass the config
> file to the JDBC connection?
> 5) Will I get the same load performance if I JDBC with streaming set
> to true as I'd using the streamer module directly (I see that I can 
> specify
> most of the streamer config options on JDBC connection configuration)?
>
> thanks.
>

>>>
>>>
>
>

Re: CacheKeyConfiguration

[narges saleh]

Thanks Stephan,

I don't want to use POJO classes if I can help it.
I want to mimic the following in my configuration file:

CREATE TABLE IF NOT EXISTS Person (
  id int,
  city_id int,
  name varchar,
  age int,
  company varchar,
  PRIMARY KEY (id, city_id)) WITH "template=partitioned,affinity_key=city_id";

Furthermore, I want to see if it is possible to define affinity over
multiple keys, for example, have the above as

CREATE TABLE IF NOT EXISTS Person (
  id int,
  city_id int,
  name varchar,
  age int,
  company varchar,
  PRIMARY KEY (id, city_id)) WITH
"template=partitioned,*affinity_key=city_id, country_id"*

*;*

I have many caches and the relationship between them imply different
set of affinity keys. All are defined within the same configuration
file.


On Mon, Jan 20, 2020 at 12:40 PM narges saleh  wrote:

> Thanks Stephan,
>
> I don't want to use POJO classes if I can help it.
> I want to mimic the following in my configuration file:
>
>
> On Mon, Jan 20, 2020 at 10:30 AM Stephen Darlington <
> stephen.darling...@gridgain.com> wrote:
>
>> Details on how to configure affinity colocation can be found in the
>> documentation:
>> https://www.gridgain.com/docs/latest/developers-guide/data-modeling/affinity-collocation
>>
>>
>> In short, use the “indexedTypes” property in the XML file and the
>> @AffinityKeyMapped annotation in your POJO key,
>>
>> Regards,
>> Stephen
>>
>> On 18 Jan 2020, at 12:28, narges saleh  wrote:
>>
>> Hi All,
>>
>> I understand that CacheKeyConfiguration is defined at ignite
>> configuration level. That being the case, how do you tie the affinity key
>> to a particular cache, within the XML config file?
>> The following code snippet shows how to do in java code.
>>
>>   CacheConfiguration personCfg = new 
>> CacheConfiguration("persons");
>>
>> //configure the affinity key
>> personCfg.setKeyConfiguration(new CacheKeyConfiguration("Person", 
>> "companyId"));
>>
>> Also, how do you define an affinity key with multiple fields, using 
>> CacheKeyConfiguration, say SSN and company id are both part of the affinity 
>> key.
>>
>> thanks.
>>
>>
>>
>>

Re: CacheKeyConfiguration

[narges saleh]

Thanks Stephan,

I don't want to use POJO classes if I can help it.
I want to mimic the following in my configuration file:


On Mon, Jan 20, 2020 at 10:30 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> Details on how to configure affinity colocation can be found in the
> documentation:
> https://www.gridgain.com/docs/latest/developers-guide/data-modeling/affinity-collocation
>
>
> In short, use the “indexedTypes” property in the XML file and the
> @AffinityKeyMapped annotation in your POJO key,
>
> Regards,
> Stephen
>
> On 18 Jan 2020, at 12:28, narges saleh  wrote:
>
> Hi All,
>
> I understand that CacheKeyConfiguration is defined at ignite configuration
> level. That being the case, how do you tie the affinity key to a particular
> cache, within the XML config file?
> The following code snippet shows how to do in java code.
>
>   CacheConfiguration personCfg = new 
> CacheConfiguration("persons");
>
> //configure the affinity key
> personCfg.setKeyConfiguration(new CacheKeyConfiguration("Person", 
> "companyId"));
>
> Also, how do you define an affinity key with multiple fields, using 
> CacheKeyConfiguration, say SSN and company id are both part of the affinity 
> key.
>
> thanks.
>
>
>
>

Query performance varying with LIMIT keyword

[nunob]

Hello,

I have table A with PK (col1, col2, col3) and table B with PK (col1, col2
col3)

Both tables have around 300k records.

This query executes in *2ms*:

/SELECT * FROM table_a a
LEFT JOIN table_b b ON  b.col1 = a.col1
 AND b.col2 = a.col2
 AND b.col3 = a.col3
*LIMIT 1 *OFFSET 0;/

This query executes in *1.4s*:

/SELECT * FROM table_a a
LEFT JOIN table_b b ON  b.col1 = a.col1
 AND b.col2 = a.col2
 AND b.col3 = a.col3
*LIMIT 10 *OFFSET 0;/

Shouldn't the execution time be the same for both queries or am I missing
something?



Regards,

Nuno





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

Re: Native Persistence & JDBC

[narges saleh]

Hello Ilya

I do have the PERSON2 cache. Here is the snippet for the cache
configuration. I don't have any issue with this configuration if I don't
enable native persistence.













wrote:

> Hello!
>
> Maybe you don't have PERSON2 cache? :)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 20 янв. 2020 г. в 02:47, narges saleh :
>
>> Hi All
>>
>> I am using JDBC connection for inserting data into caches specified in my
>> config file (via query entities). If I don't enable native persistence,
>> everything works fine and I can insert the data into cache/table and query
>> the cache/table. But if I enable native persistence, the client dies as
>> soon it attempts to create the JDBC connection, using the configuration
>> file, with this error:
>>
>> SQLException: Client is invalid. Probably cache name is wrong.
>>
>> The connection command is this:
>>
>> Connection conn = DriverManager.getConnection(
>> "jdbc:ignite:cfg://cache=PERSON2:streaming=true:streamingFlushFrequency=
>> 2000@file:///opt/ignite/config/query-entity-store.xml");
>>
>> Any idea what could I be doing wrong?
>>
>> thanks.
>>
>

RE: Re: How best to push continuously updating ordered data on Apache ignite cache

[Alexandr Shapkin]

Hello! You could take a look at putAll method that sends all updates to the server right away. > *What is best way out of above to push continuously updating data like> market data?*For me it seems that the DataStreamer is more suitable for continuous data processing where you are not interested in getting acks from a server.Use StreamReceiver/StreamTransformer for additional data modificationbefore the updating the values. As Mikael suggested, you could implement some kind of an update counter. It feels that DateTime should work here. Atomic sequences for the valid stock price could be helpful as well [1]. [1] - https://apacheignite.readme.io/docs/atomic-types From: MikaelSent: Friday, January 17, 2020 12:07 PMTo: user@ignite.apache.orgSubject: Re: How best to push continuously updating ordered data on Apache ignite cache Hi! Trusting that things come in the correct order could be tricky, the only way to do it I guess it to use put(), if you need fast writes you will have to use multiple threads and any ordering will be lost, can't you include some ordering data when you write them, a counter or whatever and use that to sort them in client 2 ? that would be uch safer. You might need to include some kind of waiting process in case one entry has not arrived yet, but if you use a counter to write them you know that after 1 there will always ba a 2 and so on without any gaps so it should not be that messy. Mikael Den 2020-01-17 kl. 04:51, skrev trans:> *Usecase*> > Here is the topology we are working on> > *Server - 1* --> marketData cache, holds different share prices information> > *Client - 1* --> Pushing data on the cache> > *Client - 2* --> Continuous query, listening updates coming on marketData> cache per key basis> > I want data to follow the order in which it was received and pushed on> queue. Reason is that client - 2 should not get old data. For example last> price data for an instrument moved from 100 to 101 then 102. Client - 2> should get in the same order and to **not** get in order like 100 to 102> then 101.> So for a key in my cache i want the messages to be pushed in order.> > Ways of pushing data on cache:> >   1. *put* seems to be safest way but looks like slow and full cache update> is happening and then thread moves to next statement. This might not be> suitable for pushing 2 updates per second.> >   2. *putAsync *seems to be good way, my understanding is that it uses> striped pool to push data on the cache. As the  striped pool> > uses max(8, no of cores) so it should be faster. But as the multiple threads> are being processed in parallel so does it confirm the data ordering as it> was pushed in?> >   3. *DataStreamer *seems to be best way as it also processes things in> parallel but again the problem is with the order of putting data into cache.> API documentation> > also mention that ordering of data is not guaranteed.> > > Can someone please clarify above? I could not find document giving clear> deeper understanding for these ways.> *What is best way out of above to push continuously updating data like> market data?*> > > > --> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

[Ilya Kasnacheev]

Hello again!

I guess that maybe you have to specify a default data region configuration
here, and not just rely on default configuration for default data region.

I also think this is a bug :)

Regards,
-- 
Ilya Kasnacheev


пн, 20 янв. 2020 г. в 20:16, Ilya Kasnacheev :

> Hello!
>
> It's very strange, considering the following code in 2.7.6:
>
> /**
>  * @return {@code true} if persistence is enabled for at least one data 
> region, {@code false} if not.
>  */
> public static boolean isPersistenceEnabled(DataStorageConfiguration cfg) {
> if (cfg == null)
> return false;
>
> DataRegionConfiguration dfltReg = cfg.getDefaultDataRegionConfiguration();
>
> if (dfltReg == null)
> return false;
>
> if (dfltReg.isPersistenceEnabled())
> return true;
>
> DataRegionConfiguration[] regCfgs = cfg.getDataRegionConfigurations();
>
> if (regCfgs == null)
> return false;
>
> for (DataRegionConfiguration regCfg : regCfgs) {
> if (regCfg.isPersistenceEnabled())
> return true;
> }
>
> return false;
> }
>
> Regards,
>
> --
> Ilya Kasnacheev
>
>
> пн, 20 янв. 2020 г. в 19:54, j_recuerda :
>
>> Hi, Ilya,
>>
>> I am afraid I have tested it and it doesn't.
>>
>> Thanks!
>>
>>
>> ilya.kasnacheev wrote
>> > Hello!
>> >
>> > I think that system region is persistent if *any* of the regions is
>> > persistent, not just the default one.
>> >
>> > Regards,
>> > --
>> > Ilya Kasnacheev
>>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

[Ilya Kasnacheev]

Hello!

It's very strange, considering the following code in 2.7.6:

/**
 * @return {@code true} if persistence is enabled for at least one
data region, {@code false} if not.
 */
public static boolean isPersistenceEnabled(DataStorageConfiguration cfg) {
if (cfg == null)
return false;

DataRegionConfiguration dfltReg = cfg.getDefaultDataRegionConfiguration();

if (dfltReg == null)
return false;

if (dfltReg.isPersistenceEnabled())
return true;

DataRegionConfiguration[] regCfgs = cfg.getDataRegionConfigurations();

if (regCfgs == null)
return false;

for (DataRegionConfiguration regCfg : regCfgs) {
if (regCfg.isPersistenceEnabled())
return true;
}

return false;
}

Regards,

-- 
Ilya Kasnacheev


пн, 20 янв. 2020 г. в 19:54, j_recuerda :

> Hi, Ilya,
>
> I am afraid I have tested it and it doesn't.
>
> Thanks!
>
>
> ilya.kasnacheev wrote
> > Hello!
> >
> > I think that system region is persistent if *any* of the regions is
> > persistent, not just the default one.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: java.lang.NullPointerException while preloadEntry

[Ilya Kasnacheev]

Hello!

Can you provide logs from all server nodes? I think there's something in
them, besides this error.

Regards,
-- 
Ilya Kasnacheev


пн, 20 янв. 2020 г. в 20:03, userx :

> Hi,
>
> Topology version is 67. Ignite version is 2.7.6.
>
> I went through the thread mentioned by you but in our case, we do not have
> clients connecting and disconnecting time and again. If a client is
> connected to the cluster, the topololgy version is increased by 1. The
> client doesn't disconnect ever. There are around 11 ignite servers and 56
> clients.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: java.lang.NullPointerException while preloadEntry

[userx]

Hi,

Topology version is 67. Ignite version is 2.7.6.

I went through the thread mentioned by you but in our case, we do not have
clients connecting and disconnecting time and again. If a client is
connected to the cluster, the topololgy version is increased by 1. The
client doesn't disconnect ever. There are around 11 ignite servers and 56
clients. 



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

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

[j_recuerda]

Hi, Ilya,

I am afraid I have tested it and it doesn't.

Thanks!


ilya.kasnacheev wrote
> Hello!
> 
> I think that system region is persistent if *any* of the regions is
> persistent, not just the default one.
> 
> Regards,
> -- 
> Ilya Kasnacheev





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

Re: Native Persistence & JDBC

[Ilya Kasnacheev]

Hello!

Maybe you don't have PERSON2 cache? :)

Regards,
-- 
Ilya Kasnacheev


пн, 20 янв. 2020 г. в 02:47, narges saleh :

> Hi All
>
> I am using JDBC connection for inserting data into caches specified in my
> config file (via query entities). If I don't enable native persistence,
> everything works fine and I can insert the data into cache/table and query
> the cache/table. But if I enable native persistence, the client dies as
> soon it attempts to create the JDBC connection, using the configuration
> file, with this error:
>
> SQLException: Client is invalid. Probably cache name is wrong.
>
> The connection command is this:
>
> Connection conn = DriverManager.getConnection(
> "jdbc:ignite:cfg://cache=PERSON2:streaming=true:streamingFlushFrequency=
> 2000@file:///opt/ignite/config/query-entity-store.xml");
>
> Any idea what could I be doing wrong?
>
> thanks.
>

User-defined event

[j_recuerda]

Hi,

I am running Ignite 2.7.0. I am trying to trigger a user-defined event that
can be listened by all the nodes in the cluster but in the IgniteEvents API
there is just 'recordLocal', which doesn't trigger the listeners in remote
nodes.

I have looked for a way of doing so in the documentation but I couldn't find
anything. Any reference on how to achieve that?


Thanks!



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

Re: CacheKeyConfiguration

[Stephen Darlington]

Details on how to configure affinity colocation can be found in the 
documentation: 
https://www.gridgain.com/docs/latest/developers-guide/data-modeling/affinity-collocation
 

In short, use the “indexedTypes” property in the XML file and the 
@AffinityKeyMapped annotation in your POJO key,

Regards,
Stephen

> On 18 Jan 2020, at 12:28, narges saleh  wrote:
> 
> Hi All,
> 
> I understand that CacheKeyConfiguration is defined at ignite configuration 
> level. That being the case, how do you tie the affinity key to a particular 
> cache, within the XML config file?
> The following code snippet shows how to do in java code.
>   CacheConfiguration personCfg = new 
> CacheConfiguration("persons");
>
> //configure the affinity key
> personCfg.setKeyConfiguration(new CacheKeyConfiguration("Person", 
> "companyId"));
> 
> Also, how do you define an affinity key with multiple fields, using 
> CacheKeyConfiguration, say SSN and company id are both part of the affinity 
> key.
> thanks.

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

[Ilya Kasnacheev]

Hello!

I think that system region is persistent if *any* of the regions is
persistent, not just the default one.

Regards,
-- 
Ilya Kasnacheev


пт, 17 янв. 2020 г. в 21:52, Mikael :

> Hi!
>
> If you set the default region persistent all services will be persistent
> also, I guess this goes for all the set, queues and counters also, if
> you want to use the security system it has to be persistent, I use it
> all time just for the fact that all services will survive a  restart
> even if all nodes go down.
>
> Mikael
>
> Den 2020-01-17 kl. 18:49, skrev j_recuerda:
> > I am using Ignite 2.7.0
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: JVM crashed with SIGSEGV with stack trace to OptimizedObjectOutputStream.writeObject

[Ilya Kasnacheev]

Hello!

If it's always the same physical machine, I would check hardware and/or OS.

I don't remember seeing this exception and I don't see why you would only
see it on 1 node.

Regards,
-- 
Ilya Kasnacheev


пн, 20 янв. 2020 г. в 11:50, tarunk :

> Hi All,
>
> In our 12 nodes ignite cluster one of the node jvm get crashes sometimes
> with below error.
> Is this some know issue with Ignite ? or some other memory/jvm issue.
> We are using openjdk 1.8 ("1.8.0_232") provided by RedHat.
>
> A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7fef7f1d3eb0, pid=42623,
> tid=0x7feea62c8700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build
> 1.8.0_222-b10)
> # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64
> compressed oops)
> # Problematic frame:
> # J 62683 C2
>
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(Ljava/lang/Object;)V
> (331 bytes) @ 0x7fef7f1d3eb0 [0x7fef7f1d3e00+0xb0]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core
> dumping, try "ulimit -c unlimited" before starting Java again
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: JDBC Connectivity

[Stephen Darlington]

Which JDBC settings? If you use the JDBC thick client, you can define your 
caches there if you like.

> On 18 Jan 2020, at 12:01, narges saleh  wrote:
> 
> Hello Stephan,
> 
> Thanks. I get this working using query entity in my XML config file. I assume 
> it is not possible to do the same with JDBC settings in the XML file.
> 
> On Fri, Jan 17, 2020 at 2:10 AM Stephen Darlington 
> mailto:stephen.darling...@gridgain.com>> 
> wrote:
> See the “Configuring Indexes using query entities” section of the 
> documentation:  
> https://www.gridgain.com/docs/latest/developers-guide/SQL/indexes#configuring-indexes-using-query-entities
>  
> 
> 
> Regards,
> Stephen 
> 
>> On 16 Jan 2020, at 23:14, narges saleh > > wrote:
>> 
>> 
>> Thanks Stephan.
>> 
>> Can you send me an example where the cache and tables are entirely defined 
>> in the XML configuration file (and no POJO), with query entity or just JDBC? 
>> Let's assume that the sql codes run on a server node or a thick client.
>> 
>> 
>> On Thu, Jan 16, 2020 at 8:02 AM Stephen Darlington 
>> mailto:stephen.darling...@gridgain.com>> 
>> wrote:
>> If you create a cache, either in code or XML, using the minimal list of 
>> parameter it won’t be accessible using SQL.
>> 
>> There are a number of ways you can define what’s visible using SQL. You can 
>> use a POJO with the @QuerySqlField annotation (and the indexTypes property 
>> in the XML file) or define QueryEntities. See the documentarian: 
>> https://www.gridgain.com/docs/latest/developers-guide/SQL/indexes 
>>  
>> 
>> Whether you do it on the client or server side is a bit of a religious 
>> debate, but either works. The important thing is that the first definition 
>> to hit the cluster is the one that takes effect. 
>> 
>> The most common pattern I see with JDBC is the caches are defined server 
>> side, and clients connect using the thin-client driver. Thin clients just 
>> need a hostname and port.
>> 
>> However, there is also a thick-client JDBC driver. The XML here is no 
>> different from any other node.
>> 
>> Regards,
>> Stephen
>> 
>>> On 16 Jan 2020, at 12:54, narges saleh >> > wrote:
>>> 
>>> Thanks Ilya, Steve.
>>> 1) What do you mean by SQL enabled? Do I still need to define the POJO 
>>> classes for the objects/tables?
>>> 2) Can I specify the caches including the table definitions entirely in XML 
>>> config file and pass the config file to the JDBC connection? If yes, I'd 
>>> greatly appreciate it if you provide some small samples. Please keep in 
>>> mind that we have native persistence in place not a third party database.
>>> 
>>> 
>>> 
>>> On Wed, Jan 15, 2020 at 7:29 AM Ilya Kasnacheev >> > wrote:
>>> Hello!
>>> 
>>> 4) I actually think that if you specify caches in thick client's config 
>>> file, and they are absent on server, they will be created.
>>> 
>>> (However, they will not be changed if configuration differs)
>>> 
>>> Regards,
>>> -- 
>>> Ilya Kasnacheev
>>> 
>>> 
>>> ср, 15 янв. 2020 г. в 15:59, narges saleh >> >:
>>> Hi All,
>>> 
>>> I am trying to use ignite's cache grid with native persistence and prefer 
>>> to use JDBC for cache/db connectivity.
>>> 
>>> 1) Is this possible, in either client or server mode?
>>> 2) If yes, I assume, I'd need one JDBC connection per cache, as I see it is 
>>> possible to specify only one cache per JDBC connection. Is this right?
>>> 3) Is this also true if I need to join multiple tables/caches?
>>> 4) Can I specify my caches in XML config file and just pass the config file 
>>> to the JDBC connection?
>>> 5) Will I get the same load performance if I JDBC with streaming set to 
>>> true as I'd using the streamer module directly (I see that I can specify 
>>> most of the streamer config options on JDBC connection configuration)?
>>> 
>>> thanks.
>> 
>> 

Re: java.lang.NullPointerException while preloadEntry

[Ilya Kasnacheev]

Hello!

I can see there is a previous occurrence of this issue:
http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-in-GridDhtPartitionDemander-td19010.html

Can you elaborate what is your topology version and actual Ignite version?
Maybe you can find anything else in server logs?

Regards,
-- 
Ilya Kasnacheev


пн, 20 янв. 2020 г. в 16:40, userx :

> hi team,
>
> I recently observed an error bringing down one of the ignite server nodes.
> The log mentions a NullPointerExceptionException on preload of an entry.
> Subsequently 2 other nodes went down. Here is the stack trace of first
> failure
>
> 2019-12-14 06:47:51,030 ERROR [sys-#61006%ABCD4%] {}
> org.apache.ignite.internal.processors.cache.GridCacheIoManager -
> Failed processing message
> [
> senderId=647bc0f2-67d8-469b-9a49-af4231463887,
> msg=GridDhtPartitionSupplyMessage
> [
> rebalanceId=117004,
> topVer=AffinityTopologyVersion
> [
> topVer=67,
> minorTopVer=395
> ],
> missed=null,
> clean=null,
> msgSize=524366,
> estimatedKeysCnt=-1,
> size=1,
> parts=[449],
> super=GridCacheGroupIdMessage [grpId=1152451571]
> ]
> ]
> java.lang.NullPointerException
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:893)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:772)
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:387)
> at
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:419)
> at
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:409)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
>
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
>
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
>
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
>
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
>
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
>
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> 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)
>
>
> 1) The question is that in spite of the fixed number of Ignite server
> nodes,
> why is the rebalance triggered ?
> 2) What is causing the Null pointer ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

RE: Populate ddl (e.g., create table) to third party persistence

[Alexandr Shapkin]

Hello! I don’t think it could be done out of the box. You could try to start from the opposite side and generate a schema from a RDBMS instead using the WebConsole [1]. [1] - https://www.gridgain.com/docs/web-console/2019.12.02/automatic-rdbms-integration  From: crypto_rickleeSent: Friday, January 17, 2020 10:19 AMTo: user@ignite.apache.orgSubject: Populate ddl (e.g., create table) to third party persistence Hi all, I'm using Postgres as the third party persistence for Ignite 2.7.6. Justwant to know if I create a table on ignite cluster, is there any way topopulate the schema back to the Postgres automatically? Thanks!   --Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 

RE: Re: Cache entries expiring in pageEvictionMode=DISABLED

[Alexandr Shapkin]

>What's worse - they are evicted on one node, and eviction>is not propagated on the other two nodes (so now every node has different>count of entries for that cache, even though it's replicated) Data region configuration defines a local machine’s memory settings, it doesn’t propagate to other nodes.  Have you managed to get the eviction work properly? From: akorenshSent: Wednesday, January 15, 2020 11:36 PMTo: user@ignite.apache.orgSubject: Re: Cache entries expiring in pageEvictionMode=DISABLED Hi, Are you not seeing cache entries and therefore making the assumption thateviction has kicked in?You could inadvertently be using a different config w/persistence turned on? search in ignite logs for the words "persistenceEnabled=false"  If you've not enabled onHeapCaching or persistence, and page eviction isdisabled and no memory is left, Ignite will throwIgniteOutOfMemoryException. docs for your version: https://apacheignite.readme.io/v2.3/docs/evictions Can you try with only one cache(NonEvictable_256MB_Region) and see whetherthe problem repeats itself? Also, you have an old version, and if possible, can you do a small testusing a newer version(2.7.6) https://ignite.apache.org/download.cgi  and seewhether the behavior repeats itself. If you are able to reproduce this on 2.7.6, then send us your entire config,a reproducer project (or the code that you use to populate the cache) and wewill take a look. Thanks, Alex   --Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 

java.lang.NullPointerException while preloadEntry

[userx]

hi team,

I recently observed an error bringing down one of the ignite server nodes.
The log mentions a NullPointerExceptionException on preload of an entry.
Subsequently 2 other nodes went down. Here is the stack trace of first
failure

2019-12-14 06:47:51,030 ERROR [sys-#61006%ABCD4%] {}
org.apache.ignite.internal.processors.cache.GridCacheIoManager - 
Failed processing message 
[
senderId=647bc0f2-67d8-469b-9a49-af4231463887, 
msg=GridDhtPartitionSupplyMessage 
[
rebalanceId=117004, 
topVer=AffinityTopologyVersion 
[
topVer=67, 
minorTopVer=395
], 
missed=null, 
clean=null, 
msgSize=524366, 
estimatedKeysCnt=-1, 
size=1, 
parts=[449], 
super=GridCacheGroupIdMessage [grpId=1152451571]
]
] 
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:893)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:772)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:387)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:419)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:409)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
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)


1) The question is that in spite of the fixed number of Ignite server nodes,
why is the rebalance triggered ?
2) What is causing the Null pointer ? 



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

Re: How does a cache behave in LOCAL mode ?

[userx]

Thank you.



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

Re: Streamer and data loss

[Ilya Kasnacheev]

Hello!

If you use it in a smart way you can get very close performance (to
allowOverwrite=true data streamer), I guess.

Just call it with a decent number of entries belonging to the same cache
partition from multiple threads, with non-intersecting keys of course.

Regards,
-- 
Ilya Kasnacheev


чт, 16 янв. 2020 г. в 21:29, narges saleh :

> Hello Ilya,
>
> If I use putAll() operation then I won't get the streamer's bulk
> performance, would I? I have a huge amount of data to persist.
>
> thanks.
>
> On Thu, Jan 16, 2020 at 8:43 AM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> I think you should consider using putAll() operation if resiliency is
>> important for you, since this operation will be salvaged if initiator node
>> fails.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 16 янв. 2020 г. в 15:48, narges saleh :
>>
>>> Thanks Saikat.
>>>
>>> I am not sure if sequential keys/timestamps and Kafka like offsets would
>>> help if there are many data source clients and many streamer nodes in play;
>>> depending on the checkpoint, we might still end up duplicates (unless
>>> you're saying each client sequences its payload before sending it to the
>>> streamer; even then duplicates are possible on the cache). The only sure
>>> way, it seems to me, is for the client that catches the exception to check
>>> the cache and only resend the diff, which make things very complex. The
>>> other approach, if I am right is, to enable overwrite, so the streamer
>>> would dedup the data in cache. The latter is costly too. I think the ideal
>>> approach would have been if there were some type of streamer resiliency in
>>> place where another streamer node could pick up the buffer from a crashed
>>> streamer and continue the work.
>>>
>>>
>>> On Wed, Jan 15, 2020 at 9:00 PM Saikat Maitra 
>>> wrote:
>>>
 Hi,

 To minimise data loss during streamer node failure I think we can use
 the following steps:

 1. Use autoFlushFrequency param to set the desired flush frequency,
 depending on desired consistency level and performance you can choose how
 frequently you would like the data to be flush to Ignite nodes.

 2. Develop a automated checkpointing process to capture and store the
 source data offset, it can be something like kafka message offset or cache
 keys if keys are sequential or timestamp for last flush and depending on
 that the Ignite client can restart the data streaming process from last
 checkpoint if there are node failure.

 HTH

 Regards,
 Saikat

 On Fri, Jan 10, 2020 at 4:34 AM narges saleh 
 wrote:

> Thanks Saikat for the feedback.
>
> But if I use the overwrite option set to true to avoid duplicates in
> case I have to resend the entire payload in case of a streamer node
> failure, then I won't
>  get optimal performance, right?
> What's the best practice for dealing with data streamer node failures?
> Are there examples?
>
> On Thu, Jan 9, 2020 at 9:12 PM Saikat Maitra 
> wrote:
>
>> Hi,
>>
>> AFAIK, the DataStreamer check for presence of key and if it is
>> present in the cache then it does not allow overwrite of value if
>> allowOverwrite is set to false.
>>
>> Regards,
>> Saikat
>>
>> On Thu, Jan 9, 2020 at 6:04 AM narges saleh 
>> wrote:
>>
>>> Thanks Andrei.
>>>
>>> If the external data source client sending batches of 2-3 MB say via
>>> TCP socket connection to a bunch of socket streamers (deployed as ignite
>>> services deployed to each ignite node) and say of the streamer nodes 
>>> die,
>>> the data source client catching the exception, has to check the cache to
>>> see how much of the 2-4MB batch has been flushed to cache and resend the
>>> rest? Would setting streamer with overwrite set to true work, if the 
>>> data
>>> source client resend the entire batch?
>>> A question regarding streamer with overwrite option set to true. How
>>> does the streamer compare the content the data in hand with the data in
>>> cache, if each record is being assigned UUID when being  inserted to 
>>> cache?
>>>
>>>
>>> On Tue, Jan 7, 2020 at 4:40 AM Andrei Aleksandrov <
>>> aealexsand...@gmail.com> wrote:
>>>
 Hi,

 Not flushed data in a data streamer will be lost. Data streamer
 works
 thought some Ignite node and in case if this the node failed it
 can't
 somehow start working with another one. So your application should
 think
 about how to track that all data was loaded (wait for completion of
 loading, catch the exceptions, check the cache sizes, etc) and use
 another client for data loading in case if previous one was failed.

 BR,
 Andrei

 1/6/2020 2:37 AM, narges saleh пишет:
 > Hi All,
 >

Re: Getting all data from cache via scan query is taking lot of time

[Pavel Tupitsyn]

Ticket filed and fix is on the way:
https://issues.apache.org/jira/browse/IGNITE-12555

On Tue, Jan 14, 2020 at 6:44 PM Pavel Tupitsyn  wrote:

> I've tried that code with a single local Ignite server, started with
> default configuration, the result is:
>Time for PutAll: 187 ms for rows: 7500
>Time for fetching all data: 128 ms for rows: 7500
>
> However, when I removed JSON serialization and stored the objects as is
> (IgniteCache):
>Time for PutAll: 1924 ms for rows: 7500
>Time for fetching all data: 20288 ms for rows: 7500
>
> There is a performance issue with DateTime value serialization. I'm
> investigating and will get back to you with details soon.
>
> Meanwhile, there is a *workaround*: force Timestamp serialization format
> and convert all values to UTC (which is a good idea anyway):
> new IgniteClientConfiguration
> {
> ...
> BinaryConfiguration = new BinaryConfiguration
> {
> Serializer = new BinaryReflectiveSerializer
> {
> ForceTimestamp = true
> }
> }
> };
>
> Then call ToUniversalTime() on all DateTime values. The result is:
> Time for PutAll: 761 ms for rows: 7500
> Time for fetching all data: 645 ms for rows: 7500
>
> For reference, JSON serialization of those 7500 rows (CreateMapFromList)
> takes ~600ms on my machine.
>
> On Tue, Jan 14, 2020 at 4:09 PM Tunas 
> wrote:
>
>> I am using Ignite 2.7.6 dll for Ignite and newtonSoft json for converting
>> C#
>> objects to json.
>> Ignite configuration is same as mentioned allow. (Server and client are
>> running on different machine)
>>
>> Sorry code class is little bit lengthy.
>>
>> One thing observed before publishing this code: addition of properties of
>> type ObservableCollection is taking more time.
>>
>> class Program
>> {
>> public static IIgniteClient IgniteThinClient;
>> private static IgniteClientConfiguration
>> GetIgniteClientConfiguration()
>> {
>> return new IgniteClientConfiguration
>> {
>> Endpoints = new[] { "MyWorkStation:10800" },
>> SocketTimeout = TimeSpan.FromSeconds(60)
>> };
>> }
>> static void Main(string[] args)
>> {
>> int rows = 7500;
>> var lst = GetData(rows);
>>
>> Ignition.ClientMode = true;
>> IgniteThinClient =
>> Ignition.StartClient(GetIgniteClientConfiguration());
>> var cache = IgniteThinClient.GetOrCreateCache> string>("TestSlowness");
>>
>> var map1 = CreateMapFromList(lst);
>> Stopwatch sw = new Stopwatch();
>> sw.Start();
>> cache.PutAll(map1);
>> sw.Stop();
>> Console.WriteLine($"Time for PutAll: {sw.ElapsedMilliseconds}
>> ms
>> for rows: {rows}");
>> sw.Reset();
>>
>>
>> ICacheClient cacheClient =
>> IgniteThinClient.GetOrCreateCache("TestSlowness");
>> if(cacheClient!=null)
>> {
>> sw.Start();
>> *var cacheEntries = cacheClient.Query(new
>> Apache.Ignite.Core.Cache.Query.ScanQuery(null)).GetAll();*
>> sw.Stop();
>> Console.WriteLine($"Time for fetching all data:
>> {sw.ElapsedMilliseconds} ms for rows: {rows}");
>> }
>> }
>>
>> //Actually below one is generic method(for simplicity changed to
>> non-generic)
>> private static ConcurrentDictionary
>> CreateMapFromList(IEnumerable collection)
>> {
>> var map = new ConcurrentDictionary();
>> if (collection != null && collection.Any())
>> {
>> foreach (EmpDataSet item in collection)
>> {
>> var val = SerializedEntity(item);
>> if (!string.IsNullOrWhiteSpace(val))
>> {
>> map.TryAdd(item.DtId, val);
>> }
>> }
>> }
>> return map;
>> }
>>
>>
>> private static List GetData(int rows = 7000)
>> {
>> Random rand = new Random();
>>
>> var lst = new List();
>> for (int i=1; i<=rows;i++)
>> {
>> var obj1 = new EmpDataSet();
>> obj1.DtId = i;
>> obj1.EmpRef = rand.Next(rows + rows);
>> obj1.DtName = RandomString(rand.Next(15, 20));
>> obj1.DraftDtId = rand.Next(rows + rows);
>> obj1.ApprovedDtId = rand.Next(rows + rows);
>> obj1.Description = RandomString(rand.Next(20, 60));
>> obj1.Code1 = RandomString(rand.Next(1, 10),
>> Convert.ToBoolean(rand.Next(0, 1)));
>> obj1.Code2 = RandomString(rand.Next(1, 10),
>> 

Re: Could not create .NET CacheStore

[Pavel Tupitsyn]

Yes, you can create a cache template in two ways:
* At startup: add IgniteConfiguration.CacheConfiguration where Name has an
asterisk in it, like 'cache-foo-*'
* After startup: Ignite.AddCacheConfiguration, same thing with `*` in the
Name

After that, when you call CreateCache(string name), and the name
matches the template name,
settings from the template are applied:

ignite.CreateCache("cache-foo-1")


On Sat, Jan 18, 2020 at 8:27 AM siva  wrote:

> Hi,
>
> Thanks for reply.It's working fine now after added cache configuration and
> factory classes.
>
> so Is there any way like cache creation time create template and later for
> all other client can access same temple for the crossponding cache
> configuration?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

JVM crashed with SIGSEGV with stack trace to OptimizedObjectOutputStream.writeObject

[tarunk]

Hi All,

In our 12 nodes ignite cluster one of the node jvm get crashes sometimes
with below error.
Is this some know issue with Ignite ? or some other memory/jvm issue.
We are using openjdk 1.8 ("1.8.0_232") provided by RedHat.

A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fef7f1d3eb0, pid=42623, tid=0x7feea62c8700
#
# JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build
1.8.0_222-b10)
# Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# J 62683 C2
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(Ljava/lang/Object;)V
(331 bytes) @ 0x7fef7f1d3eb0 [0x7fef7f1d3e00+0xb0]
#
# Failed to write core dump. Core dumps have been disabled. To enable core
dumping, try "ulimit -c unlimited" before starting Java again




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