date:20170324

Hi Igor,

First I will explain you what I did. successfully build the solution from
the location
F:\Apache\apache-ignite-fabric-1.9.0-bin\apache-ignite-fabric-1.9.0-bin\platforms\cpp\project\vs\ignite.sln.
Then executed the command Install_amd64  to install
ignite driver. After that created DSN like below screenshot.
 

My console application code is:
using System.Data;
using Apache.Ignite.Core;
using System.Data.Odbc;

namespace CreateCluster
{
class Program
{
static void Main(string[] args)
{
IIgnite ignite =
Ignition.Start(@"F:\Visual
Studio2015\Projects\CreateCluster\CreateCluster\my-file.xml"));
var cache = ignite.GetOrCreateCache("Person");
cache.Put(1, "John");
cache.Put(2, "Smith");
cache.Put(3, "Vinet");
cache.Get(1);
cache.Get(2);
cache.Get(3);
}
}
}

my-file.xml code:



http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xmlns:util="http://www.springframework.org/schema/util;
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;>
  



  

 
  

  

  

  


  

  

  




If I run console application, node is started. 
My problem is, no data exist in database while connecting through ignite
ODBC driver.

Can you please help me, what will do to display data?



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

Re: Apache Ignite Query Entity String Array

2017-03-24 Thread tolga

Thanks a lot.

On Thu, Mar 23, 2017, 11:15 AM dkarachentsev [via Apache Ignite Users] <
ml-node+s70518n11385...@n6.nabble.com> wrote:

> Hi,
>
> You need to set value="L[java.lang.String;" and for querying you may use
> array_contains function. For example:
> ... WHERE array_contains(ABC, ?);
>
> Thanks!
>
> -Dmitry.
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-Query-Entity-String-Array-tp11368p11385.html
> To unsubscribe from Apache Ignite Query Entity String Array, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-Query-Entity-String-Array-tp11368p11441.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Presenting Apache Ignite at European and US conferences

2017-03-24 Thread Denis Magda

Folks,

I’m pleased to say that if you live in Russia or have a chance to go there in 
the very beginning of April then you shouldn’t miss a chance  to join Yakov 
Zhdanov’s and Vladimir Ozerov’s talks they do at JBreak and JPoint conferences:

- Yakov: Scalability in Distributed In-Memory Systems, JBreak 2017, 
Novosibirsk, Russia
   
https://2017.jbreak.ru/en/talks/scalability-in-distributed-in-memory-systems/  

- Vladimir: Scalability in Distributed In-Memory Systems, JPoint 2017, Moscow, 
Russia
  https://jpoint.ru/talks/scalability-in-distributed-in-memory-systems/

Ignite’s news page has been updated: https://ignite.apache.org/news.html

Please support our committers by twitting around:
https://twitter.com/ApacheIgnite/status/845344456098246657 

https://twitter.com/ApacheIgnite/status/845345221101568000 


—
Denis


> On Mar 22, 2017, at 5:17 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> Let me share with you a list of nearest conferences joining which you can 
> learn more about Ignite. Check the news page for more details:
> https://ignite.apache.org/news.html
> 
> - Introduction to Apache Ignite, March 24, Codemotion Rome, Mandhir Gidda:
>  
> http://rome2017.codemotionworld.com/wp-content/themes/event/detail-talk.php?detail=5799
> 
> - Apache Ignite SQL Grid, March 28, Big Data Bootcamp, Denis Magda:
>  https://blogs.apache.org/ignite/entry/presenting-apache-ignite-sql-grid
> 
> - Apache Ignite SQL Grid, March 30, PG Conf US, Denis Magda:
>  http://pgconf.us/conferences/2017/program/proposals/340
> 
> - Accelerate MySQL® for Demanding OLAP and OLTP Use Cases with Apache® 
> Ignite™, 25 April, Percona Live, Nikita Ivanov:
>  
> https://www.percona.com/live/17/sessions/accelerate-mysql®-demanding-olap-and-oltp-use-cases-apache®-ignite™-0
> 
> 
> —
> Denis
> 
> 
>

Re: Logging ignite-log4j.jar

2017-03-24 Thread javastuff....@gmail.com

Thanks Andrey.

Looked at code and seems like check for log configuration is made, 
/if(!isConfigured()) {
this.impl.setLevel(Level.OFF);
}/

but not completely correct. Below is the method from Log4JLogger

/public static boolean isConfigured() {
return Logger.getRootLogger().getAllAppenders().hasMoreElements();
} /

It is looking at appenders from rootLogger only. It should also check for
other Loggers. Probably below code should fix it.

/public static boolean isConfigured() {
Enumeration appenders = Logger.getRootLogger().getAllAppenders();
if (appenders.hasMoreElements()) {
return true;
}
else {
Enumeration loggers = LogManager.getCurrentLoggers() ;
while (loggers.hasMoreElements()) {
Logger c = (Logger) loggers.nextElement();
if (c.getAllAppenders().hasMoreElements())
return true;
}
}
return false;
}/

Thanks,
-Sam



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Logging-ignite-log4j-jar-tp11400p11439.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NullPointerException when using IGFS

2017-03-24 Thread joewang

Yes--we were experiencing this in 1.8 before upgrading to 1.9.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-when-using-IGFS-tp11328p11438.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: New version of Web Console released.

2017-03-24 Thread Denis Magda

Great job Alex! Thanks for making the console more compelling with every 
release!

—
Denis

> On Mar 24, 2017, at 12:06 AM, Alexey Kuznetsov  
> wrote:
> 
> Igniters!
> 
> I'd like to announce that we just pushed new version of Ignite Web Console to 
> master branch
>  and redeployed the new version on GridGain infrastructure 
> (https://console.gridgain.com ) where you can 
> give it a try right a way.
> 
> NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web 
> Console.
> 
> What's new:
> 
>   * Build with WebPack 2.
>   * Added support for "Enforce join order" on Queries screen.
>   * Improved errors handling on Queries screen. Now in case of error you will 
> see message from root cause.
>   * Added "Running queries" screen that will show "long running queries" and 
> ability to cancel selected queries.
>   * Added tracking of Web Console features usage on "Admin Panel" screen, 
> descibed here: https://apacheignite-tools.readme.io/docs/usage-tracing 
> 
> 
> -- 
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com

Re: Missing records Ignite cache size grows

Hi diopek,

I can't see how cache size relates to value classes and value object
content.

I rework my test and still can't reproduce this issue even with 2 millions
of entries in cache, but you mention about a half a million.

On Fri, Mar 3, 2017 at 6:25 PM, diopek  wrote:

> Hi Andrew,
> Difference in your repro;
> your cache entry is >,
> and you always add single entry to value ArrayList
> in our case
> >
> MyPOJO is java bean that has ~30 attributes.
> and ArrayList might have sometimes 100s of objects.
> During my local tests, that I am using ~20GB of RAM, I couldn't reproduce
> either.
> Issue occurs with high number of records with production data on servers
> with larger amount of RAM.
> I am wondering if you can try to replicate that scenario on your end.
> Thanks
>
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Missing-records-Ignite-cache-size-
> grows-tp10809p11022.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov
import java.io.Serializable;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.concurrent.ThreadLocalRandom;
import java.util.stream.LongStream;
import javax.cache.configuration.FactoryBuilder;
import javax.cache.integration.CacheLoaderException;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.Ignition;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.store.CacheLoadOnlyStoreAdapter;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.lang.IgniteBiTuple;

/**
 * Can't reproduced.
 */
public class MissedEntries {
/** */
private static final int CACHE_SIZE = 2_000_000;

/** */
private static CacheConfiguration cacheConfig(String cacheName) {
CacheConfiguration cacheCfg = new CacheConfiguration<>(cacheName);
cacheCfg.setStartSize(CACHE_SIZE);
cacheCfg.setCacheMode(CacheMode.LOCAL);
cacheCfg.setIndexedTypes(Long.class, ArrayList.class);

cacheCfg.setCacheStoreFactory(FactoryBuilder.factoryOf(MyCacheLoadOnlyStore.class));

return cacheCfg;
}

/** */
public static void main(String[] args) {
try {
Ignite ignite = Ignition.start(new IgniteConfiguration().setGridName("node-0"));

IgniteCache cache = ignite.getOrCreateCache(cacheConfig("myCache"));

cache.loadCache(null);

int size = cache.size();

if (CACHE_SIZE != size)
throw new AssertionError("Data lost: "+size);
}
finally {
Ignition.stopAll(true);
}
}

/**
 *
 */
public static class MyCacheLoadOnlyStore extends CacheLoadOnlyStoreAdapter {
/** {@inheritDoc} */
@Override protected Iterator inputIterator(Object... args) throws CacheLoaderException {
return LongStream.range(0, CACHE_SIZE).iterator();
}

/** {@inheritDoc} */
@Override protected IgniteBiTuple parse(Long rec, Object... args) {
final int size = ThreadLocalRandom.current().nextInt(50);

ArrayList val1 = new ArrayList<>(size);

for (int i = 0; i < size; i++)
val1.add(MyObj.createRandom());

if(rec % 10_000 == 0)
System.out.println("Generated: "+rec);

return new IgniteBiTuple<>(rec, val1);
}
}

public static class MyObj implements Serializable {
int field1;

int field2;

int field3;

String field4;

String field5;

public MyObj(int field1, int field2, int field3, String field4, String field5) {
this.field1 = field1;
this.field2 = field2;
this.field3 = field3;
this.field4 = field4;
this.field5 = field5;
}

static MyObj createRandom() {
final ThreadLocalRandom random = ThreadLocalRandom.current();

return new MyObj(
random.nextInt(20),
random.nextInt(50, 70),
random.nextInt(100, 120),
String.valueOf(random.nextInt(100)),
String.valueOf(random.nextInt(1000))
);
}
}
}

Re: Logging ignite-log4j.jar

Hi Sam.
I've created a ticket [1].

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

On Fri, Mar 24, 2017 at 1:50 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Hi Sam,
>
> 1. Looks like a bug. I think Ignite should not raise log level when adding
> console appender.
> Setting System property "IGNITE_CONSOLE_APPENDER" to true will set
> rootLogger level to OFF that can be unexpectedly as well.
> Seems, we should check if there is no other loggers configured which can
> inherits rootLogger logging level before turning rootLogger off.
>
> Right?
>
> 2. You can configure ConsoleAppender for RootLogger explicitly. Or
> override logging Level for other loggers.
>
>
>
> On Thu, Mar 23, 2017 at 11:41 PM, javastuff@gmail.com <
> javastuff@gmail.com> wrote:
>
>> Hi
>>
>> My application already uses Log4j for logging, simply adding
>> ignite-log4j.jar enables Ignite logging. I also added a new logger
>> configuration for package "org.apche.ignite" in my application logging
>> configuration, so that Ignite can log into a separate rolling file.
>> Ignite logging working fine. However rootLogger log level is changed to
>> INFO
>> by Ignite initialization, which is problematic for my application logging.
>>
>> Ignite configuration file does not have configuration for GridLogger, so
>> at
>> initialization it tries to add a new consoleAppender with INFO level by
>> instantiating Log4JLogger(), here it also updates rootLogger to INFO.
>>
>> Question -
>> 1. Why does Ignite need to update rootLogger log level?
>> 2. Is this not the good way to configure logging for ignite using
>> ignite-log4j.jar?
>>
>> Thanks
>> -Sam
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Logging-ignite-log4j-jar-tp11400.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>



-- 
Best regards,
Andrey V. Mashenkov

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

2017-03-24 Thread bintisepaha

Hey Andrey, Thanks a lot for getting back.

These errors were a result of a bad client connected to grid.

We have been running clients that leave and join the cluster constantly in
order to see if we can reproduce this issue. Last night we saw this issue
again. Here is one of the errors that a sys thread has on a client node that
initiates a transaction. The client node was not restarted or disconnected.
It kept working fine.
We do not restart these clients but there are some otehr clietns that leave
and join the cluster.

Do you think this is helpful in locating the cause?

Exception in thread "sys-#41%DataGridServer-Production%"
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxKey.finishUnmarshal(IgniteTxKey.java:92)
at
org.apache.ignite.internal.processors.cache.transactions.TxLocksResponse.finishUnmarshal(TxLocksResponse.java:190)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.unmarshall(IgniteTxManager.java:2427)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.onMessage(IgniteTxManager.java:2317)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1238)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:866)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:829)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[20:02:18] Topology snapshot [ver=7551, servers=16, clients=53, CPUs=217,
heap=740.0GB]
[20:02:22] Topology snapshot [ver=7552, servers=16, clients=52, CPUs=213,
heap=740.0GB]
[20:02:28] Topology snapshot [ver=7553, servers=16, clients=53, CPUs=217,
heap=740.0GB]
[20:02:36] Topology snapshot [ver=7554, servers=16, clients=54, CPUs=217,
heap=740.0GB]
[20:02:40] Topology snapshot [ver=7555, servers=16, clients=53, CPUs=217,
heap=740.0GB]
[20:02:41] Topology snapshot [ver=7556, servers=16, clients=54, CPUs=217,
heap=740.0GB]
[20:02:48] Topology snapshot [ver=7557, servers=16, clients=53, CPUs=217,
heap=740.0GB]




--
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-tp10536p11433.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: cache replication factor

2017-03-24 Thread dkarachentsev

Hi Tuco,

You're speaking about PARTITIONED cache with custom number of backups [1,
2]. You may specify how many copies partition will have. For example, You
have 3 nodes and number of backups set to 1, that means each partition has 1
copy on other node. In other words, if one node failed - you'll not lose
data. If number of backups 2 - 2 nodes could be failed without data loose,
and so forth.

[1] https://apacheignite.readme.io/v1.8/docs/cache-modes#partitioned-mode
[2]
https://ignite.apache.org/releases/mobile/org/apache/ignite/configuration/CacheConfiguration.html#setBackups(int)

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/cache-replication-factor-tp11409p11432.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NullPointerException when using IGFS

2017-03-24 Thread dkarachentsev

Joe,

It seems a bug, I've filed a ticket [1]. Could you please check if this
problem exists in 1.8 version?

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

Thanks!

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-when-using-IGFS-tp11328p11431.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Load data to cache

Please, share your final code. Also, can you share ODBC code?

Best Regards,
Igor

On Fri, Mar 24, 2017 at 3:42 PM, kavitha  wrote:

> Hi,
>
> I changed my QueryEntity as you suggested. But still my database is empty.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Load-data-to-cache-tp11394p11429.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Load data to cache

Hi,

I changed my QueryEntity as you suggested. But still my database is empty.



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

Re: Issue with automatic persistence

Hi Alper,

Got it.

You can try to clean ignite work directory.
If it wouldn't help try to check it against ignite-1.8-1.9 or get GridGain
support, as it can be a regression or already fixed.

On Fri, Mar 24, 2017 at 3:23 PM, Alper Tekinalp  wrote:

> Hi Andrey,
>
> I did not provide any logs only specified the line that mentioned on
> previous message:
>
> *Failed to register marshalled class for more than 10 times in a row*
> From a double check I recognized that we use ignite from GridGain external
> repository. From their site: "It includes Apache Ignite plus security
> patches and bug fixes which GridGain has contributed to Apache Ignite but
> which have not yet been released."
>
> So based on that comment can I say we use ignite 1.8 or the two versions
> have much difference?
>
>
> On Fri, Mar 24, 2017 at 2:51 PM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
>> Hi Alper,
>>
>> 1. I see ignite-1.5.0.final version in logs you provide.
>> 2. Ignite doesn't have 1.8.3 version.
>>
>> On Fri, Mar 24, 2017 at 2:40 PM, Alper Tekinalp  wrote:
>>
>>> Hi.
>>>
>>> I forget to mention about it but we use Ignite 1.8.3.
>>>
>>> On Fri, Mar 24, 2017 at 12:15 PM, Andrey Mashenkov <
>>> andrey.mashen...@gmail.com> wrote:
>>>
 Hi Alper,

 Possibly, it is a bug [1] fixed in ignite-1.6.

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

 On Fri, Mar 24, 2017 at 10:21 AM, Alper Tekinalp 
 wrote:

> Hi.
>
> We see the following log on our servers:
>
>
> *Failed to register marshalled class for more than 10 times in a row *
> I could not relate it to an error so I dont have any idea about the
> problem. What cause that problem? Can you give a hint?
>
> On Fri, Jun 17, 2016 at 1:22 AM, Denis Magda 
> wrote:
>
>> Hi,
>>
>> Do you see the working below on any of the nodes?
>> *Failed to register marshalled class for more than 10 times in a row *
>>
>> Actually it’s difficult to say what is the exact reason of the issue.
>> Can you upgrade to the latest Ignite version to see if the issue is still
>> reproducible?
>>
>> —
>> Denis
>>
>> On Jun 16, 2016, at 2:15 PM, Saurabh Sharma 
>> wrote:
>>
>> Hi,
>>
>> We are using ignite cache with automatic persistence feature for
>> storing the objects in cache. We have objects used as key and value for
>> this cache.
>> Sometimes when we start our application we get the following error
>> while we try to push any value in this cache.
>>
>> It is very random behaviour. It works fine if we try to run the
>> application again.
>> Can someone please suggest if we are missing out something.
>>
>> org.apache.ignite.binary.BinaryObjectException: Failed to get field
>> because type ID of passed object differs from type ID this BinaryField
>> belongs to [expected=-418749773, actual=0]
>> at org.apache.ignite.internal.bin
>> ary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.bin
>> ary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2039)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:1999)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2457)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(Grid
>> H2AbstractKeyValueRow.java:289) ~[ignite-indexing-1.5.0.final.
>> jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:120)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:115)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:107)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at java.util.concurrent.Concurren
>> tSkipListMap.cpr(ConcurrentSkipListMap.java:655) ~[?:1.8.0_77]
>> at java.util.concurrent.Concurren
>>

Re: Issue with automatic persistence

2017-03-24 Thread Alper Tekinalp

Hi Andrey,

I did not provide any logs only specified the line that mentioned on
previous message:

*Failed to register marshalled class for more than 10 times in a row*
>From a double check I recognized that we use ignite from GridGain external
repository. From their site: "It includes Apache Ignite plus security
patches and bug fixes which GridGain has contributed to Apache Ignite but
which have not yet been released."

So based on that comment can I say we use ignite 1.8 or the two versions
have much difference?


On Fri, Mar 24, 2017 at 2:51 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Hi Alper,
>
> 1. I see ignite-1.5.0.final version in logs you provide.
> 2. Ignite doesn't have 1.8.3 version.
>
> On Fri, Mar 24, 2017 at 2:40 PM, Alper Tekinalp  wrote:
>
>> Hi.
>>
>> I forget to mention about it but we use Ignite 1.8.3.
>>
>> On Fri, Mar 24, 2017 at 12:15 PM, Andrey Mashenkov <
>> andrey.mashen...@gmail.com> wrote:
>>
>>> Hi Alper,
>>>
>>> Possibly, it is a bug [1] fixed in ignite-1.6.
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-983
>>>
>>> On Fri, Mar 24, 2017 at 10:21 AM, Alper Tekinalp  wrote:
>>>
 Hi.

 We see the following log on our servers:


 *Failed to register marshalled class for more than 10 times in a row *
 I could not relate it to an error so I dont have any idea about the
 problem. What cause that problem? Can you give a hint?

 On Fri, Jun 17, 2016 at 1:22 AM, Denis Magda 
 wrote:

> Hi,
>
> Do you see the working below on any of the nodes?
> *Failed to register marshalled class for more than 10 times in a row *
>
> Actually it’s difficult to say what is the exact reason of the issue.
> Can you upgrade to the latest Ignite version to see if the issue is still
> reproducible?
>
> —
> Denis
>
> On Jun 16, 2016, at 2:15 PM, Saurabh Sharma 
> wrote:
>
> Hi,
>
> We are using ignite cache with automatic persistence feature for
> storing the objects in cache. We have objects used as key and value for
> this cache.
> Sometimes when we start our application we get the following error
> while we try to push any value in this cache.
>
> It is very random behaviour. It works fine if we try to run the
> application again.
> Can someone please suggest if we are missing out something.
>
> org.apache.ignite.binary.BinaryObjectException: Failed to get field
> because type ID of passed object differs from type ID this BinaryField
> belongs to [expected=-418749773, actual=0]
> at org.apache.ignite.internal.bin
> ary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.bin
> ary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2039)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:1999)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2457)
> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(Grid
> H2AbstractKeyValueRow.java:289) ~[ignite-indexing-1.5.0.final.
> jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:120)
> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:115)
> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
> at org.apache.ignite.internal.pro
> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:107)
> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
> at java.util.concurrent.Concurren
> tSkipListMap.cpr(ConcurrentSkipListMap.java:655) ~[?:1.8.0_77]
> at java.util.concurrent.Concurren
> tSkipListMap.doPut(ConcurrentSkipListMap.java:835) ~[?:1.8.0_77]
> at java.util.concurrent.Concurren
> tSkipListMap.put(ConcurrentSkipListMap.java:1581) ~[?:1.8.0_77]
> at org.apache.ignite.internal.pro
> cessors.query.h2.opt.GridH2TreeIndex.put(GridH2TreeIndex.java:403)
> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
> at

Re: Load data to cache

Well, in your "Person" CacheConfiguration QueryEntity is wrong.

In your code you are creating cache with key of type "java.lang.Integer"
and value of type "java.lang.String", while in your QueryEntity you have
configured it only for types "java.lang.Integer" and "Person".

Best Regards,
Igor

On Fri, Mar 24, 2017 at 3:16 PM, kavitha  wrote:

> Hi Igor,
>
> Yes. I set QueryEntry for cache. But I got empty table.
> My Cache Configuration is:
>
> 
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:util="http://www.springframework.org/schema/util;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;>
>class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
> 
>   
> 
>
>
> 
>   
> 
>   
>   
>   
>   
>
>   
> 
>   
> 
> 
>
> 
>   
> 
> 
> 
>   
> 
>
> 
> 
> 
> 
> 
> 
> 
>   
> 
>   
> 
>
> 
>   
>   
>   
>   
>
>   
> 
>   
> 
> 
>
> 
>   
> 
>   
> 
>
> 
> 
> 
> 
> 
> 
> 
>   
> 
>   
> 
>   
> 
>   
> 
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Load-data-to-cache-tp11394p11425.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Load data to cache

Hi Igor,

Yes. I set QueryEntry for cache. But I got empty table.
My Cache Configuration is:



http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xmlns:util="http://www.springframework.org/schema/util;
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;>
  



  




  

  
  
  
  

  

  




  



  









  

  



  
  
  
  

  

  




  

  









  

  

  

  




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

Re: Very slow cache query compared to H2

Also, I'm pretty sure that 7220 milliseconds is the result you are getting
on the "cold"
JVM. Try warming it up before you are making any benchmarks (i.e. try
running at least
5 queries before you run actual benchmark).

Best Regards,
Igor

On Fri, Mar 24, 2017 at 11:14 AM, Andrey Mashenkov 
wrote:

> Hi Zaid,
>
> Have you try to run query on MySQL or H2 in client server mode?
> In your test, there is an additional overhead on network round-trip and
> data serialization\deserialization. Ignite is designed as distributed
> storage, so complex SQL queries should run faster while you adding new
> nodes.
>
> You can try add more nodes and make some of your cached partitioned to get
> a speed-up due to query will be run in multiple threads (on multiple
> nodes). Speed-up will be as much noticeable as more data should be
> looked-up by data engine. Also you can try to rise up SQl query parallelizm
> level that available from ignite-1.9 to run query in multiple threads
> within single node.
>
> Comparing to Mysql, Ignite gives you failover distributed storage with
> full ACID out-of-the-box for free.
> Of course, it has lacks in some scenarios. E.g. for now, it has bigger
> overhead for simple queries than anyone would expected, but most of SQL
> engine lacks can be overcome with
> carefully data distribution planing and using fast key-value engine in
> some cases.
>
> So, if you plan to use some distributed solution (not Ignite only) you
> should test it in environment as much closer to production as possible, not
> just a execution time of one query on single node.
>
> Thanks.
>
>
>
> On Fri, Mar 24, 2017 at 9:06 AM, zaid  wrote:
>
>> Hi,
>> Thanks for your time looking into the issue. I have modified SlowQuery
>> program and now you should get 10 records as query response.
>>
>> SlowQuery.java
>> > SlowQuery.java>
>>
>> My concern is that we need to decide whether we should continue using
>> MySQL
>> or switch to Ignite SQL.
>> MySQL takes 56 milliseconds to execute the query whereas SQL grid takes
>> 7220
>> milliseconds in client server mode for my use case.
>> Are there any optimizations I can do to reduce Ignite SQL execution time
>> with respect to configuration?
>>
>> Regards,
>> Zaid
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Very-slow-cache-query-compared-to-H2-tp11013p11405.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>

Re: Load data to cache

Hello,

You should set "QueryEntity" for your cache:


  

  

  

  


  

  

  



Best Regards,
Igor

On Fri, Mar 24, 2017 at 2:00 PM, kavitha  wrote:

> Hi,
>
> I set cache name as 'Person' in Ignite ODBC driver.
>
> 
> How Can I load data in it?
> I tried following code to load data. But no tables exist, while connecting
> database through odbc connection. Please explain me how to create database
> ?
> class Program
> {
> static void Main(string[] args)
> {
> IIgnite ignite = Ignition.Start(@"F:Visual Studio
> 2015\Projects\CreateCluster\CreateCluster\my-file.xml");
> var cache = ignite.GetOrCreateCache("Person");
> cache.Put(1, "John");
> cache.Put(2, "Smith");
> cache.Get(1);
> cache.Get(2);
> }
> }
>
> my-file.xml:
> 
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>  class="org.apache.ignite.configuration.IgniteConfiguration">
>   
> 
>   
>  
>  
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Load-data-to-cache-tp11394p11420.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Issue with automatic persistence

Hi Alper,

1. I see ignite-1.5.0.final version in logs you provide.
2. Ignite doesn't have 1.8.3 version.

On Fri, Mar 24, 2017 at 2:40 PM, Alper Tekinalp  wrote:

> Hi.
>
> I forget to mention about it but we use Ignite 1.8.3.
>
> On Fri, Mar 24, 2017 at 12:15 PM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
>> Hi Alper,
>>
>> Possibly, it is a bug [1] fixed in ignite-1.6.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-983
>>
>> On Fri, Mar 24, 2017 at 10:21 AM, Alper Tekinalp  wrote:
>>
>>> Hi.
>>>
>>> We see the following log on our servers:
>>>
>>>
>>> *Failed to register marshalled class for more than 10 times in a row *
>>> I could not relate it to an error so I dont have any idea about the
>>> problem. What cause that problem? Can you give a hint?
>>>
>>> On Fri, Jun 17, 2016 at 1:22 AM, Denis Magda 
>>> wrote:
>>>
 Hi,

 Do you see the working below on any of the nodes?
 *Failed to register marshalled class for more than 10 times in a row *

 Actually it’s difficult to say what is the exact reason of the issue.
 Can you upgrade to the latest Ignite version to see if the issue is still
 reproducible?

 —
 Denis

 On Jun 16, 2016, at 2:15 PM, Saurabh Sharma 
 wrote:

 Hi,

 We are using ignite cache with automatic persistence feature for
 storing the objects in cache. We have objects used as key and value for
 this cache.
 Sometimes when we start our application we get the following error
 while we try to push any value in this cache.

 It is very random behaviour. It works fine if we try to run the
 application again.
 Can someone please suggest if we are missing out something.

 org.apache.ignite.binary.BinaryObjectException: Failed to get field
 because type ID of passed object differs from type ID this BinaryField
 belongs to [expected=-418749773, actual=0]
 at org.apache.ignite.internal.bin
 ary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.bin
 ary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2039)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:1999)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2457)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(Grid
 H2AbstractKeyValueRow.java:289) ~[ignite-indexing-1.5.0.final.
 jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:120)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:115)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:107)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at java.util.concurrent.Concurren
 tSkipListMap.cpr(ConcurrentSkipListMap.java:655) ~[?:1.8.0_77]
 at java.util.concurrent.Concurren
 tSkipListMap.doPut(ConcurrentSkipListMap.java:835) ~[?:1.8.0_77]
 at java.util.concurrent.Concurren
 tSkipListMap.put(ConcurrentSkipListMap.java:1581) ~[?:1.8.0_77]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2TreeIndex.put(GridH2TreeIndex.java:403)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:406)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.opt.GridH2Table.update(GridH2Table.java:340)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:523)
 ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
 at org.apache.ignite.internal.pro
 cessors.query.GridQueryProcessor.store(GridQueryProcessor.java:695)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
 at

Re: Issue with automatic persistence

2017-03-24 Thread Alper Tekinalp

Hi.

I forget to mention about it but we use Ignite 1.8.3.

On Fri, Mar 24, 2017 at 12:15 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Hi Alper,
>
> Possibly, it is a bug [1] fixed in ignite-1.6.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-983
>
> On Fri, Mar 24, 2017 at 10:21 AM, Alper Tekinalp  wrote:
>
>> Hi.
>>
>> We see the following log on our servers:
>>
>>
>> *Failed to register marshalled class for more than 10 times in a row *
>> I could not relate it to an error so I dont have any idea about the
>> problem. What cause that problem? Can you give a hint?
>>
>> On Fri, Jun 17, 2016 at 1:22 AM, Denis Magda  wrote:
>>
>>> Hi,
>>>
>>> Do you see the working below on any of the nodes?
>>> *Failed to register marshalled class for more than 10 times in a row *
>>>
>>> Actually it’s difficult to say what is the exact reason of the issue.
>>> Can you upgrade to the latest Ignite version to see if the issue is still
>>> reproducible?
>>>
>>> —
>>> Denis
>>>
>>> On Jun 16, 2016, at 2:15 PM, Saurabh Sharma 
>>> wrote:
>>>
>>> Hi,
>>>
>>> We are using ignite cache with automatic persistence feature for storing
>>> the objects in cache. We have objects used as key and value for this cache.
>>> Sometimes when we start our application we get the following error while
>>> we try to push any value in this cache.
>>>
>>> It is very random behaviour. It works fine if we try to run the
>>> application again.
>>> Can someone please suggest if we are missing out something.
>>>
>>> org.apache.ignite.binary.BinaryObjectException: Failed to get field
>>> because type ID of passed object differs from type ID this BinaryField
>>> belongs to [expected=-418749773, actual=0]
>>> at org.apache.ignite.internal.bin
>>> ary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
>>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.bin
>>> ary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
>>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2039)
>>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:1999)
>>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2457)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(Grid
>>> H2AbstractKeyValueRow.java:289) ~[ignite-indexing-1.5.0.final.
>>> jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:120)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:115)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:107)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at java.util.concurrent.Concurren
>>> tSkipListMap.cpr(ConcurrentSkipListMap.java:655) ~[?:1.8.0_77]
>>> at java.util.concurrent.Concurren
>>> tSkipListMap.doPut(ConcurrentSkipListMap.java:835) ~[?:1.8.0_77]
>>> at java.util.concurrent.Concurren
>>> tSkipListMap.put(ConcurrentSkipListMap.java:1581) ~[?:1.8.0_77]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2TreeIndex.put(GridH2TreeIndex.java:403)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:406)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.opt.GridH2Table.update(GridH2Table.java:340)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:523)
>>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.query.GridQueryProcessor.store(GridQueryProcessor.java:695)
>>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:406)
>>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>>> at org.apache.ignite.internal.pro
>>> cessors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:3740)
>>>

Re: Load data to cache

Hi,

I set cache name as 'Person' in Ignite ODBC driver.

 
How Can I load data in it?
I tried following code to load data. But no tables exist, while connecting
database through odbc connection. Please explain me how to create database ?
class Program 
{ 
static void Main(string[] args) 
{ 
IIgnite ignite = Ignition.Start(@"F:Visual Studio
2015\Projects\CreateCluster\CreateCluster\my-file.xml"); 
var cache = ignite.GetOrCreateCache("Person");
cache.Put(1, "John");
cache.Put(2, "Smith");
cache.Get(1);
cache.Get(2);
}
}

my-file.xml:
 

http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>

  


 
 



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

Re: Logging ignite-log4j.jar

Hi Sam,

1. Looks like a bug. I think Ignite should not raise log level when adding
console appender.
Setting System property "IGNITE_CONSOLE_APPENDER" to true will set
rootLogger level to OFF that can be unexpectedly as well.
Seems, we should check if there is no other loggers configured which can
inherits rootLogger logging level before turning rootLogger off.

Right?

2. You can configure ConsoleAppender for RootLogger explicitly. Or override
logging Level for other loggers.



On Thu, Mar 23, 2017 at 11:41 PM, javastuff@gmail.com <
javastuff@gmail.com> wrote:

> Hi
>
> My application already uses Log4j for logging, simply adding
> ignite-log4j.jar enables Ignite logging. I also added a new logger
> configuration for package "org.apche.ignite" in my application logging
> configuration, so that Ignite can log into a separate rolling file.
> Ignite logging working fine. However rootLogger log level is changed to
> INFO
> by Ignite initialization, which is problematic for my application logging.
>
> Ignite configuration file does not have configuration for GridLogger, so at
> initialization it tries to add a new consoleAppender with INFO level by
> instantiating Log4JLogger(), here it also updates rootLogger to INFO.
>
> Question -
> 1. Why does Ignite need to update rootLogger log level?
> 2. Is this not the good way to configure logging for ignite using
> ignite-log4j.jar?
>
> Thanks
> -Sam
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Logging-ignite-log4j-jar-tp11400.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov

Re: ignite messaging disconnection behaviour

2017-03-24 Thread dkarachentsev

Hi Kevin,

It seems that async mode has no effect for message sending, I've wrote a
suggestion to fix this in dev list. But for now you could delegate message
sending to separate thread just to release your main thread.
I'll send follow up message to you with ticket number, if or when it will be
opened.

Thanks!

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11418.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Hi Andrey,Thanks for your reply. My interceptor will save some data into local files then move the file to another mounted directory(NFS or S3). There are other programs do the merge operations. I use node Id to make the file unique. so I think it is fine. Just as your mentioned, there are IO operations, I already make it async-write.now all seems good.

ThanksShawn

On 03/24/2017 16:31，Andrey Mashenkov wrote：

Hi Shawn,What stream do you mean? Ignite CacheInterceptorcan be serialized and executed on different node, possibly you send it with a stream created on client side. If it so, it is a bad idea.CacehInterceptor supports resource injecting. See org.apache.ignite.resources package. So, you can make async call of some code from it, which will do all IO work.Also it has a note in javadoc: * Implementations should not execute any complex logic,* including locking, networking or cache operations,* as it may lead to deadlock, since this method is called* from sensitive synchronization blocks.On Fri, Mar 24, 2017 at 4:16 AM, shawn.du wrote:

Hi Andrey,
Thanks for your reply. one more question:Does the interceptor need to be thread-safe? My interceptor throws unexpected Io Exceptions like trying to write closed stream.

ThanksShawn

On 03/23/2017 15:18，Andrey Mashenkov wrote：

Hi Shawn,CacheInterceptor should be called once on one node.On Wed, Mar 22, 2017 at 5:11 AM, shawn.du wrote:

Hi,If I have multiple-nodes cluster, and I set up a cache interceptor on a cache. the cache mode is partitioned or duplicated. in partition mode, the cache maybe have a backup or not. My question is: when a cache entry is removed, the interceptor will be called once on one node or multiple times on multiple node?

ThanksShawn

-- Best regards,Andrey V. Mashenkov

Re: Issue with automatic persistence

Hi Alper,

Possibly, it is a bug [1] fixed in ignite-1.6.

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

On Fri, Mar 24, 2017 at 10:21 AM, Alper Tekinalp  wrote:

> Hi.
>
> We see the following log on our servers:
>
>
> *Failed to register marshalled class for more than 10 times in a row *
> I could not relate it to an error so I dont have any idea about the
> problem. What cause that problem? Can you give a hint?
>
> On Fri, Jun 17, 2016 at 1:22 AM, Denis Magda  wrote:
>
>> Hi,
>>
>> Do you see the working below on any of the nodes?
>> *Failed to register marshalled class for more than 10 times in a row *
>>
>> Actually it’s difficult to say what is the exact reason of the issue. Can
>> you upgrade to the latest Ignite version to see if the issue is still
>> reproducible?
>>
>> —
>> Denis
>>
>> On Jun 16, 2016, at 2:15 PM, Saurabh Sharma 
>> wrote:
>>
>> Hi,
>>
>> We are using ignite cache with automatic persistence feature for storing
>> the objects in cache. We have objects used as key and value for this cache.
>> Sometimes when we start our application we get the following error while
>> we try to push any value in this cache.
>>
>> It is very random behaviour. It works fine if we try to run the
>> application again.
>> Can someone please suggest if we are missing out something.
>>
>> org.apache.ignite.binary.BinaryObjectException: Failed to get field
>> because type ID of passed object differs from type ID this BinaryField
>> belongs to [expected=-418749773, actual=0]
>> at org.apache.ignite.internal.bin
>> ary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.bin
>> ary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2039)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:1999)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2457)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(Grid
>> H2AbstractKeyValueRow.java:289) ~[ignite-indexing-1.5.0.final.
>> jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:120)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:115)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2TreeIndex$2.compare(GridH2TreeIndex.java:107)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at java.util.concurrent.Concurren
>> tSkipListMap.cpr(ConcurrentSkipListMap.java:655) ~[?:1.8.0_77]
>> at java.util.concurrent.Concurren
>> tSkipListMap.doPut(ConcurrentSkipListMap.java:835) ~[?:1.8.0_77]
>> at java.util.concurrent.Concurren
>> tSkipListMap.put(ConcurrentSkipListMap.java:1581) ~[?:1.8.0_77]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2TreeIndex.put(GridH2TreeIndex.java:403)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:406)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.opt.GridH2Table.update(GridH2Table.java:340)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:523)
>> ~[ignite-indexing-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.query.GridQueryProcessor.store(GridQueryProcessor.java:695)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:406)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:3740)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>> cessors.cache.GridCacheMapEntry.innerUpdateLocal(GridCacheMapEntry.java:1661)
>> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>> at org.apache.ignite.internal.pro
>>

Re: Load data to cache

2017-03-24 Thread Pavel Tupitsyn

You have to include Person class in binary configuration:

IIgnite ignite = Ignition.Start(new IgniteConfiguration
{
SpringConfigUrl = @"F:\Visual Studio
2015\Projects\CreateCluster\CreateCluster\my-file.xml",
BinaryConfiguration = new
BinaryConfiguration(typeof(Person))
});

Also you have different cache names in config (personCache) and code
(Mycache).
Use GetCache instead of GetOrCreateCache to make sure that cache is started
from XML config.



On Fri, Mar 24, 2017 at 11:32 AM, kavitha  wrote:

> Hi,
>
> I am using following code to load data in Ignite cluster. But I got below
> error.
>
> my-file.xml code:
> 
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>  class="org.apache.ignite.configuration.IgniteConfiguration">
>   
> 
>   
>  
> 
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
> 
> 
>  value="java.lang.Long">
>  value="ignite.myexamples.model.Person">
> 
> 
>  value="java.lang.Long">
>  value="java.lang.String">
>  value="java.lang.Long">
>  value="java.lang.Integer">
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>
> 
> 
>
> class Person :IBinarizable
> {
> public long id { get; set; }
> public long orgId { get; set; }
> public string name { get; set; }
> public int salary { get; set; }
>
> public Person(long a, long b, string c, int d)
> {
> id = a;
> orgId = b;
> name = c;
> salary = d;
> }
> public void WriteBinary(IBinaryWriter writer)
> {
> var rawWriter = writer.GetRawWriter();
>
> rawWriter.WriteString(name);
> rawWriter.WriteInt(salary);
> }
>
> public void ReadBinary(IBinaryReader reader)
> {
> var rawReader = reader.GetRawReader();
>
> name = rawReader.ReadString();
> salary = rawReader.ReadInt();
> }
>
> }
>
>  class Program
> {
> static void Main(string[] args)
> {
> Person obj = new Person(1,1000, "John",2);
> Person obj1 = new Person(2,2000, "Smith", 38000);
>
> IIgnite ignite = Ignition.Start(@"F:Visual Studio
> 2015\Projects\CreateCluster\CreateCluster\my-file.xml");
> var cache = ignite.GetOrCreateCache("Mycache");
> cache.Put(1,obj);
> cache.Put(2,obj1);
>  }
>}
> }
>
>
> Error: An unhandled exception of type
> 'Apache.Ignite.Core.Binary.BinaryObjectException' occurred in
> Apache.Ignite.Core.dll
>
> Additional information: Unsupported object type [type=CreateCluster.Person,
> object=CreateCluster.Person].
>
> Specified type can not be serialized by Ignite: it is neither
> [Serializable], nor registered in IgniteConfiguration.BinaryConfiguration.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Load-data-to-cache-tp11394p11414.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Load data to cache

Hi,

I am using following code to load data in Ignite cluster. But I got below
error. 

my-file.xml code:


http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>

  


 






















 

 



class Person :IBinarizable
{
public long id { get; set; }
public long orgId { get; set; }
public string name { get; set; }
public int salary { get; set; }

public Person(long a, long b, string c, int d)
{
id = a;
orgId = b;
name = c;
salary = d;
}
public void WriteBinary(IBinaryWriter writer)
{
var rawWriter = writer.GetRawWriter();

rawWriter.WriteString(name);
rawWriter.WriteInt(salary);
}

public void ReadBinary(IBinaryReader reader)
{
var rawReader = reader.GetRawReader();

name = rawReader.ReadString();
salary = rawReader.ReadInt();
}

}

 class Program
{
static void Main(string[] args)
{
Person obj = new Person(1,1000, "John",2);
Person obj1 = new Person(2,2000, "Smith", 38000);

IIgnite ignite = Ignition.Start(@"F:Visual Studio
2015\Projects\CreateCluster\CreateCluster\my-file.xml");
var cache = ignite.GetOrCreateCache("Mycache");
cache.Put(1,obj);
cache.Put(2,obj1);
 }
   }
}


Error: An unhandled exception of type
'Apache.Ignite.Core.Binary.BinaryObjectException' occurred in
Apache.Ignite.Core.dll

Additional information: Unsupported object type [type=CreateCluster.Person,
object=CreateCluster.Person].

Specified type can not be serialized by Ignite: it is neither
[Serializable], nor registered in IgniteConfiguration.BinaryConfiguration.



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

Re: Can I let Ignite to do rebalance at a particular time?

2017-03-24 Thread Dmitry Karachentsev


Hi,

Totally agree wit that. And it should be possible to start re-balancing 
from client node too.


> But I think it is more convenient to start rebalancing manually from 
management console, is it right?


I don't see the difference on how to start re-balancing: from Ignite API 
or console, result will be the same.


-Dmitry.

24.03.2017 02:55, Valentin Kulichenko пишет:

Cross-posting to dev.

Guys,

Is there any reason for such implementation? Does it ever makes sense 
to trigger rebalancing on only one node?


I think rebalance() method should broadcast automatically and do the 
job on all nodes. Just in case, we can also add localRebalance() 
method. This will be more intuitive and also more consistent with 
other APIs, like loadCache/localLoadCache.


-Val

On Wed, Mar 22, 2017 at 11:52 PM, ght230 > wrote:


Thank you for your guidance.

I will try calling IgniteCache.rebalance()  via compute broadcast
task.

But I think it is more convenient to start rebalancing manually from
management console, is it right?



--
View this message in context:

http://apache-ignite-users.70518.x6.nabble.com/Can-I-let-Ignite-to-do-rebalance-at-a-particular-time-tp11301p11381.html


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

Re: CacheInterceptor issue