Re: Range queries on indexed columns

[Anil]

Thanks Andrey.

On 14 June 2017 at 20:15, Andrey Mashenkov 
wrote:

> Hi Anil,
>
> Yes, in your case map queries results already sorted and there is only
> merge on reduce side.
> Sorting can be disabled on map side when e.g. aggregates is used.
>
> On Wed, Jun 14, 2017 at 3:20 PM, Anil  wrote:
>
>> Hi Team,
>>
>> Can some help in understanding the below ? Thanks.
>>
>> On 13 June 2017 at 11:07, Anil  wrote:
>>
>>> HI Team,
>>>
>>> I have a table TEST with a indexed column COL_A. Does the following
>>> query works ?
>>>
>>> select * from Test where COL_A > '1' and COL_A < '2' offset 10  ROWS
>>> FETCH NEXT 20 ROWS ONLY
>>>
>>> As per my understanding of distributed systems, the query is sent to all
>>> nodes and gets the 10 records from each node and return 10 (whatever
>>> returns first)
>>>
>>> as indexes are distributed, the above query may not return the records
>>> in paginated way without adding sort like below.
>>>
>>> select * from Test where COL_A > '1' and COL_A < '2' order by COL_A
>>> offset 10  ROWS FETCH NEXT 20 ROWS ONLY
>>>
>>> do you see any overhead of sort here ?
>>>
>>> Does it work in following way ?
>>>
>>> send the query to all nodes and get 10 (based on sorting) records and
>>> sort all results of each node at reducer and return final 10 .
>>>
>>> Sort should not have any overhead here as sort and filter is done on
>>> indexed column.
>>>
>>> Please correct me if i am wrong. thanks.
>>>
>>> Thanks
>>>
>>>
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: Ignite web console not running in browser

[Andrey Novikov]

Hi,

In Ignite 1.9, Ignite 2.0 developer web server bind only on localhost
interface. This was fixed in master where developer web server bind for all
interfaces.

As temporary workaround you can try to replace localhost with your ip in
https://github.com/apache/ignite/blob/1.9.0/modules/web-console/frontend/gulpfile.babel.js/tasks/bundle.js
for Ignite 1.9 or set environment variable HOST for Ignite 2.0
https://github.com/apache/ignite/blob/ignite-2.0/modules/web-console/frontend/gulpfile.babel.js/webpack/environments/development.js



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-web-console-not-running-in-browser-tp13701p13852.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Out-Of-Memory

[javastuff....@gmail.com]

Hi,

We are using Ignite 1.9, OFFHEAP with SWAP disabled. We are creating caches
programmatic and want to use SQL. 
At one instance creating 350 empty cache ran into out-of-memory.  We are
already setting low queue size for delete history
(IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE=100)

Log metrics showing 25% free heap memory and 87% free off-heap. Can you
please help me understand this issue and possible resolution? OOM with heap
or offheap or H2 ?

Below is Ignite log with stack trace as well as periodic metrics.

=
2017-06-15 11:41:41,404,[exchange-worker-#68%TESTNODE%],Skipping rebalancing
(nothing scheduled) [top=AffinityTopologyVersion [topVer=1,
minorTopVer=348], evt=DISCOVERY_CUSTOM_EVT,
node=0c23715a-8c78-4852-9b1a-a5f101d65b7b]
2017-06-15 11:41:43,345,[exchange-worker-#68%TESTNODE%],Failed to
reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
minorTopVer=349], nodeId=0c23715a, evt=DISCOVERY_CUSTOM_EVT]
class
org.apache.ignite.internal.util.offheap.GridOffHeapOutOfMemoryException:
Failed to allocate memory [total=0, failed=16384]
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafeMemory.allocate0(GridUnsafeMemory.java:182)
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafeMemory.allocateSystem(GridUnsafeMemory.java:145)
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafeMap$Segment.(GridUnsafeMap.java:624)
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafeMap$Segment.(GridUnsafeMap.java:590)
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafeMap.init(GridUnsafeMap.java:273)
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafeMap.(GridUnsafeMap.java:248)
at
org.apache.ignite.internal.util.offheap.unsafe.GridUnsafePartitionedMap.(GridUnsafePartitionedMap.java:111)
at
org.apache.ignite.internal.util.offheap.GridOffHeapMapFactory.unsafePartitionedMap(GridOffHeapMapFactory.java:224)
at
org.apache.ignite.internal.processors.offheap.GridOffHeapProcessor.create(GridOffHeapProcessor.java:72)
at
org.apache.ignite.internal.processors.cache.GridCacheSwapManager.initOffHeap(GridCacheSwapManager.java:251)
at
org.apache.ignite.internal.processors.cache.GridCacheSwapManager.start0(GridCacheSwapManager.java:138)
at
org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.start(GridCacheManagerAdapter.java:50)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1091)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1745)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1636)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:382)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:581)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:464)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1674)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
2017-06-15 11:41:48,111,[grid-timeout-worker-#54%TESTNODE%],
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=0c23715a, name=TESTNODE, uptime=00:10:06:422]
^-- H/N/C [hosts=1, nodes=1, CPUs=2]
^-- CPU [cur=0.27%, avg=20.87%, GC=0%]
^-- Heap [used=1461MB, free=26.63%, comm=1991MB]
^-- Non heap [used=195MB, free=87.16%, comm=208MB]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=6, qSize=0]
^-- Outbound messages queue [size=0]
2017-06-15 11:41:48,333,[exchange-worker-#68%TESTNODE%],Failed to wait for
completion of partition map exchange (preloading will not start):
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null,
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=349],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=0c23715a-8c78-4852-9b1a-a5f101d65b7b, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:49500], discPort=49500, order=1, intOrder=1,
lastExchangeTime=1497506480276, loc=true, ver=1.9.0#20170302-sha1:a8169d0a,
isClient=false], topVer=1, nodeId8=0c23715a, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1497507101444]], crd=TcpDiscoveryNode
[id=0c23715a-8c78-4852-9b1a-a5f101d65b7b, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:49500], discPort=49500, order=1, intOrder=1,

Threads leaks problem...

[Alexander Ivanov]

Hi,  All!

I found that during the execution Ignite 2.0 accumulate threads with the
name 'pool--thread-' and as result occurs OutOfMemoryException -
unable to create native thread.

Research led me to a method IgniteUtiuls.filterReachable():

/ public static List filterReachable(Collection
addrs) {
final int reachTimeout = 2000;

if (addrs.isEmpty())
return Collections.emptyList();

if (addrs.size() == 1) {
InetAddress addr = F.first(addrs);

if (reachable(addr, reachTimeout))
return Collections.singletonList(addr);

return Collections.emptyList();
}

final List res = new ArrayList<>(addrs.size());

Collection> futs = new ArrayList<>(addrs.size());

 *   ExecutorService executor =
Executors.newFixedThreadPool(Math.min(10, addrs.size()));
*
for (final InetAddress addr : addrs) {
futs.add(executor.submit(new Runnable() {
@Override public void run() {
if (reachable(addr, reachTimeout)) {
synchronized (res) {
res.add(addr);
}
}
}
}));
}

for (Future fut : futs) {
try {
fut.get();
}
catch (InterruptedException e) {
Thread.currentThread().interrupt();

*throw new IgniteException("Thread has been interrupted.",
e);*
}
catch (ExecutionException e) {
*throw new IgniteException(e);*
}
}

*executor.shutdown();*

return res;
}
/

I think that should be mandatory call *executor.shutdown()*, for example in
the finalize block.

Alexander



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Threads-leaks-problem-tp13828.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Exception when Ignite server starts up and also when a new node joins the cluster

[Andrey Gura]

Hi,

no problems with provided configuration. There are no any errors.
Could you try run your example on different environment setups?

On Thu, Jun 15, 2017 at 7:52 AM, jaipal  wrote:
> Hi Agura.
>
> You can try with this  configuration
> 
> but it is with out write behind
> I have been using jdk7 (build 1.7.0_45-b18) on Red Hat Linux 7.3.
>
> Regards
> Jaipal
>
>
>
>
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Exception-when-Ignite-server-starts-up-and-also-when-a-new-node-joins-the-cluster-tp13684p13797.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Can java code look up cache in server without Ignition.start(cfg)

[StartCoding]

Thanks Val. It worked when I removed try()

On Wed, Jun 14, 2017 at 5:54 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n13713...@n6.nabble.com> wrote:

> Saji,
>
> You're using try-with-resources syntax, which calls Ignite.close() at the
> end and therefore stops the node. Getting rid of it will do the trick.
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Can-java-
> code-look-up-cache-in-server-without-Ignition-start-cfg-tp9008p13713.html
> To unsubscribe from Can java code look up cache in server without
> Ignition.start(cfg), click here
> 
> .
> NAML
> 
>



-- 
Thanks and Regards
Sajin




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Can-java-code-look-up-cache-in-server-without-Ignition-start-cfg-tp9008p13825.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cache Metrics

[Megha Mittal]

Hi,

Thanks for raising the jira. Looking forward to its resolution. 



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

Re: ODBC driver issue

[Igor Sapego]

Weird issue.

When it comes to ODBC, MSDN has answers to many questions.
Also, you may take a look at the following links:

http://www.easysoft.com/developer/languages/c/odbc_tutorial.html
http://www.easysoft.com/developer/languages/c/odbc-tutorial-fetching-results.html
http://www.easysoft.com/developer/languages/c/examples/index.html

Best Regards,
Igor

On Thu, Jun 15, 2017 at 4:28 PM, Riccardo Iacomini <
riccardo.iacom...@rdslab.com> wrote:

> The env command confirmed that the variable was correctly set. I tried to
> go over the installation process again, and now I managed to get it
> working. I do not actually know the exact reason, but let's say I am happy
> with it.
>
> I've now configured a Cassandra backed cache, and wanted to query it using
> the odbc driver. Any useful resource about the subject is really
> appreciated.
>
> Thank you for your help so far.
>
> Best regards
>
> Riccardo Iacomini
>
>
> *RDSLab*
>
> On Thu, Jun 15, 2017 at 11:45 AM, Igor Sapego 
> wrote:
>
>> Have you restarted your terminal after that? What does env command show?
>> Is it set?
>>
>> Best Regards,
>> Igor
>>
>> On Wed, Jun 14, 2017 at 6:18 PM, Riccardo Iacomini <
>> riccardo.iacom...@rdslab.com> wrote:
>>
>>> Yes, I've set the env variable, globally in /etc/environment. Just for
>>> completeness, I am running Ubuntu 16.04.
>>>
>>> Best
>>>
>>> Riccardo Iacomini
>>>
>>>
>>> *RDSLab*
>>>
>>> On Wed, Jun 14, 2017 at 1:02 PM, Igor Sapego 
>>> wrote:
>>>
 Do you set LD_LIBRARY_PATH to /usr/local/lib? If 'yes' then
 can you describe in details how you do that? This may help
 to identify an issue.

 Best Regards,
 Igor

 On Wed, Jun 14, 2017 at 12:30 PM, Riccardo Iacomini <
 riccardo.iacom...@rdslab.com> wrote:

> Hello Igor,
> I double checked the documentation and went over the steps again to be
> sure everything is ok. I tried running your command, that's the output:
>
>  linux-vdso.so.1 =>  (0x7fff75dd6000)
>> libignite-binary-2.0.0.19668.so.0 => 
>> /usr/local/lib/libignite-binary-2.0.0.19668.so.0
>> (0x7f40e5349000)
>> libodbcinst.so.2 => /usr/local/lib/libodbcinst.so.2
>> (0x7f40e5134000)
>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>> (0x7f40e4d8a000)
>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f40e49c1000)
>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>> (0x7f40e47ab000)
>> libignite-common-2.0.0.19668.so.0 => 
>> /usr/local/lib/libignite-common-2.0.0.19668.so.0
>> (0x7f40e4594000)
>> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
>> (0x7f40e438a000)
>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>> (0x7f40e416d000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f40e3e63000)
>> /lib64/ld-linux-x86-64.so.2 (0x555643691000)
>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f40e3c5f000)
>
>
>
> however, I still get the same error from python:
>
> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>> lib 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*
>
>
>
> Best
>
> Riccardo Iacomini
>
>
> *RDSLab*
>
> On Wed, Jun 14, 2017 at 11:10 AM, Igor Sapego 
> wrote:
>
>> So, setting LD_LIBRARY_PATH to /usr/local/lib should definetly help.
>> Are you sure your did everything right? Try the following command (in
>> one line):
>> LD_LIBRARY_PATH=/usr/local/lib ldd /usr/local/lib/libignite-odbc.so
>>
>> Best Regards,
>> Igor
>>
>> On Wed, Jun 14, 2017 at 10:15 AM, Riccardo Iacomini <
>> riccardo.iacom...@rdslab.com> wrote:
>>
>>> As asked:
>>>

 linux-vdso.so.1 =>  (0x7ffca6776000)
 libignite-binary-2.0.0.19668.so.0 => not found
 libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2
 (0x7fb92ead4000)
 libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 (0x7fb92e751000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb92e388000)
 libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
 (0x7fb92e172000)
 libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
 (0x7fb92df67000)
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
 (0x7fb92dd4a000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb92da41000)
 /lib64/ld-linux-x86-64.so.2 (0x560f6c5b)
 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb92d83c000)
>>>
>>>
>>>
>>> seems like libignite-binary is not found, but if you look at the
>>> directory listing I previously posted, it should be there.
>>>
>>>
>>>
>>> Riccardo Iacomini
>>>
>>>

Re: Understanding peerclassloading

[Helge Waastad]

Hi,
running 2.0
https://github.com/hwaastad/Ignite.git
Its a ear project (did test to evaluate classloading)
Ignite is initialized in Ignite-web servletcontextlistener
(org.waastad.servlet.StartupListener)
cache is produced: 
Cache spec is produced in Ignite-web/ (org.waastad.cache.CacheProducer)
Cache is being used in a Rest Resource:  Ignite-
web/(org.waastad.service.RestResource) 
POST to http://localhost:8080/Ignite-web/api/counter body: whatever..


I've made an IT test (which does not fail)
But running mvn tomee:run in web or ear will fail.


/hw


to., 15.06.2017 kl. 05.21 -0700, skrev afedotov:
> Hi, please share the full log containing the error.
> Which version of Ignite do you use?
> It's not reproducible on my side.
> 
> Kind regards,
> Alex.
> 
> On Thu, Jun 15, 2017 at 2:46 PM, Helge Waastad [via Apache Ignite
> Users] <[hidden email]> wrote:
> > Hi, and thx for answering. 
> > peerclassloading is enabled on both server and client. 
> > 
> > My trouble is the understanding of the reason why 
> > cache.put(key,arraylist) will not work (not trigger class loading)
> > but 
> > cache.put(key,Arrays.aslist(arraylist.toArray())) will. 
> > 
> > /hw 
> > 
> > to., 15.06.2017 kl. 03.22 -0700, skrev afedotov:
> > 
> > > Hi, 
> > > 
> > > If I get your problem right you need either enable peer class
> > loading 
> > > on both the client and the server or make sure 
> > > that all required class definitions are available on the
> > classpath of 
> > > the client. 
> > > https://apacheignite.readme.io/v2.0/docs/deployment-
> > modes#section-con
> > > figuration 
> > > 
> > > 
> > > 
> > > Kind regards, 
> > > Alex. 
> > > 
> > > On Thu, Jun 15, 2017 at 10:42 AM, Helge Waastad [via Apache
> > Ignite
> > > Users] <[hidden email]> wrote:
> > 
> > > > Hi, 
> > > > I'm pretty new to the Apache Ignite. 
> > > > I'm working with peerclassloading and need to understand a
> > couple 
> > > > of thing. 
> > > > 
> > > > Scenario: 
> > > > 1x server and 1x client 
> > > > 
> > > > Cache: 
> > > > CacheConfiguration cc = new
> > CacheConfiguration<>("my- 
> > > > cache"); 
> > > > 
> > > > Code creating classnotfound: 
> > > > FluidGridItem item = new FluidGridItem(UUID.randomUUID()); 
> > > > List ll = new ArrayList<>(); 
> > > > ll.add(item); 
> > > > cache.put(key, ll); 
> > > > 
> > > > Code loading class ok: (INFO: Class locally deployed: class 
> > > > org.primefaces.extensions.model.fluidgrid.FluidGridItem) 
> > > > FluidGridItem item = new FluidGridItem(UUID.randomUUID()); 
> > > > List ll = new ArrayList<>(); 
> > > > ll.add(item); 
> > > > cache.put(key, Arrays.asList(ll.toArray())); 
> > > > 
> > > > 
> > > > Can someone please explain why this is? 
> > > > (It's been a headache resolving this - been trying to get a
> > JCS 
> > > > project migrated to Ignite) 
> > > > 
> > > > br hw 
> > > > 
> > > > 
> > > >
> > > > If you reply to this email, your message will be added to the 
> > > > discussion below: 
> > > > http://apache-ignite-users.70518.x6.nabble.com/Understanding-
> > peercl
> > > > assloading-tp13805.html 
> > > > To start a new topic under Apache Ignite Users, email [hidden 
> > > > email]  
> > > > To unsubscribe from Apache Ignite Users, click here. 
> > > > NAML 
> > > > 
> > > 
> > > View this message in context: Re: Understanding peerclassloading 
> > > Sent from the Apache Ignite Users mailing list archive at
> > Nabble.com. 
> > 
> > 
> > If you reply to this email, your message will be added to the
> > discussion below:
> > http://apache-ignite-users.70518.x6.nabble.com/Understanding-
> > peerclassloading-tp13805p13818.html
> > To start a new topic under Apache Ignite Users, email [hidden
> > email] 
> > To unsubscribe from Apache Ignite Users, click here.
> > NAML
> > 
> 
> View this message in context: Re: Understanding peerclassloading
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ODBC driver issue

[Riccardo Iacomini]

The env command confirmed that the variable was correctly set. I tried to
go over the installation process again, and now I managed to get it
working. I do not actually know the exact reason, but let's say I am happy
with it.

I've now configured a Cassandra backed cache, and wanted to query it using
the odbc driver. Any useful resource about the subject is really
appreciated.

Thank you for your help so far.

Best regards

Riccardo Iacomini


*RDSLab*

On Thu, Jun 15, 2017 at 11:45 AM, Igor Sapego  wrote:

> Have you restarted your terminal after that? What does env command show?
> Is it set?
>
> Best Regards,
> Igor
>
> On Wed, Jun 14, 2017 at 6:18 PM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> Yes, I've set the env variable, globally in /etc/environment. Just for
>> completeness, I am running Ubuntu 16.04.
>>
>> Best
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Wed, Jun 14, 2017 at 1:02 PM, Igor Sapego 
>> wrote:
>>
>>> Do you set LD_LIBRARY_PATH to /usr/local/lib? If 'yes' then
>>> can you describe in details how you do that? This may help
>>> to identify an issue.
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Wed, Jun 14, 2017 at 12:30 PM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
 Hello Igor,
 I double checked the documentation and went over the steps again to be
 sure everything is ok. I tried running your command, that's the output:

  linux-vdso.so.1 =>  (0x7fff75dd6000)
> libignite-binary-2.0.0.19668.so.0 => 
> /usr/local/lib/libignite-binary-2.0.0.19668.so.0
> (0x7f40e5349000)
> libodbcinst.so.2 => /usr/local/lib/libodbcinst.so.2
> (0x7f40e5134000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x7f40e4d8a000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f40e49c1000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x7f40e47ab000)
> libignite-common-2.0.0.19668.so.0 => 
> /usr/local/lib/libignite-common-2.0.0.19668.so.0
> (0x7f40e4594000)
> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
> (0x7f40e438a000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f40e416d000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f40e3e63000)
> /lib64/ld-linux-x86-64.so.2 (0x555643691000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f40e3c5f000)



 however, I still get the same error from python:

 *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
> lib 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*



 Best

 Riccardo Iacomini


 *RDSLab*

 On Wed, Jun 14, 2017 at 11:10 AM, Igor Sapego 
 wrote:

> So, setting LD_LIBRARY_PATH to /usr/local/lib should definetly help.
> Are you sure your did everything right? Try the following command (in
> one line):
> LD_LIBRARY_PATH=/usr/local/lib ldd /usr/local/lib/libignite-odbc.so
>
> Best Regards,
> Igor
>
> On Wed, Jun 14, 2017 at 10:15 AM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> As asked:
>>
>>>
>>> linux-vdso.so.1 =>  (0x7ffca6776000)
>>> libignite-binary-2.0.0.19668.so.0 => not found
>>> libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2
>>> (0x7fb92ead4000)
>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>> (0x7fb92e751000)
>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb92e388000)
>>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>>> (0x7fb92e172000)
>>> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
>>> (0x7fb92df67000)
>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>> (0x7fb92dd4a000)
>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb92da41000)
>>> /lib64/ld-linux-x86-64.so.2 (0x560f6c5b)
>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb92d83c000)
>>
>>
>>
>> seems like libignite-binary is not found, but if you look at the
>> directory listing I previously posted, it should be there.
>>
>>
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Tue, Jun 13, 2017 at 6:20 PM, Igor Sapego 
>> wrote:
>>
>>> Well, try running the following command:
>>> ldd /usr/local/lib/libignite-odbc.so
>>>
>>> This may help us see which library can't be found.
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Tue, Jun 13, 2017 at 6:10 PM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
 Thank you for the reply Igor,

 the error just changed into:

 *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver 

Re: Understanding peerclassloading

[afedotov]

Hi, please share the full log containing the error.
Which version of Ignite do you use?
It's not reproducible on my side.

Kind regards,
Alex.

On Thu, Jun 15, 2017 at 2:46 PM, Helge Waastad [via Apache Ignite Users] <
ml+s70518n13818...@n6.nabble.com> wrote:

> Hi, and thx for answering.
> peerclassloading is enabled on both server and client.
>
> My trouble is the understanding of the reason why
> cache.put(key,arraylist) will not work (not trigger class loading) but
> cache.put(key,Arrays.aslist(arraylist.toArray())) will.
>
> /hw
>
> to., 15.06.2017 kl. 03.22 -0700, skrev afedotov:
>
> > Hi,
> >
> > If I get your problem right you need either enable peer class loading
> > on both the client and the server or make sure
> > that all required class definitions are available on the classpath of
> > the client.
> > https://apacheignite.readme.io/v2.0/docs/deployment-modes#section-con
> > figuration
> >
> >
> >
> > Kind regards,
> > Alex.
> >
> > On Thu, Jun 15, 2017 at 10:42 AM, Helge Waastad [via Apache Ignite
> > Users] <[hidden email]> wrote:
> > > Hi,
> > > I'm pretty new to the Apache Ignite.
> > > I'm working with peerclassloading and need to understand a couple
> > > of thing.
> > >
> > > Scenario:
> > > 1x server and 1x client
> > >
> > > Cache:
> > > CacheConfiguration cc = new CacheConfiguration<>("my-
> > > cache");
> > >
> > > Code creating classnotfound:
> > > FluidGridItem item = new FluidGridItem(UUID.randomUUID());
> > > List ll = new ArrayList<>();
> > > ll.add(item);
> > > cache.put(key, ll);
> > >
> > > Code loading class ok: (INFO: Class locally deployed: class
> > > org.primefaces.extensions.model.fluidgrid.FluidGridItem)
> > > FluidGridItem item = new FluidGridItem(UUID.randomUUID());
> > > List ll = new ArrayList<>();
> > > ll.add(item);
> > > cache.put(key, Arrays.asList(ll.toArray()));
> > >
> > >
> > > Can someone please explain why this is?
> > > (It's been a headache resolving this - been trying to get a JCS
> > > project migrated to Ignite)
> > >
> > > br hw
> > >
> > >
> > >
> > > If you reply to this email, your message will be added to the
> > > discussion below:
> > > http://apache-ignite-users.70518.x6.nabble.com/Understanding-peercl
> > > assloading-tp13805.html
> > > To start a new topic under Apache Ignite Users, email [hidden
> > > email]
> > > To unsubscribe from Apache Ignite Users, click here.
> > > NAML
> > >
> >
> > View this message in context: Re: Understanding peerclassloading
> > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Understanding-
> peerclassloading-tp13805p13818.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




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

Re: Understanding peerclassloading

[Helge Waastad]

Hi, and thx for answering.
peerclassloading is enabled on both server and client.

My trouble is the understanding of the reason why
cache.put(key,arraylist) will not work (not trigger class loading) but
cache.put(key,Arrays.aslist(arraylist.toArray())) will.

/hw

to., 15.06.2017 kl. 03.22 -0700, skrev afedotov:
> Hi,
> 
> If I get your problem right you need either enable peer class loading
> on both the client and the server or make sure
> that all required class definitions are available on the classpath of
> the client.
> https://apacheignite.readme.io/v2.0/docs/deployment-modes#section-con
> figuration
> 
> 
> 
> Kind regards,
> Alex.
> 
> On Thu, Jun 15, 2017 at 10:42 AM, Helge Waastad [via Apache Ignite
> Users] <[hidden email]> wrote:
> > Hi,
> > I'm pretty new to the Apache Ignite.
> > I'm working with peerclassloading and need to understand a couple
> > of thing.
> > 
> > Scenario:
> > 1x server and 1x client
> > 
> > Cache:
> > CacheConfiguration cc = new CacheConfiguration<>("my-
> > cache");
> > 
> > Code creating classnotfound:
> > FluidGridItem item = new FluidGridItem(UUID.randomUUID());
> > List ll = new ArrayList<>();
> > ll.add(item);
> > cache.put(key, ll);
> > 
> > Code loading class ok: (INFO: Class locally deployed: class
> > org.primefaces.extensions.model.fluidgrid.FluidGridItem)
> > FluidGridItem item = new FluidGridItem(UUID.randomUUID());
> > List ll = new ArrayList<>();
> > ll.add(item);
> > cache.put(key, Arrays.asList(ll.toArray()));
> > 
> > 
> > Can someone please explain why this is?
> > (It's been a headache resolving this - been trying to get a JCS
> > project migrated to Ignite)
> > 
> > br hw
> > 
> > 
> > 
> > If you reply to this email, your message will be added to the
> > discussion below:
> > http://apache-ignite-users.70518.x6.nabble.com/Understanding-peercl
> > assloading-tp13805.html
> > To start a new topic under Apache Ignite Users, email [hidden
> > email] 
> > To unsubscribe from Apache Ignite Users, click here.
> > NAML
> > 
> 
> View this message in context: Re: Understanding peerclassloading
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite-jdbc port

[afedotov]

Sure. Just use regular Spring beans configuration approach.


...








Kind regards,
Alex.

On Thu, Jun 15, 2017 at 1:18 PM, ishan-jain [via Apache Ignite Users] <
ml+s70518n13815...@n6.nabble.com> wrote:

> But is there a way to firectly set it in xml file?
>
> On Thu, Jun 15, 2017 at 3:48 PM, Ishan Jain <[hidden email]
> > wrote:
>
>> Hostname:Port/Cache_name
>>
>> Thanx,Anyways i found the solution. ignite.configuration().getConn
>> ectorConfiguration().setPort(11212);
>>
>> On Thu, Jun 15, 2017 at 3:39 PM, afedotov <[hidden email]
>> > wrote:
>>
>>> Hi.
>>>
>>> Which kind of connection URL do you use: jdbc:ignite:cfg://[@]<
>>> config_url> or jdbc:ignite://:/ ?
>>>
>>> Kind regards,
>>> Alex.
>>>
>>> On Thu, Jun 15, 2017 at 11:26 AM, ishan-jain [via Apache Ignite Users] 
>>> <[hidden
>>> email] > wrote:
>>>
 how can i set my jdbc discovery port value in ignite config xml file.
 Need to change it from 11211 as i am using two ignite clusters

 --
 If you reply to this email, your message will be added to the
 discussion below:
 http://apache-ignite-users.70518.x6.nabble.com/Ignite-jdbc-p
 ort-tp13807.html
 To start a new topic under Apache Ignite Users, email [hidden email]
 
 To unsubscribe from Apache Ignite Users, click here.
 NAML
 

>>>
>>>
>>> --
>>> View this message in context: Re: Ignite-jdbc port
>>> 
>>>
>>> Sent from the Apache Ignite Users mailing list archive
>>>  at Nabble.com.
>>>
>>
>>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-
> jdbc-port-tp13807p13815.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




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

Re: Understanding peerclassloading

[afedotov]

Hi,

If I get your problem right you need either enable peer class loading on
both the client and the server or make sure
that all required class definitions are available on the classpath of the
client.
https://apacheignite.readme.io/v2.0/docs/deployment-modes#section-configuration



Kind regards,
Alex.

On Thu, Jun 15, 2017 at 10:42 AM, Helge Waastad [via Apache Ignite Users] <
ml+s70518n13805...@n6.nabble.com> wrote:

> Hi,
> I'm pretty new to the Apache Ignite.
> I'm working with peerclassloading and need to understand a couple of thing.
>
> Scenario:
> 1x server and 1x client
>
> Cache:
> CacheConfiguration cc = new CacheConfiguration<>("my-
> cache");
>
> Code creating classnotfound:
> FluidGridItem item = new FluidGridItem(UUID.randomUUID());
> List ll = new ArrayList<>();
> ll.add(item);
> cache.put(key, ll);
>
> Code loading class ok: (INFO: Class locally deployed: class
> org.primefaces.extensions.model.fluidgrid.FluidGridItem)
> FluidGridItem item = new FluidGridItem(UUID.randomUUID());
> List ll = new ArrayList<>();
> ll.add(item);
> cache.put(key, Arrays.asList(ll.toArray()));
>
>
> Can someone please explain why this is?
> (It's been a headache resolving this - been trying to get a JCS project
> migrated to Ignite)
>
> br hw
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Understanding-
> peerclassloading-tp13805.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




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

Re: Ignite-jdbc port

[Ishan Jain]

But is there a way to firectly set it in xml file?

On Thu, Jun 15, 2017 at 3:48 PM, Ishan Jain  wrote:

> Hostname:Port/Cache_name
>
> Thanx,Anyways i found the solution. ignite.configuration().
> getConnectorConfiguration().setPort(11212);
>
> On Thu, Jun 15, 2017 at 3:39 PM, afedotov 
> wrote:
>
>> Hi.
>>
>> Which kind of connection URL do you use: jdbc:ignite:cfg://[@]<
>> config_url> or jdbc:ignite://:/ ?
>>
>> Kind regards,
>> Alex.
>>
>> On Thu, Jun 15, 2017 at 11:26 AM, ishan-jain [via Apache Ignite Users] 
>> <[hidden
>> email] > wrote:
>>
>>> how can i set my jdbc discovery port value in ignite config xml file.
>>> Need to change it from 11211 as i am using two ignite clusters
>>>
>>> --
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>> http://apache-ignite-users.70518.x6.nabble.com/Ignite-jdbc-p
>>> ort-tp13807.html
>>> To start a new topic under Apache Ignite Users, email [hidden email]
>>> 
>>> To unsubscribe from Apache Ignite Users, click here.
>>> NAML
>>> 
>>>
>>
>>
>> --
>> View this message in context: Re: Ignite-jdbc port
>> 
>>
>> Sent from the Apache Ignite Users mailing list archive
>>  at Nabble.com.
>>
>
>

Re: Ignite-jdbc port

[Ishan Jain]

Hostname:Port/Cache_name

Thanx,Anyways i found the solution.
ignite.configuration().getConnectorConfiguration().setPort(11212);

On Thu, Jun 15, 2017 at 3:39 PM, afedotov 
wrote:

> Hi.
>
> Which kind of connection URL do you use: jdbc:ignite:cfg://[@]<
> config_url> or jdbc:ignite://:/ ?
>
> Kind regards,
> Alex.
>
> On Thu, Jun 15, 2017 at 11:26 AM, ishan-jain [via Apache Ignite Users] 
> <[hidden
> email] > wrote:
>
>> how can i set my jdbc discovery port value in ignite config xml file.
>> Need to change it from 11211 as i am using two ignite clusters
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-ignite-users.70518.x6.nabble.com/Ignite-jdbc-
>> port-tp13807.html
>> To start a new topic under Apache Ignite Users, email [hidden email]
>> 
>> To unsubscribe from Apache Ignite Users, click here.
>> NAML
>> 
>>
>
>
> --
> View this message in context: Re: Ignite-jdbc port
> 
>
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>

Re: Ignite-jdbc port

[afedotov]

Hi.

Which kind of connection URL do you use: jdbc:ignite:cfg://[@]<
config_url> or jdbc:ignite://:/ ?

Kind regards,
Alex.

On Thu, Jun 15, 2017 at 11:26 AM, ishan-jain [via Apache Ignite Users] <
ml+s70518n13807...@n6.nabble.com> wrote:

> how can i set my jdbc discovery port value in ignite config xml file. Need
> to change it from 11211 as i am using two ignite clusters
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-
> jdbc-port-tp13807.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




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

encounter issue on ignite 2.0

[minisoft_rm]

dear experts, I got the following error when start up my ignite 2.0 with
exported cluster project:

Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement
"CREATE INDEX PRIMARY[*] ON ""CartentriesCache_62_20_v1"".CARTENTRIES
(""PK"" ASC, ""_KEY"" ASC) "; expected "identifier"; SQL statement:
CREATE INDEX PRIMARY ON "CartentriesCache_62_20_v1".Cartentries ("PK" ASC,
"_KEY" ASC) [42001-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.getSyntaxError(DbException.java:205)
at org.h2.command.Parser.readIdentifierWithSchema(Parser.java:3197)
at org.h2.command.Parser.parseCreate(Parser.java:4374)
at org.h2.command.Parser.parsePrepared(Parser.java:365)
at org.h2.command.Parser.parse(Parser.java:320)
at org.h2.command.Parser.parse(Parser.java:292)
at org.h2.command.Parser.prepareCommand(Parser.java:257)
at org.h2.engine.Session.prepareLocal(Session.java:573)
at org.h2.engine.Session.prepareCommand(Session.java:514)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
at 
org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:482)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSql(IgniteH2Indexing.java:870)
... 16 more

\\
seems the internal h2 want to create index with name of "primary"?!

please advise, thanks.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/encounter-issue-on-ignite-2-0-tp13812.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cache Metrics

[Dmitry Pavlov]

Hi Megha,

Please note there was improvement added about this metric
https://issues.apache.org/jira/browse/IGNITE-5490

Best Regards,
Dmitry Pavlov

чт, 15 июн. 2017 г. в 12:34, Megha Mittal :

> Hi,
>
> Thanks for your reply. It's quite possible that rebalancing might be taking
> place which led to this difference. As after some time I got matching
> numbers.
>
> But I am still not clear why is metrics().getOffHeapAllocatedSize() = 0 .
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-Metrics-tp13624p13809.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Ignite Cache Metrics

[Megha Mittal]

Hi,

Thanks for your reply. It's quite possible that rebalancing might be taking
place which led to this difference. As after some time I got matching
numbers.

But I am still not clear why is metrics().getOffHeapAllocatedSize() = 0 .



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

Ignite-cassandra module issue

[nash1k]

Hi! 
I'm using the cassandra as persistence store for my caches and have one
issue by handling a huge data (via IgniteDataStreamer from kafka). 
Ignite Configuration:
final IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
igniteConfiguration.setIgniteInstanceName("test");
igniteConfiguration.setClientMode(true);
igniteConfiguration.setGridLogger(new Slf4jLogger());
igniteConfiguration.setMetricsLogFrequency(0);
igniteConfiguration.setDiscoverySpi(configureTcpDiscoverySpi());
final BinaryConfiguration binaryConfiguration = new BinaryConfiguration();
binaryConfiguration.setCompactFooter(false);
igniteConfiguration.setBinaryConfiguration(binaryConfiguration);
igniteConfiguration.setPeerClassLoadingEnabled(true);
final MemoryPolicyConfiguration memoryPolicyConfiguration = new
MemoryPolicyConfiguration();
memoryPolicyConfiguration.setName("3Gb_Region_Eviction");
memoryPolicyConfiguration.setInitialSize(1024L * 1024L * 1024L);
memoryPolicyConfiguration.setMaxSize(3072L * 1024L * 1024L);
   
memoryPolicyConfiguration.setPageEvictionMode(DataPageEvictionMode.RANDOM_2_LRU);
final MemoryConfiguration memoryConfiguration = new MemoryConfiguration();
memoryConfiguration.setMemoryPolicies(memoryPolicyConfiguration);
igniteConfiguration.setMemoryConfiguration(memoryConfiguration);

Cache configuration:
final CacheConfiguration cacheConfiguration = new
CacheConfiguration<>();
cacheConfiguration.setAtomicityMode(CacheAtomicityMode.ATOMIC);
cacheConfiguration.setStoreKeepBinary(true);
cacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
cacheConfiguration.setBackups(0);
cacheConfiguration.setStatisticsEnabled(false);
cacheConfiguration.setName("TestCache");

cacheConfiguration.setReadThrough(true);
cacheConfiguration.setWriteThrough(true);

cacheConfiguration.setWriteBehindEnabled(true);
cacheConfiguration.setWriteBehindFlushFrequency(1);
cacheConfiguration.setWriteBehindFlushSize(0);
cacheConfiguration.setWriteBehindFlushThreadCount(2);
cacheConfiguration.setWriteBehindBatchSize(1);


final CassandraCacheStoreFactory
cacheStoreFactory = new CassandraCacheStoreFactory<>();
final DataSource dataSource = new DataSource();
dataSource.setContactPoints(contactPoints);
dataSource.setReadConsistency("ONE");
dataSource.setWriteConsistency("ONE");
dataSource.setLoadBalancingPolicy(new TokenAwarePolicy(new
RoundRobinPolicy()));
cacheStoreFactory.setDataSource(dataSource);

final String CASSANDRA_PERSISTENCE = "" +
"" +
"" +
"";
final KeyValuePersistenceSettings settings = new
KeyValuePersistenceSettings(
String.format(CASSANDRA_PERSISTENCE, "test", "test_table",
"java.lang.String", "PRIMITIVE",
"org.apache.ignite.binary.BinaryObject", "BLOB"));
cacheStoreFactory.setPersistenceSettings(settings);
cacheConfiguration.setCacheStoreFactory(cacheStoreFactory);

When application works some time (hour or more, may be less - from time to
time) I see this exceptions on the ignite nodes:
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=4f43d78b, name=null, uptime=00:12:00:072]
^-- H/N/C [hosts=3, nodes=3, CPUs=96]
^-- CPU [cur=0%, avg=1.86%, GC=0%]
^-- PageMemory [pages=118064]
^-- Heap [used=4800MB, free=53.12%, comm=10240MB]
^-- Non heap [used=78MB, free=-1%, comm=80MB]
^-- Public thread pool [active=0, idle=32, qSize=0]
^-- System thread pool [active=0, idle=32, qSize=0]
^-- Outbound messages queue [size=0]
[15:28:28,626][INFO][grid-timeout-worker-#39%null%][IgniteKernal] FreeList
[name=null, buckets=256, dataPages=102080, reusePages=0]
[15:29:02,317][WARNING][sys-#106%null%][CassandraCacheStore] Prepared
statement cluster error detected, refreshing Cassandra session
com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute
unknown prepared query : 0xcad5832309a512feeb602eec67408130. You may have
used a PreparedStatement that was created with another Cluster instance.
at
com.datastax.driver.core.SessionManager.makeRequestMessage(SessionManager.java:568)
at
com.datastax.driver.core.SessionManager.executeAsync(SessionManager.java:131)
at
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:63)
at
org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:144)
at
org.apache.ignite.cache.store.cassandra.CassandraCacheStore.load(CassandraCacheStore.java:168)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.load(GridCacheWriteBehindStore.java:500)
 

Ignite-jdbc port

[ishan-jain]

how can i set my jdbc discovery port value in ignite config xml file. Need to
change it from 11211 as i am using two ignite clusters



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

Re: Ignite Cache Metrics

[ezhuravlev]

Hi,

Are you sure that your cache was not accessed in the same time by another
nodes/threads? Are you sure that rebalance was finished?

Could you share some simple reproducer with us? 

I've tried to reproduce same behavior, but  OFFHEAP, PRIMARY & BACKUP was
equal to each other. Also, right after streaming of data
metrics().getOffHeapPrimaryEntriesCount() was a little bit smaller than
these sizes, but in a short time it became equal to them too. 

Here are other memory metrics:
https://apacheignite.readme.io/docs/memory-and-cache-metrics

Evgenii



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

Understanding peerclassloading

[Helge Waastad]

Hi,
I'm pretty new to the Apache Ignite.
I'm working with peerclassloading and need to understand a couple of
thing.

Scenario:
1x server and 1x client

Cache:
CacheConfiguration cc = new CacheConfiguration<>("my-
cache");

Code creating classnotfound:
FluidGridItem item = new FluidGridItem(UUID.randomUUID());
List ll = new ArrayList<>();
ll.add(item);
cache.put(key, ll);

Code loading class ok: (INFO: Class locally deployed: class
org.primefaces.extensions.model.fluidgrid.FluidGridItem)
FluidGridItem item = new FluidGridItem(UUID.randomUUID());
List ll = new ArrayList<>();
ll.add(item);
cache.put(key, Arrays.asList(ll.toArray()));


Can someone please explain why this is?
(It's been a headache resolving this - been trying to get a JCS project
migrated to Ignite)

br hw

deploy is not working by IgniteDataStreamer

[nash1k]

Hi! 
I tried to use IgniteDataStreamer with kafka integration (extends
StreamAdapter), but had a little strange situation.
final IgniteDataStreamer streamer =
ignite.dataStreamer(callCache().getName());
streamer.autoFlushFrequency(5000);
streamer.keepBinary(false);
streamer.perNodeBufferSize(5120);

On the remote node when I tried to get value from the Collection of entries: 
public void receive(final IgniteCache cache, final
Collection> callEntries) throws IgniteException {
callEntries.forEach(binaryCall -> {
Call call = binaryCall.getValue();
}

I have Exception:
[16:47:49] (err) Failed to execute compound future reducer:
GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
cancelled=false, err=null, futs=[true]]class
org.apache.ignite.IgniteCheckedException: DataStreamer request failed
[node=61c1854a-338f-435b-ae61-fa1ec3f8a1a7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1772)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:333)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
at
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
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:748)
Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
ru.test.domain.Call
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:701)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1745)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1704)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:273)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:161)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerEntry$1.getValue(DataStreamerEntry.java:96)
at
ru.test.service.CallbackReceiver.lambda$receive$1(CallbackReceiver.java:90)
at java.lang.Iterable.forEach(Iterable.java:75)
at ru.test.service.CallbackReceiver.receive(CallbackReceiver.java:81)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:382)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:301)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:58)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:88)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
at
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
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)
Caused by: java.lang.ClassNotFoundException: ru.test.domain.Call
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8478)
at
org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:340)
at

Transaction Boundary - Data Streamer

[Sri Ganesh V]

Hi,

Is it possible to use streamers to add data to different transactional
caches with transaction boundary defined?

Example : 
Transaction tx = ignite.transactions().txStart();

   strmr1.addData(1,"xyz"); // strmr1 is configured to stream data
to cache1 (cache1-transactional)
   strmr2.addData(2,"abc"); // strmr2 is configured to stream data
to cache2 (cache2-transactional)

tx.commit();

Please suggest the best way to achieve this with optimal performance for
both cache inserts and updates.

Thanks,
Ganesh



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Transaction-Boundary-Data-Streamer-tp13803.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NoClassDefFoundError org/h2/server/Service

[ezhuravlev]

Hi,

SensorDataGenerator doesn't start Ignite node, so you should have only 1
server and 1 client node in topology:

Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=6.8GB]

Check it, most probably you have one more running server node on your host.

Also, your topology version is 46, it's strange, looks like nodes failed and
started nearly 20 times.

Evgenii



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NoClassDefFoundError-org-h2-server-Service-tp13636p13802.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.