Re: Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

[Jeff Jiao]

Thank you..
We have very large data set and several servers with big memory so it will
be ok to reach 80% or even 90%.
I recommend to highlight this major change in detail in "[ANNOUNCE] Apache
Ignite 2.2.0/2.3.0 Released", now I understand in 2.2 release announcement
"This release includes a couple of fixes to resolve excessive memory usage
caused by default memory allocation parameters." means this...



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

Yardstick benchmarking on Ignite with Persistent store

[amol wagh]

Hello,

I recently started experimenting with Apache Ignite. I want to experiment
the persistent store feature in particular. I am running Apache Ignite and
I successfully tried example programs for persisting data on SSD. Now, I
want run yardstick benchmarks in similar configuration, I followed the same
configuration steps like I followed for examples but no luck. I can not see
data on SSD that I have mounted.

So question are 1) Does Yardstick benchmarks have implementation to write
data to storage device.
2) If yes, how to configure or do we need any modification to benchmarks?

here are couple of line I followed in java code-
- setPersistenceEnabled to true
- setCustomStoragePath to custom location
- setWalArchivePath to custom
- setWlPath to custom
- set data store configuration
-start ignite server


Thanks,
AW

Re: Problems with explain statemenz

[dk]

Thanks,

that is absolutely correct.

If explain is used only the first colum contains a value.

Thus the following statement prints out the execution plan:

try (FieldsQueryCursor> joinCursor =  activityCache.query(sql)) {
 
for (List row : joinCursor){
 
System.out.println(" explain statement: " + row.get(0); 

}

}



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

Re: What is the path for Log4j configuration?

[Ralph Goers]

I’ve looked at Ignite’s Log4j2Logger. It calls Log4j2’s Configurator when the 
class is constructed. The problem here is that if you are using Log4j 2 and are 
logging before Ignite initializes you do not want this behavior. Furthermore, 
it tries to programmatically create a ConsoleAppender, which is likely you 
don’t want or need.  I am thinking I will create an alternate Logger for Ignite 
that doesn’t do any of this and submit a PR for it. With that you will just 
configure Log4j according to the Log4j documentation and these problems will go 
away. I could add it to Log4j itself but it really doesn’t belong there.

Ralph

> On Dec 14, 2017, at 12:00 PM, Ralph Goers  wrote:
> 
> Did you add the status=“DEBUG”?  I suspect that log4j is being initialized 
> before ignite starts and then Ignite is trying to reconfigure it. Previously 
> you had no log4j2.xml so the initial configuration failed but Ignite’s 
> probably worked. Once you moved the file the initial configuration worked but 
> Ignite was unable to configure logging. Personally, I have my own version of 
> Log4j2Logger that only routes ignites logging calls to Log4j and does none of 
> the extra stuff. In that case you just configure Log4j “normally” and this 
> problem doesn’t occur.  I’ll take a look at the Ignite code and try to 
> determine why it is having these problems.
> 
> Ralph
> 
>> On Dec 14, 2017, at 11:27 AM, sherryhw  wrote:
>> 
>> I moved the log4j2.xml into the resources folder now.
>> --resources
>> |--config
>> |--data-node-config.xml
>> |--log4j2.xml
>> 
>> Now when I start the data-node, the spring log file is fine at first, can
>> printout the debug mode of spring log, however, it still fails at Ignite.
>> "Exception in thread "main" class org.apache.ignite.IgniteException: Failed
>> to instantiate Spring XML application context
>> [springUrl=/target/classes/config/data-node-config.xml, err=Error
>> creating bean with name
>> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL
>> [...target/classes/config/data-node-config.xml]: Cannot create inner bean
>> 'org.apache.ignite.logger.log4j2.Log4J2Logger#d2de489' of type
>> [org.apache.ignite.logger.log4j2.Log4J2Logger] while setting bean property
>> 'gridLogger'; nested exception is
>> org.springframework.beans.factory.BeanCreationException: Error creating bean
>> with name 'org.apache.ignite.logger.log4j2.Log4J2Logger#d2de489' defined in
>> URL [/target/classes/config/data-node-config.xml]: Bean instantiation
>> via constructor failed; nested exception is
>> org.springframework.beans.BeanInstantiationException: Failed to instantiate
>> [org.apache.ignite.logger.log4j2.Log4J2Logger]: Constructor threw exception;
>> nested exception is class org.apache.ignite.IgniteCheckedException: Log4j
>> configuration path was not found: /log4j2.xml]
>> "
>> 
>> So the issue should be within the ignite trying to configure the log.
>> Do you have any ideas how to resolve it?
>> If I use absolute path, it could work correctly.
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>> 
> 
> 
> 

Re: memory usage in 2.3

[Denis Magda]

Hi Shawn,

> but in my ignite config ss.xml, I use another bean id "ignite.cfg" for class 
> org.apache.ignite.configuration.IgniteConfiguration.
> will this cause the problem?

Yes, the above should be a reason on why the memory configuration changes were 
not picked up.

—
Denis

> On Dec 13, 2017, at 7:05 PM, shawn.du  wrote:
> 
> 
> Hi Denis,
> [policyName=default, size=12.9 GB]
> It seems that 30G off heap setting didn't take effect.
> 
> I set it in default-config.xml
> 
>   class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
>  class="org.apache.ignite.configuration.DataStorageConfiguration">
> 
> 
>  class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
> 
> 
>
> 
> 
>  
> 
> but in my ignite config ss.xml, I use another bean id "ignite.cfg" for class 
> org.apache.ignite.configuration.IgniteConfiguration.
> will this cause the problem?
> 
> Thanks
> Shawn
> 
> On 12/14/2017 10:48，shawn.du 
>  wrote： 
> Hi Denis,
> 
> after run 20 hours, ignite client can't update cache and threw blow 
> exceptions:
> 
>  Caused by: org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not 
> enough memory allocated (consider increasing data region size or enabling 
> evictions) [policyName=default, size=12.9 GB]
> at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:292)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePageNoReuse(DataStructure.java:117)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePage(DataStructure.java:105)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$8400(BPlusTree.java:81)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertWithSplit(BPlusTree.java:2703)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:2665)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$2500(BPlusTree.java:2547)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:411)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:392)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4697)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4682)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:342)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:261)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$11100(BPlusTree.java:81)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:2859)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7600(BPlusTree.java:2547)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2285)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2266)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2266)
>  ~[stormjar.jar:?]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2006)
>  ~[stormjar.jar:?]
> 
> I had only a node running ignite server. others are all in client mode.
> I start ignite server with -Xms10g -Xmx10g and set default region size 30G. 
> disable persistence, disable on-heap cache.
> 
> also find this using visorcmd with command "node "
> | Maximum 

Is it possible to change notify event for continuous query

[fefe]

My data in ignite cache are Maps(the map can be pretty big, few kilobytes).
Is it possible to change the value of the event that is generated for the
continuous query when filter passed? Currently, the continuous query event
returns the whole map, but I need only a subset of values from that map.
Ideally, there would be more continuous queries for that cache and each of
them would return the different subset of values from that map.

thanks,



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

Re: Cache listener for new keys

[fefe]

Hello Alex,

I need to be notified about new keys, because on every client I am creating
a register of the keys. My keys are not the simple number, but contains id,
type and version. Key register on the client then contain info about latest
version per data/id and so on... 





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

Re: How to re-direct Ignite logs to log4j2?

[sherryhw]

Hi I have a same issue here.
How did you resolve it?
Thanks.
Sherry



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

Re: What is the path for Log4j configuration?

[Ralph Goers]

Did you add the status=“DEBUG”?  I suspect that log4j is being initialized 
before ignite starts and then Ignite is trying to reconfigure it. Previously 
you had no log4j2.xml so the initial configuration failed but Ignite’s probably 
worked. Once you moved the file the initial configuration worked but Ignite was 
unable to configure logging. Personally, I have my own version of Log4j2Logger 
that only routes ignites logging calls to Log4j and does none of the extra 
stuff. In that case you just configure Log4j “normally” and this problem 
doesn’t occur.  I’ll take a look at the Ignite code and try to determine why it 
is having these problems.

Ralph

> On Dec 14, 2017, at 11:27 AM, sherryhw  wrote:
> 
> I moved the log4j2.xml into the resources folder now.
> --resources
>  |--config
>  |--data-node-config.xml
>  |--log4j2.xml
> 
> Now when I start the data-node, the spring log file is fine at first, can
> printout the debug mode of spring log, however, it still fails at Ignite.
> "Exception in thread "main" class org.apache.ignite.IgniteException: Failed
> to instantiate Spring XML application context
> [springUrl=/target/classes/config/data-node-config.xml, err=Error
> creating bean with name
> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL
> [...target/classes/config/data-node-config.xml]: Cannot create inner bean
> 'org.apache.ignite.logger.log4j2.Log4J2Logger#d2de489' of type
> [org.apache.ignite.logger.log4j2.Log4J2Logger] while setting bean property
> 'gridLogger'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'org.apache.ignite.logger.log4j2.Log4J2Logger#d2de489' defined in
> URL [/target/classes/config/data-node-config.xml]: Bean instantiation
> via constructor failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.apache.ignite.logger.log4j2.Log4J2Logger]: Constructor threw exception;
> nested exception is class org.apache.ignite.IgniteCheckedException: Log4j
> configuration path was not found: /log4j2.xml]
> "
> 
> So the issue should be within the ignite trying to configure the log.
> Do you have any ideas how to resolve it?
> If I use absolute path, it could work correctly.
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> 

Re: What is the path for Log4j configuration?

[sherryhw]

I moved the log4j2.xml into the resources folder now.
--resources
  |--config
  |--data-node-config.xml
  |--log4j2.xml

Now when I start the data-node, the spring log file is fine at first, can
printout the debug mode of spring log, however, it still fails at Ignite.
"Exception in thread "main" class org.apache.ignite.IgniteException: Failed
to instantiate Spring XML application context
[springUrl=/target/classes/config/data-node-config.xml, err=Error
creating bean with name
'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL
[...target/classes/config/data-node-config.xml]: Cannot create inner bean
'org.apache.ignite.logger.log4j2.Log4J2Logger#d2de489' of type
[org.apache.ignite.logger.log4j2.Log4J2Logger] while setting bean property
'gridLogger'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'org.apache.ignite.logger.log4j2.Log4J2Logger#d2de489' defined in
URL [/target/classes/config/data-node-config.xml]: Bean instantiation
via constructor failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[org.apache.ignite.logger.log4j2.Log4J2Logger]: Constructor threw exception;
nested exception is class org.apache.ignite.IgniteCheckedException: Log4j
configuration path was not found: /log4j2.xml]
"

So the issue should be within the ignite trying to configure the log.
Do you have any ideas how to resolve it?
If I use absolute path, it could work correctly.



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

Re: What is the path for Log4j configuration?

[Ralph Goers]

I should qualify that. I would have to look at Ignite’s version of the 
Log4j2Logger class (I don’t use that myself as it does some things I don’t care 
for). If it is properly calling the Log4j 2 Configurator with the path you 
provided then it should be working. However, there are scenarios where it may 
be initializing Log4j 2 properly but Log4j tried to configure itself first and 
didn’t find the file but then Ignite forced it to reconfigure with the new 
file. In that case you can ignore the error message.  You should add 
status=“DEBUG” to the configuration element in your log4j2.xml to see if the 
file is ever being configured.

Ralph

> On Dec 14, 2017, at 11:09 AM, Ralph Goers  wrote:
> 
> Log4j 2 won’t find that because it is config/log4j2.xml and it is looking for 
> log4j2.xml on the classpath.
> 
> Ralph
> 
>> On Dec 14, 2017, at 11:07 AM, sherryhw  wrote:
>> 
>> It is in "target/classes/config/log4j2.xml"
>> Is this what you mentioned?
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>> 
> 
> 
> 

Re: What is the path for Log4j configuration?

[Ralph Goers]

Log4j 2 won’t find that because it is config/log4j2.xml and it is looking for 
log4j2.xml on the classpath.

Ralph

> On Dec 14, 2017, at 11:07 AM, sherryhw  wrote:
> 
> It is in "target/classes/config/log4j2.xml"
> Is this what you mentioned?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> 

Re: What is the path for Log4j configuration?

[sherryhw]

It is in "target/classes/config/log4j2.xml"
Is this what you mentioned?



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

Re: What is the path for Log4j configuration?

[Ralph Goers]

Do you have a log4j2.xml on your classpath?

Ralph


> On Dec 14, 2017, at 11:04 AM, sherryhw  wrote:
> 
> Thanks.
> However I checked the log4j 2 is in my pom and it is in my classpath. So I
> guess it is not this cause?
> Sherry
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> 

Re: What is the path for Log4j configuration?

[sherryhw]

Thanks.
However I checked the log4j 2 is in my pom and it is in my classpath. So I
guess it is not this cause?
Sherry



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

Re: What is the path for Log4j configuration?

[Rajarshi Pain]

Hello,
Check if you have log4j jar in build path? I guess jar is missing.

Thanks,
Raj

On Thu 14 Dec, 2017, 23:22 sherryhw,  wrote:

> Hi guys,
> I am using Log4j2 for Ignite logging, but I always have this error:
> "* Failed to instantiate [org.apache.ignite.logger.log4j2.Log4J2Logger]:
> Constructor threw exception; nested exception is class
> org.apache.ignite.IgniteCheckedException: Log4j configuration path was not
> found:config/log4j2.xml*"
>
> This is my configuration.
> *data-node-config.xml*
> 
> 
> 
>  value="config/log4j2.xml"/>
> 
> 
> 
> And my log4j2.xml locates in the same folder as data-node-config.xml. Both
> of them are in config folder.
> File structure:
> --src
>   |--main
> |--java
>   |--DataNodeStartUp.java
> |--resources
>   |--config
>  |--data-node-config.xml
>  |--log4j2.xml
> However, whenever I run DataNodeStartUp.java main method to call "Ignite
> ignite = Ignition.start("config/data-node-config.xml");" to start my
> data-node, it always has the error for cannot find the  Log4j configuration
> path.
> If I use the absolute path it can work. So there is nothing wrong with my
> other configurations. What is this relative path of log4j2.xml?
>
> Thanks!
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
-- 

Thanks
Rajarshi

What is the path for Log4j configuration?

[sherryhw]

Hi guys, 
I am using Log4j2 for Ignite logging, but I always have this error:
"* Failed to instantiate [org.apache.ignite.logger.log4j2.Log4J2Logger]:
Constructor threw exception; nested exception is class
org.apache.ignite.IgniteCheckedException: Log4j configuration path was not
found:config/log4j2.xml*"

This is my configuration.
*data-node-config.xml*







And my log4j2.xml locates in the same folder as data-node-config.xml. Both
of them are in config folder.
File structure:
--src
  |--main
|--java
  |--DataNodeStartUp.java
|--resources
  |--config
 |--data-node-config.xml
 |--log4j2.xml
However, whenever I run DataNodeStartUp.java main method to call "Ignite
ignite = Ignition.start("config/data-node-config.xml");" to start my
data-node, it always has the error for cannot find the  Log4j configuration
path. 
If I use the absolute path it can work. So there is nothing wrong with my
other configurations. What is this relative path of log4j2.xml?

Thanks!
 



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

Re: how to set SQL timeout for the cluster?

[afedotov]

Hi,

For now, it's possible to set timeout only on the query based level, i.e.
setTimeout().
You could create a utility factory method for the Query instances that would
set up the required timeout and use it throughout the code.

Kind regards,
Alex




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

Re: Failed to instantiate Spring XML application context

[Rajarshi Pain]

Thanks Alex. I will try this tomorrow.
It's given wrong in the Apache Ignite Website which has to be corrected.

*Link: *
https://apacheignite.readme.io/v1.0/docs/off-heap-memory#section-onheap_tiered



[image: Inline image 1]

Thanks,
Raj

On Thu, Dec 14, 2017 at 5:43 PM, Alexey Kukushkin  wrote:

> You have a wrong class name CacheFifoEvictionPolicy. It should be
> FifoEvictionPolicy
>



-- 
Regards,
Rajarshi Pain

Re: Count mismatch for a cache between ignitevisor & Sqlline

[afedotov]

Hi,

Could you please check, what result would produce a regular Ignite
SqlFieldsQuery?
Would it be the same result as for Sqlline?

Kind regards,
Alex



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

how to set SQL timeout for the cluster?

[Aurora]

Hi igniters,
we want to avoid long query SQL running in the cluster, thus we need setup
unified SQL timeout in the XML configuration file.
but I didn't find related properties or beans.
how?  thanks.



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

Re: Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

[daniels]

Thank you,dear Alexey.



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

Re: Sorting or ranking TextQuery?

[zbyszek]

Andrew,
Thank you for your response.

>>So, it looks like this integration has very limited scope of use.
I was interested in one particular Lucene feature which is described as
"Lucene returns results ... sorted by an arbitrary field", so any way of
influencing order/ranking in the query result would be really helpful.
Seems like H2 integration with Lucene could do the trick.

Regards,
zbyszek



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

Re: insert so slow via JDBC thin driver

[Alexey Kukushkin]

With one server you just insert data locally. After you added the second
server you started moving data over the network. Apparently putting data
into local RAM is much faster than delivering same date to a remote node.

Ignite is first of all a distributed system. I suggest this: configure your
data loader node as Ignite client. Measure performance of loading data into
one server node (1 server + 1 client cluster) and then measure performance
of loading same data into two server nodes (2 servers + 1 client cluster).
You will get linear performance increase.

Re: BinaryMarshaller unmarshal error

[Alexey Kukushkin]

You must have the service JARs on the server Ignite's classpath. Peer class
loading is not applicable here. Adding the service class to binary config
is not required.

Re: Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

[Alexey Kukushkin]

The reason to reduce default amount of memory allocated for Ignite from 80%
to 20% was numerous complaints about severe performance degradation. The
investigations showed that was due to remaining 20% of RAM often was not
enough for the operating system and other typical enterprise utilities to
operate efficiently thus killing the server performance. 20% was considered
a safe default amount and you can always configure amount of available
memory

for your specific setup.

The memory configuration

is applicable only for off-heap memory. If you enabled on-heap caching, it
is strongly recommended to configure an eviction policy

to limit the on-heap memory usage. Otherwise you can go out of memory.

Re: Failed to instantiate Spring XML application context

[Alexey Kukushkin]

You have a wrong class name CacheFifoEvictionPolicy. It should be
FifoEvictionPolicy

Re: How to do 'stream processing' and more questions of a Ignite newbie

[Alexey Kukushkin]

1. To reduce operating costs in real enterprise environments, have a single
application-agnostic Ignite cluster and multiple business function-centric
applications configuring themselves in the cluster upon startup. You will
have a single Ignite server configuration file including generic settings
(e.g. discovery mechanism, memory and persistence settings, whether to
support peer class loading) and application-specific configurations
defining the application data models (caches configuration). The Operations
team will manage a single cluster while the apps are still decoupled from
each other thus reducing the operating cost.

In real enterprise environments the admins would create wrappers over
ignite.sh (or develop a script from scratch) to start/stop the cluster
where enterprise-wide deployment, monitoring, error handling, logging,
networking, etc. settings would be automatically applied.

2. Web Console allows you to configure cluster and data model by filling
web forms (either from scratch or automatically converting existing
relational model). It is up to you to decide whether you prefer editing XML
yourself or filling web forms and the generating XML (and Java project
skeleton) automatically. You may consider generating initial project using
Web Console and then continue updating it by editing raw XML.

3. I think you already answered your question: you need to either enable
peer class loading or have the Interpolation class on the server classpath.
The reason is that, even though your simple server-side filter "e -> true"
does not capture any outer class members, Java lambda still has an implicit
reference to the outer class "Interpolation" that has to be deserialised.

Ignite supports Docker deployment
. Did you try
following the instructions? Share your specific problems if you have any.
Also, as an application developer, you are less focused on the deployment
approach - that is normally for the enterprise Operations team to decide.
As I recommended above, consider the cluster as a shared "resource" that
your app would connect to no matter how the cluster was deployed.

4. Not sure I understood your question. I guess your concern is you were
getting all events in local listener since your remote filter passes all
the events. You are right that you need to properly filter events on the
server side using remote filter to minimise traffic.
You can run a continuous query from any kind of node - either client or
server nodes. "local" listener means it is running on the node where the
query was originated and remote filter runs on all the remote server nodes.

insert so slow via JDBC thin driver

[Michael Jay]

Hello, I am a new Ignite leaner. I want to insert 50,000,000 rows into a
table. Here,i got a problem.
When one host and one sever node, the speed of insert is about 2,000,000 per
minute,  the usage of cpu is 30-40%; however two hosts and two sever nodes,
about 100,000 per minute,and the usage of cpu is only 5%. It's so slow,what
can i do to improve the performance? Thanks.

my default-config.xml:
   





   








































10x.x.x.226:47500..47509

10x.x.x.75:47500..47509












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

Re: BinaryMarshaller unmarshal error

[yonggu.lee]

After add a type name of my service impl to binary config, the service
deployment succeeded. 

However, I don't understand why I have to supply a specific service impl
name in config, though that class is provided as jar in the classpath of
ignite.

And still Scan query from web console failed with the message, 

Error: class org.apache.ignite.IgniteCheckedException: Query execution
failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN,
clsName=null, clause=null, filter=null, transform=null, part=null,
incMeta=false, metrics=GridCacheQueryMetricsAdapter
[minTime=9223372036854775807, maxTime=0, sumTime=0, avgTime=0.0, execs=0,
completed=0, fails=0], pageSize=100, timeout=0, keepAll=true,
incBackups=false, dedup=false, prj=null, keepBinary=true,
subjId=d068bad1-3bf7-45a0-8fa1-437b0d4e5f0e, taskHash=0], rdc=null,
trans=null]



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