Unexpected flag value

[Anil]

Hi,

i am seeing *class org.apache.ignite.binary.BinaryObjectException:
Unexpected flag value *when i run a query.

What could be the actual root cause of this issue ? i have attached the
complete stack trace.

But the query is running fine when i run explicitly.

I can provide the sudo code for the scenario if required. thanks,

Thanks.

rx.exceptions.OnErrorNotImplementedException: Failed to query Ignite.
at 
rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(InternalObservableUtils.java:386)
at 
rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(InternalObservableUtils.java:383)
at rx.internal.util.ActionSubscriber.onError(ActionSubscriber.java:44)
at rx.observers.SafeSubscriber._onError(SafeSubscriber.java:153)
at rx.observers.SafeSubscriber.onError(SafeSubscriber.java:115)
at 
com.test.ignite.IgniteJdbcTemplate.lambda$null$1(IgniteJdbcTemplate.java:32)
at rx.internal.util.ActionSubscriber.onError(ActionSubscriber.java:44)
at rx.observers.SafeSubscriber._onError(SafeSubscriber.java:153)
at rx.observers.SafeSubscriber.onError(SafeSubscriber.java:115)
at 
io.vertx.rx.java.ObservableOnSubscribeAdapter.fireError(ObservableOnSubscribeAdapter.java:87)
at 
io.vertx.rx.java.ObservableFuture$1.dispatch(ObservableFuture.java:61)
at 
io.vertx.rx.java.ObservableFuture$HandlerAdapter.handle(ObservableFuture.java:32)
at 
io.vertx.rx.java.ObservableFuture$HandlerAdapter.handle(ObservableFuture.java:12)
at io.vertx.core.impl.FutureImpl.checkCallHandler(FutureImpl.java:158)
at io.vertx.core.impl.FutureImpl.setHandler(FutureImpl.java:100)
at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:279)
at 
io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:324)
at 
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at 
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:445)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Failed to query Ignite.
at 
org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(JdbcStatement.java:149)
at 
org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:64)
at 
org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83)
at 
org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83)
at com.test.ignite.JDBCQuery.executeStatement(JDBCQuery.java:45)
at com.test.ignite.JDBCQuery.execute(JDBCQuery.java:37)
at com.test.ignite.JDBCQuery.execute(JDBCQuery.java:14)
at com.test.ignite.JDBCHandler.handle(JDBCHandler.java:42)
at com.test.ignite.JDBCHandler.handle(JDBCHandler.java:28)
at 
io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:263)
at 
io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor.lambda$new$0(OrderedExecutorFactory.java:94)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Unexpected 
flag value [pos=340, expected=9, actual=4]
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlagNoHandles(BinaryReaderExImpl.java:1424)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readString(BinaryReaderExImpl.java:935)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readString(BinaryReaderExImpl.java:930)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:707)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:639)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:829)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1498)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
at 

Re: Data streamers: How to ensure loading data for the current partition only

[Sumanta Ghosh]

Hi Val,
Thanks a lot - yes, the problem I mentioned does not exist if the data
streamer run on a single node. However, this raises another question though.
How to ensure that data streamers run on a single node only? Is it done by
ignite automatically? If not, can you suggest any best practice for that?
I am running a single sprint boot application which also starts ignite. In
order to keep the deployment simple, I was trying to avoid a dedicated node
for ignite only. 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Data-streamers-How-to-ensure-loading-data-for-the-current-partition-only-tp10949p10960.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Failure to start a bigger ignite cluster.

[atricuix]

Hi Andrey,

Thanks for looking into this.

A bit confused. We use only one JVM per box and each ignite server JVM has a
different IP address.
So by default localPort() also uses 100 ports starting 47100 / 47500. We
have already opened the entire range in our ingress security rules.

I did not understand the sharedMemory part. Are you suggesting to disable it
as we use a VM?

Thanks,
Aswin



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failure-to-start-a-bigger-ignite-cluster-tp10852p10959.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to use H2 database functions in the Sql query using .Net APIs

[Sergi Vladykin]

Currently you have to write your SQL functions in Java.

Sergi

2017-02-28 19:51 GMT+03:00 mrinalkamboj :

> Thanks @Sergi, this is Java code, will it work in a similar way for .Net
> too
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/How-to-use-H2-database-functions-in-
> the-Sql-query-using-Net-APIs-tp10939p10950.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: SpringTransactionManager - Participating in existing transactions is not supported

[vkulichenko]

Please refer to this page for all the information about contributing and
process description:
https://ignite.apache.org/community/contribute.html#contribute

I don't think there is a ticket for this issue, so first thing would be to
create it.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/SpringTransactionManager-Participating-in-existing-transactions-is-not-supported-tp7305p10957.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Lucene like Contains phrase query

[vkulichenko]

Ranjit,

It looks like you don't have Ignite libraries on Spark executor's classpath.
Please refer to Spark documentation for information on how to do this. You
will probably use 'spark.jars.packages' or similar.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Lucene-like-Contains-phrase-query-tp10808p10956.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: backup to swap

[vkulichenko]

Anil,

As discussed before, you can try to implement your own eviction policy to
achieve what you want to achieve. See Andrey's suggestion on how to check if
a node is primary or backup.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/backup-to-swap-tp10255p10953.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: upsert example??

[Andrey Mashenkov]

Hi Cris,

Please, take a look at EntryProcessor.
It has atomicity guarantee, but be ware it can be called more than once for
each entry.

On Tue, Feb 28, 2017 at 6:14 AM, Chris Berry  wrote:

> Hi,
>
> I am attempting to convert an existing application to use Apache Ignite.
>
> The current logic does an “upsert”  from a stream of data. And it will be
> very difficult to modify the existing code.
>
> Something like this:
>
> *public void *upsertEntry(TKey key, NewInstanceFunctor
> newInstFunc, UpsertFunctor upsertFunc) {
> TValue document = getAndNewIfReqd(key, newInstFunc);
> document = upsertFunc.modifyForUpsert(document);
> getIgniteCache().put(key, document);
> }
>
> public TValue getAndNewIfReqd(TKey key, NewInstanceFunctor
> newInstFunc) {
> TValue document = getEntry(key);
> if (document == null) {
> document = newInstFunc.newInstance();
> getIgniteCache().put(key, document);
> }
> return document;
> }
>
> So, in pseudo-code
> 1) get the document from the cache
> 2) if null, create a document and put it to the cache
> 3) modify the document
> 4) put the updated document to the cache
>
> This is clearly inefficient.
> I am pretty certain that I can accomplish this using a DataStreamer and a
> StreamTransformer??
> I wonder if someone could point me at an example of how to do this??
>
> Thanks,
> — Chris
>
>
>
>
>
>
>



-- 
Best regards,
Andrey V. Mashenkov

Data streamers: How to ensure loading data for the current partition only

[Sumanta Ghosh]

Hi,
Want to ensure that data streamer in each node only loads the relevant data
for that node (I am assuming that data streamers are running in all nodes
that are up).
In the documentation - in the Cache loader, it mentions about storing
affinity key in DB and then retrieve the data based on affinity key. Will
the same apply for data streamers as well? If yes, what is the good way to
update the affinity key in case there is addition of node in the cluster?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Data-streamers-How-to-ensure-loading-data-for-the-current-partition-only-tp10949.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: SpringTransactionManager - Participating in existing transactions is not supported

[Sumanta Ghosh]

Hi Val,
Thanks for the reply. Basically its a very small fix (below); however, I am
new to Ignite and hence not sure if this covers all the scenarios. Also,
this is the first time I would be contributing anything to ignite community,
so please let me know the process as well (in case the below code make
sense).

@Override
protected void doSetRollbackOnly(DefaultTransactionStatus status) throws
TransactionException {
Transaction txn = 
((Ignite)this.getResourceFactory()).transactions().tx();
if (txn!=null) txn.setRollbackOnly();
}



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/SpringTransactionManager-Participating-in-existing-transactions-is-not-supported-tp7305p10947.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Renaming a cache

[Andrey Gura]

Hi, Steve

Cache couldn't be renamed. Only way to copy cache entries is read all
entries from one cache and insert entries into another cache.

Of course you can implement partition aware copy in order to reduce
network traffic and performance penalty.

On Tue, Feb 28, 2017 at 4:46 PM, steve.hostettler
 wrote:
> Hello all,
>
> currently, we have one cache per validity date. The validity date being part
> of the cache name. We are considering delta loading and therefore I would
> like to know whether it is possible to rename or quickly copy a cache
> (without doing it at a  per entry level).
>
> Many thanks in advance
>
>
>
>
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Renaming-a-cache-tp10943.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: cache namespace support

[Andrey Gura]

Hi,

There is no such concept as namespace in Ignite. I think tha both ways
is acceptable but it depends on your requirements and there is no
silver bullet.

On Tue, Feb 28, 2017 at 4:16 AM, shawn.du  wrote:
> Hi,
>
> I have a use case like below:
> I want to store key-value caches in ignite, but each key-value has a
> namespace. key are unique in a namespace.
> Each cache entry has the same data type for both key and value.
> When query, We always query by key and namespace.
> sometimes, we query all caches of a namespace or remove all entries in one
> namespace.
>
> I think there are two solutions:
> #1 create cache for each namespace, like use namespace as the cache name.
>   using the approach, there may many caches in ignite.  IMO, it is a bit
> dirty, I meant when using ignitevisor to show caches
>   you will see many caches.
> #2 create one cache, each cache entry has namespace,key and value. using
> (namespace,key) as the cache key.
>   This solution is clean. but you have to create a static class/complex
> configuration. also you have to use SQL to query all/remove all
>   data in a namespace.
>
> I think this is a very common use case. Can ignite support it in  lower
> layer for solution clean and  better performance?
> welcome your comments.
>
> Thanks
> Shawn
>

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

[Andrey Gura]

> The long pause is between 2 different threads, so isn't that normal?

Usually it is not normal. So need some investigation in order to
understand why this pause happens.

> Also the 9990 ms and 10 ms used earlier for some previous step in the tn, is
this how ignite breaks out the time?

When Ignite starts transaction on initial node it pass timeout to
tranasction. After mapping keys on nodes of cluster Ignite starts
transactions on remote nodes and pass remaining transaction time to
it. So it is possible that it is your case.

> Is there any way we can force release a locked key without restarting the
whole cluster?

There is no such way.

On Mon, Feb 27, 2017 at 5:39 PM, bintisepaha  wrote:
> Andrey, thanks for getting back.
> The long pause is between 2 different threads, so isn't that normal?
>
> Also the 9990 ms and 10 ms used earlier for some previous step in the tn, is
> this how ignite breaks out the time? we have always seen the timeouts for
> the value in ms that we set in our code. Also the stack trace does not come
> from our code which it usually does on genuine timeouts that do not leave
> the key locked.
>
> We are trying 1.8 in UAT environment and will release to production soon.
> Unfortunately this issue does not happen in UAT and we have no way of
> reproducing it.
>
> Is there any way we can force release a locked key without restarting the
> whole cluster?
>
> Thanks,
> Binti
>
>
>
>
>
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p10910.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to use H2 database functions in the Sql query using .Net APIs

[Sergi Vladykin]

Sorry, right now Ignite uses an older H2 version. I hope we will be able to
upgrade it soon, but for now you can go with user defined functions [1].

[1]
https://ignite.apache.org/releases/1.8.0/javadoc/org/apache/ignite/cache/query/annotations/QuerySqlFunction.html

Sergi

2017-02-28 15:13 GMT+03:00 mrinalkamboj :

> I am trying to use the following query from the .Net client:
>
> *select _key,OrderId, OrderName, OrderDateTime, OrderValue, OrderAddress
> from OrderEntity Where REGEXP_LIKE(OrderAddress,?)*
>
> Where for the placeholder ?, I supply the valid Regular expression, but
> following is exception generated:
>
> *Caused by: org.h2.jdbc.JdbcSQLException: Function "REGEXP_LIKE" not found;
> SQL statement: select _key,OrderId, OrderName, OrderDateTime, OrderValue,
> OrderAddress from OrderEntity Where REGEXP_LIKE(OrderAddress,?)*
>
> I can use the Like operator effectively, as follows, but that's not enough
> I
> need to do complex regex mapping
>
> *select OrderId, OrderName, OrderDateTime, OrderValue, OrderAddress from
> OrderEntity Where OrderAddress like '%' || ?*
>
> This also seems to be the case for other H2 database functions available at
> the following link
>
> http://www.h2database.com/html/functions.html
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/How-to-use-H2-database-functions-in-
> the-Sql-query-using-Net-APIs-tp10939.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Same Affinity For Same Key On All Caches

[Andrey Mashenkov]

Hi Val,

Assume, we have A-B-A topology and we have X,Y caches of single partition
(just for simplicity)  with 1 backup and same afinity function.
Obviously, every node contains all partitions of both caches.
Now, we can have on nodeA:  X as primary and Y as backup
On nodeB: X as backup and Y as primary.

So, for same key data of both caches is collocated, but primary node
differs.

As far as I know, Rendezvous move partitions only to newly added node while
Fair can move partitions among all nodes.

It is possible I am wrong, but IHMO

It looks like partitions partition primary and backups creates in order and
do not reassign after exchange.
E.g. for topology A-B-C-D-A:
Newly created cache will have partition 'x' primary on A and backups on
B,C, partition 'y' primary on B and backups on C,D and etc.
After adding node E, some primary will be moved to it and order will be
broken. E.g 'y' can become primary on E and backups on C,D.
Now if we add new cache, we wil have for 'y' C as primary and D,E as backup.

Possible we just have wrong node order in partition->node mapping.

Can somebody clarify how primary partition is assigned?

On Tue, Feb 28, 2017 at 9:56 AM, Alper Tekinalp  wrote:

> Hi Val,
>
> We are using fair affinity function because we want to keep data more
> balanced among nodes. When I change "new FairAffinityFunction(128)"  with
> "new RendezvousAffinityFunction(false, 128)" I could not reproduce the
> problem.
>
>
> On Tue, Feb 28, 2017 at 7:15 AM, vkulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Andrey,
>>
>> Is there an explanation for this? If this all is true, it sounds like a
>> bug
>> to me, and pretty serious one.
>>
>> Alper, what is the reason for using fair affinity function? Do you have
>> the
>> same behavior with rendezvous (the default one)?
>>
>> -Val
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Same-Affinity-For-Same-Key-On-All-Caches-
>> tp10829p10933.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
> 
>



-- 
Best regards,
Andrey V. Mashenkov

How to use H2 database functions in the Sql query using .Net APIs

[mrinalkamboj]

I am trying to use the following query from the .Net client:

*select _key,OrderId, OrderName, OrderDateTime, OrderValue, OrderAddress
from OrderEntity Where REGEXP_LIKE(OrderAddress,?)*

Where for the placeholder ?, I supply the valid Regular expression, but
following is exception generated:

*Caused by: org.h2.jdbc.JdbcSQLException: Function "REGEXP_LIKE" not found;
SQL statement: select _key,OrderId, OrderName, OrderDateTime, OrderValue,
OrderAddress from OrderEntity Where REGEXP_LIKE(OrderAddress,?)*

I can use the Like operator effectively, as follows, but that's not enough I
need to do complex regex mapping

*select OrderId, OrderName, OrderDateTime, OrderValue, OrderAddress from
OrderEntity Where OrderAddress like '%' || ?*

This also seems to be the case for other H2 database functions available at
the following link

http://www.h2database.com/html/functions.html



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-use-H2-database-functions-in-the-Sql-query-using-Net-APIs-tp10939.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Node fauliure

[Andrey Mashenkov]

Hi Anil,

Unfortunatelly, I have no luck to reproduce it.

On Mon, Feb 27, 2017 at 3:21 PM, Anil  wrote:

> Hi Andrey,
>
> thanks for looking into it. could you please share more details around the
> bug ? this helps us.
>
> Thanks.
>
> On 27 February 2017 at 17:27, Andrey Mashenkov 
> wrote:
>
>> Thanks, It was very helpful.
>>
>> Seems, Offheap with swap enabled funcionality has a bug.
>>
>> On Mon, Feb 27, 2017 at 2:46 PM, Anil  wrote:
>>
>>> Hi Andrey,
>>>
>>> I set both off heap cache and swap enabled = true.
>>>
>>> Thanks
>>>
>>> On 27 February 2017 at 16:48, Andrey Mashenkov <
>>> andrey.mashen...@gmail.com> wrote:
>>>
 Hi Anil,

 One more question. Did you use Offheap cache or may be SwapEnabled=true
 is set?


 On Sat, Feb 25, 2017 at 5:14 AM, Anil  wrote:

> Thank you Andrey.
>



 --
 Best regards,
 Andrey V. Mashenkov

>>>
>>>
>>
>


-- 
Best regards,
Andrey V. Mashenkov

Re: getOrCreateCache hang

[Nikolai Tikhonov]

I am not able reproduce exactly your test (do not have Postgre instance),
 but I do not get hangs on start caches. I suppose that issue related with
your setup and for getting cause of problem I need full logs and thread
dumps (by kill -3 PID or jstack) from all nodes. Could you please provide
this data?

On Mon, Feb 27, 2017 at 10:36 PM, Matt Warner 
wrote:

> Something's not right. I'm seeing this as 100% reproducible on two
> different OSes.
>
> Are you running "mvn package" on both testIgnite1 and testIgnite2 and then
> starting the shaded JARs simultaneously from two different shell windows
> using "java-jar ignite?...-standalone.jar"?
>
> Matt
>
> On Feb 27, 2017, at 8:58 AM, Nikolai Tikhonov 
> wrote:
>
> I was not able reproduce it. Could you share full logs and thread dumps
> from all nodes?
>
> On Mon, Feb 27, 2017 at 7:45 PM, Matt Warner 
> wrote:
>
>> Using the test code I sent previously, I changed the ports to be a range
>> but both clients still deadlock on getOrCreateCache.
>>
>> Are you able to reproduce this using the test code I sent?
>>
>> Matt
>>
>>
>> On Mon, Feb 27, 2017 at 3:02 AM, Nikolai Tikhonov 
>> wrote:
>>
>>> Hi Matt!
>>>
>>> Try to change ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500")); to
>>> ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500..47505"));
>>>
>>> On Fri, Feb 24, 2017 at 4:00 PM, Matt Warner 
>>> wrote:
>>>
 Hi Nikolai.

 I discovered the reason the two applications weren't seeing each other
 was resolved by adding an explicit port number (Arrays.asList("
 127.0.0.1:47500")). However, the two still deadlock when running
 concurrently.

 The latest test shows one application blocked in getOrCreateCache, the
 other blocked in Ignition.start. As soon as I kill the process stuck in
 Iginition.start the other process continues successfully. I've attached the
 latest test code.

 Any ideas?

 Matt

 On Wed, Feb 22, 2017 at 10:30 AM, Matt Warner [via Apache Ignite Users]
 <[hidden email] >
 wrote:

> One other observation: with the third application acting as just the
> server, and just one of the clients running, there is no issue. Only when
> there are multiple clients do I get the deadlock on getOrCreateCache.
>
> Matt
>
> --
> If you reply to this email, your message will be added to the
> discussion below:
> http://apache-ignite-users.70518.x6.nabble.com/getOrCreateCa
> che-hang-tp10737p10811.html
> To unsubscribe from getOrCreateCache hang, click here.
> NAML
> 
>


 *testIgnite.tar.gz* (14K) Download Attachment
 

 --
 View this message in context: Re: getOrCreateCache hang
 

 Sent from the Apache Ignite Users mailing list archive
  at Nabble.com.

>>>
>>>
>>
>