Thin client cannot retrieve data that was inserted with the regular Ignite client when using a composite key

[Roman Shtykh]

Thin client cannot retrieve data with the composite key when it is put by a 
regular (thick) Ignite client.

Is any additional configuration needed or is it a bug?


    import java.io.Serializable;
    import org.apache.ignite.Ignite;
    import org.apache.ignite.IgniteCache;
    import org.apache.ignite.Ignition;
    import org.apache.ignite.client.ClientCache;
    import org.apache.ignite.client.ClientException;
    import org.apache.ignite.client.IgniteClient;
    import org.apache.ignite.configuration.ClientConfiguration;
    
    public class ThinClientGets {
    final static String CACHE_NAME = "testCache";
    
    public static void main(String[] args) {
    try (Ignite ignite = Ignition.start()) {
    try (IgniteCache c = 
ignite.getOrCreateCache(CACHE_NAME)) {
    c.put(new TestKey("a", "0"), 1);
    
    System.out.println("Val: " + c.get(new TestKey("a", "0")));
    }
    
    try (IgniteCache c = 
ignite.getOrCreateCache(CACHE_NAME + 2)) {
    c.put("k1", 1);
    
    System.out.println("Val: " + c.get("k1"));
    }
    
    // thin client
    System.out.println("-- Getting with a thin client --");
    ClientConfiguration cfg = new 
ClientConfiguration().setAddresses("127.0.0.1:10800");
    
    try (IgniteClient igniteClient = Ignition.startClient(cfg)) {
    ClientCache cache = 
igniteClient.cache(CACHE_NAME);
    
    // null here!
    System.out.println(cache.get(new TestKey("a", "0")));
    
    ClientCache cache2 = 
igniteClient.cache(CACHE_NAME + 2);
    
    System.out.println(cache2.get("k1"));
    }
    catch (ClientException e) {
    System.err.println(e.getMessage());
    }
    catch (Exception e) {
    System.err.format("Unexpected failure: %s\n", e);
    
    }
    }
    }
    
    static class TestKey implements Serializable {
    private final String a;
    
    private final String b;
    
    public TestKey(String a, String b) {
    this.a = a;
    this.b = b;
    }
    
    public String getA() {
    return a;
    }
    
    public String getB() {
    return b;
    }
    }
    }


--
Roman

Quering with PHP PDO returns null for all column values except the 1st one

[Roman Shtykh]

Hello,
PHP PDO returns null for all column values except the 1st one. Using PHP 
odbc_connect returns all column values.
array(10) {  ["ORGID"]=>  string(1) "2"  [0]=>  string(1) "2"  ["FIRSTNAME"]=>  
NULL  [1]=>  NULL  ["LASTNAME"]=>  NULL  [2]=>  NULL  ["RESUME"]=>  NULL  [3]=> 
 NULL  ["SALARY"]=>  NULL  [4]=>  NULL}
The description how it can be reproduced is here
https://issues.apache.org/jira/browse/IGNITE-9897

I remember it was not a problem with Ignite 2.0. Any workaround or fix for this 
issue?
-- Roman

Re: Docker deployment with EXTERNAL_LIBS environment variable

[Roman Shtykh]

I had the same problem (pretty common not having -i option) and fixed it. Need 
a review.https://issues.apache.org/jira/browse/IGNITE-8143
-- Roman
 

On Tuesday, April 17, 2018, 7:15:25 p.m. GMT+9, Petr Ivanov 
 wrote:  
 
 Hi, Kseniya.


I guess that something wrong with wget in distribution (alpine-linux). I will 
need some testing to investigate further.



> On 17 Apr 2018, at 13:02, Ksenia Vazhdaeva  wrote:
> 
> Hello,
> 
> I am trying to deploy Apache Ignite 2.4.0 in docker using external libs as
> described at https://apacheignite.readme.io/docs/docker-deployment
> 
> /docker run -d --name ignite -v
> /storage/ignite/ignite-server-config.xml:/etc/ignite/ignite-server-config.xml
> \
>    -e "CONFIG_URI=file:///etc/ignite/ignite-server-config.xml" -p
> 47500:47500 \
>    -e
> "EXTERNAL_LIBS=http://central.maven.org/maven2/org/apache/ignite/ignite-schedule/1.0.0/ignite-schedule-1.0.0.jar";
> \
>    apacheignite/ignite:2.4.0/
> 
> Docker container is started but in docker logs there is an error
> 
> /wget: unrecognized option: i
> BusyBox v1.27.2 (2017-12-12 10:41:50 GMT) multi-call binary.
> 
> Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document
> FILE]
>     [--header 'header: value'] [-Y|--proxy on/off] [-P DIR]
>     [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL.../
> 
> Thus the external lib is not loaded.
> Could you, please, help me to resolve the problem or provide me with another
> way to add external libraries to Ignite classpath?
> 
> Thanks in advance,
> Ksenia
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
  

Re: Kubernetes - Access Ignite Cluster Externally

[Roman Shtykh]

I have been playing with this for a while, and managed to get an external 
client node get into the topology, but it failed to communicate to the cluster. 
Some points:1. Used TcpDiscoveryKubernetesIpFinder for sever nodes
2. Exposed pods via NodePort on custom ports (higher than 3); more flexible 
than hostNetwork = True
3. Created an address resolver for finding and communication SPIs, so that pods 
addresses are conveyed to the external client.4. Used TcpDiscoveryVmIpFinder 
for the client to successfully join the topology.
Unfortunately, TcpCommunicationSPI fails to connect to the server nodes. The 
client has all addresses of the ClusterNode it attempts to connect to, 
including internal pods' IP, 127.0.0.1, 0:0:0:0:0:0:0:0 and external IP, but 
fails to reach the external IP from the list (see 
TcpCommunicationSPI.createTcpClient). Having ClusterNode expose only the 
address that was registered by the address resolver might fix it (haven't 
checked yet) -- anyway, I think the client should not be provided with and 
communicate via internal addresses iff external addresses are provided, should 
it?
-- Roman
 

On Thursday, April 5, 2018, 3:33:10 p.m. GMT+9, sid_human 
 wrote:  
 
 Hi 

I had recently come across this similar issue. I have multiple ignite server
pods up in a cluster and running in 3 - 4 nodes. At the same time, I have
ignite clients that can connect and work perfectly fine if they are running
as pods in these nodes. 

I tried to implement an external client connecting to the ignite server pods
cluster but no avail. I have followed through the readme.io pages of
kubernetes discovery. Here are the issues I had confronted:

1) Setting hostNetwork = True in the yaml configuration of ignite pods is a
network issue because running multiple containers on a node and each
container trying to host the port would send an error. So, I tried running
one container - one node. 
2) I have added a comment  IGNITE-4161
  with the exact client
configurations which seem to retrieve the server pods IP addresses. But no
connection is made.

I'm afraid no one has tried this before successfully and no development on
external clients are made as someone had posted in the same Jira- issue.

Thank you.



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

Re: Using Apache Ignite with Zookeeper

[Roman Shtykh]

You can specify the port your zk is running on as shown in [1], and it should 
be opened

https://apacheignite.readme.io/docs/cluster-config#zookeeper-based-discovery
Roman
 

On Thursday, April 5, 2018, 4:48:05 p.m. GMT+9, monalsinha 
 wrote:  
 
 I am using Apche Ignite with zookeeper based discovery using curator
framework.
Do I need to open any port on my ignite node like TCP based discovery, in
order for this to work?



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

Re: REST API qryexe saying Argument cannot be null: sql.

[Roman Shtykh]

Hi Anji,
Can you provide more details (what queries are issued, what output is produced, 
etc.) for your additional questions to be answered?
-- Roman
 
 

On Thursday, September 14, 2017, 4:37:08 AM GMT+9, ANJANEYA PRASAD 
NIDUBROLU  wrote:  
 
 Hello Roman,
Thanks...I have tried adding '&' and looks like it will work, currently I am 
getting exceptions due to class/ type i created.But, one doubt will REST API 
not accept single argument?
In my earlier example, i tried arg1=xxx&qry=+%3D+%3F, then it is 
complaining that parameter '#1' is not set.Again i tried the same by adding 
another predicate and came with successStatus = 0.
Similarly, how about more than 3 or 4 arguments, will i be able to use arg3, 
arg4, ?
Please suggest.
Thanks,Anji.
On Wed, Sep 13, 2017 at 9:44 AM, Roman Shtykh  wrote:

Hi Anji,
The error says that you don't provide sql query.You might miss "&" before "qry".

-- Roman
 

On Wednesday, September 13, 2017, 2:42:12 AM GMT+9, ANJANEYA PRASAD 
NIDUBROLU  wrote:  
 
 Thanks Evgenii...
Actually i have included "Type" and "CacheName" also. But i pasted wrong url by 
mistakenly. The result is still the same. Here in the query/ REST url nowhere i 
am using "sql". May be "qry" from the REST url/command will be parsed to "sql". 
Not sure how and where this parsing is happening and what is wrong with the url 
I am trying.
Any thoughts please?
Thanks,Anji.
On Tuesday, September 12, 2017, ezhuravlev  wrote:

Hi,

I don't see in your query defined cacheName and type parameters. If cache
name not provided, default cache will be used.

You can find all this information in the documentation:
https://apacheignite.readme.io /docs/rest-api#section-sql-que ry-execute

Also, have you checked logs from Ignite node?

Evgenii



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

  

  

[Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

[Roman Shtykh]

Hi,

I will be making a short presentation at Data Platform Conference Tokyo 2017 on 
Apache Ignite with emphasis on IoT.
Attending is free. Please come if you are in Tokyo.

https://ignite.apache.org/events.html#dataplatform-jp
Best regards,Roman

Re: REST API qryexe saying Argument cannot be null: sql.

[Roman Shtykh]

Hi Anji,
The error says that you don't provide sql query.You might miss "&" before "qry".

-- Roman
 

On Wednesday, September 13, 2017, 2:42:12 AM GMT+9, ANJANEYA PRASAD 
NIDUBROLU  wrote:  
 
 Thanks Evgenii...
Actually i have included "Type" and "CacheName" also. But i pasted wrong url by 
mistakenly. The result is still the same. Here in the query/ REST url nowhere i 
am using "sql". May be "qry" from the REST url/command will be parsed to "sql". 
Not sure how and where this parsing is happening and what is wrong with the url 
I am trying.
Any thoughts please?
Thanks,Anji.
On Tuesday, September 12, 2017, ezhuravlev  wrote:

Hi,

I don't see in your query defined cacheName and type parameters. If cache
name not provided, default cache will be used.

You can find all this information in the documentation:
https://apacheignite.readme.io /docs/rest-api#section-sql-que ry-execute

Also, have you checked logs from Ignite node?

Evgenii



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

Re: About Apache Ignite in Japanese

[Roman Shtykh]

Thank you, guys!

The project is little known in Japan, and I am trying to raise attention to it. 
I might ping you for some help in future :)
-- Roman



On Friday, July 28, 2017 11:21 PM, Tom Diederich 
 wrote:
 

 Awesome job! Let me know if I can help with any language-realted translations 
to or from Japanese! I speak some but my wife is Japanese and we can together 
help. :-)






On Jul 28, 2017, at 12:51 AM, Yakov Zhdanov  wrote:
Wow! Very cool! Great job, Roman!
--Yakov



   

Re: Is it necessary to configure setting HBase which use Secondary File System?

[Roman Shtykh]

Vladimir,
Isn't it the point of "hbase.wal.dir" to have WAL in a different directory or 
even a different file system? [1]
Also, both HBase WAL and IgniteHadoopFileSystem use 
'org.apache.hadoop.fs.FileSystem'. I am just curious how it breaks HBase.

[1] https://issues.apache.org/jira/browse/HBASE-17437[2] 
https://github.com/apache/hbase/blob/c38bf12444aca77c7cb12637147c07dc711acbe9/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
-- Roman


On Thursday, June 8, 2017 5:00 PM, Vladimir Ozerov  
wrote:
 

 Hi Takashi,
"igfs://" prefix should be used in your application code, in those places where 
data is accessed. It is illegal to change "hbase.wal.dir" property, as it 
breaks HBase internals.
On Thu, Jun 8, 2017 at 6:30 AM, Takashi Sasaki  wrote:

Hello,

I used igfs:// instead of hdfs:// for hbase.wal.dir property, then
HBase Master Server throwed Exception.

2017-06-08 02:51:56,745 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase. master.HMaster.
        at org.apache.hadoop.hbase. master.HMaster. 
constructMaster(HMaster.java: 2577)
        at org.apache.hadoop.hbase. master.HMasterCommandLine. startMaster( 
HMasterCommandLine.java:231)
        at org.apache.hadoop.hbase. master.HMasterCommandLine.run( 
HMasterCommandLine.java:137)
        at org.apache.hadoop.util. ToolRunner.run(ToolRunner. java:70)
        at org.apache.hadoop.hbase.util. ServerCommandLine.doMain( 
ServerCommandLine.java:126)
        at org.apache.hadoop.hbase. master.HMaster.main(HMaster. java:2587)
Caused by: java.io.IOException: File system is already initialized:
org.apache.ignite.internal. processors.hadoop.impl.igfs. 
HadoopIgfsWrapper@1dbd580
        at org.apache.ignite.hadoop.fs. v1.IgniteHadoopFileSystem. initialize( 
IgniteHadoopFileSystem.java: 215)
        at org.apache.hadoop.hbase.fs. HFileSystem.( HFileSystem.java:87)
        at org.apache.hadoop.hbase. regionserver.HRegionServer. 
initializeFileSystem( HRegionServer.java:634)
        at org.apache.hadoop.hbase. regionserver.HRegionServer.< 
init>(HRegionServer.java:576)
        at org.apache.hadoop.hbase. master.HMaster.(HMaster. java:397)
        at sun.reflect. NativeConstructorAccessorImpl. newInstance0(Native 
Method)

I checked Ignite source code.
It seems to be called initialize method more than once, so the server
throw the exception.

I added properties to core-site.xml:

  fs.igfs.impl
  org.apache.ignite. hadoop.fs.v1. IgniteHadoopFileSystem


  fs.AbstractFileSystem. igfs.impl
  org.apache.ignite. hadoop.fs.v2. IgniteHadoopFileSystem


I changed property hbase-site.xml:

  hbase.wal.dir
  igfs://igfs@/user/ hbase/WAL


Hadoop version: 2.7.3
HBase version: 1.3.0
Ignite version: 2.0.0

How can I solve this problem?
Give me advice if you like.

Thanks,
Takashi

2017-06-07 21:38 GMT+09:00 Takashi Sasaki :
> Hello,
>
> I'm newbie of Ignite, so have some question.
>
> When I use Secondary File System to write HBase WAL, should I use
> igfs:// instead of hdfs:// ?
>
> hbase-site.xml(default) is hdfs://.
>
> --
> 
>   hbase.wal.dir
>   hdfs://[dnsname]:[port] /user/hbase/WAL
> 
> --
>
> Does the secondary file system require some configuration changes to Hbase?
>
> Please give me advice.
>
> Thanks,
> Takashi




   

Re: MyBatis Ignite L2 cache Integration issues

[Roman Shtykh]

Muthu,
For 1 & 2, have you checked [1]? I think it is not related to Ignite L2 
integration. Please see the cache section.
For 3, have you checked if it happens with the default L2 cache?

[1] http://www.mybatis.org/mybatis-3/sqlmap-xml.html

-- Roman
On Tuesday, June 6, 2017 9:06 AM, mlekshma  
wrote:
 

 Hi Folks,

I see the following issues when using mybatis-ignite. Wondering if any one
else faced & solved these issues or if i am missing something as these seem
very difficult to work around,

1. Eviction or flushing of all entries on insert : Basically whenever i call
a mapper.insert operation all current entries in the cache get flushed. I
guess i can set the flushCache to false and in the code follow up the insert
with a get by that id to make sure it gets cached..but i am wondering if
this is something that can be fixed or if i am doing something wrong.

2. No caching on insert : As mentioned earlier, in addition to flushing of
all entries the entry being inserted with mapper.insert is also not getting
cached by default which again can be worked around by the above method.

3. No caching when using selectByExample (to select based on a condition or
to select all entries) & select by a CustomCriteria (using Criteria Object)
: Basically when using mapper.selectByExample instead of selectByPrimaryKey
or when selecting with a custom criteria object, the fetched entities don't
get cached. I am not sure how i can work around this issue. This is also a
bit of a problem since on app restarts we will need the cache to be loaded
with all entries in the DB table by virtue of doing a
mapper.selectByExample.

Thanks
Muthu



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-issues-tp13391.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: How to create custom SinkRecord extractor?

[Roman Shtykh]

Check SinkRecord#value() [1]. Cast the object to the data type you use in your 
Kafka connector and extract the field you need.

And please continue posting your questions related to this topic in one thread 
-- we have a bunch already. Thank you!

[1] 
https://kafka.apache.org/0100/javadoc/index.html?org/apache/kafka/connect/sink/SinkRecord.html
-- Roman


On Wednesday, May 31, 2017 5:29 PM, ignitedFox  
wrote:
 

 hi,

I have records in kafka like;



Each record represents a "Bus" entry, with bus ID, route, etc. The records
are fetched from DB using Kafka JDBC Connector. I want to insert them to
Ignite, having "BUS_ID" as the key, and Bus object as the value. I got to
know that there need to do something like 



But I dont know how to do this. Somebody kindly help me on this?

Thank you



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-create-custom-SinkRecord-extractor-tp13261.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: How to solve SinkRecord cannot be cast exception?

[Roman Shtykh]

public Entry extract(TupleBus msg)  -> public Entry extract(SinkRecord msg) 
in your extractor.
-- Roman


On Tuesday, May 30, 2017 10:21 PM, ignitedFox  
wrote:
 

 Hi Humphrey,

So I need to create another class Bus? and define all getters and setters
there right? and instead of , i need to use ? is that the change I need to
make?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-solve-SinkRecord-cannot-be-cast-exception-tp13221p13231.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: Where should I place Kafka connect converter class files?

[Roman Shtykh]

How about making a jar with com.ignitedfox.ignite.stream.MyExtractor and 
putting it on the classpath (for instance, where your ignite-kafka-x.x.x.jar 
is)?
-- Roman  

On Tuesday, May 30, 2017 5:30 PM, ignitedFox  
wrote:
 

 Hi,

I have made a class "MyExtractor" like  to create custom key for Ignite sink
connector. The class belongs to package . When I try to launch connector, I
am getting the error;



I have placed my class files *MyExtractor* and *TupleBUS* (with specialized
toString() method and getKey() method for keys and all), in the directory .
I then made sub directories inside that folder and then I placed class files
inside . Still I am getting the same error. Somebody kindly tell me what is
wrong here and how to fix it.

Thank you.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Where-should-I-place-Kafka-connect-converter-class-files-tp13214.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: How to configure Ignite sink connector to use key-value?

[Roman Shtykh]

Hi,
Please see https://apacheignite-mix.readme.io/v2.0/docs/kafka-streamer

1. You can find the jars in the binary release of Ignite in lib/, for 
instance.2. To parse your json string and extract key and value, I recommend 
using Ignite 1.8 and up. With it, you can parse the incoming data with your 
extractor and decide what has to be your key. See this link for a simple 
extractor.https://github.com/apache/ignite/blob/master/modules/kafka/src/test/java/org/apache/ignite/stream/kafka/connect/IgniteSinkConnectorTest.java
-- Roman


On Monday, May 29, 2017 10:29 PM, Humphrey  wrote:
 

 See answers in the following post.

http://apache-ignite-users.70518.x6.nabble.com/Kindly-tell-me-where-to-find-these-jar-files-td12649.html

I think in the last step you need to convert the data you getting to an
cache object, for example Annotation Based Configuration [1] so you can use
it to query your cache. Implementing the StreamSingleTupleExtractor will do
the conversion for you to the correct format.

[1]
https://apacheignite.readme.io/docs/indexes#annotation-based-configuration



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-configure-Ignite-sink-connector-to-use-key-value-tp13162p13198.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

lhost 
-Ddb.port=5432 -Ddb.name=postgres -DIGNITE_QUIET=false -jar 
Documents\Work\server\target\ server-i
gnite-l2cache-poc-0.0.1- SNAPSHOT.jar
Listening for transport dt_socket at address: 8787

  .     _    __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|__ _/=/_/_/_/
 :: Spring Boot ::    (v1.5.2.RELEASE)

2017-05-26 01:00:19.161  INFO 14176 --- [   main] c.b.dcm.server. 
ObjectCacheApplication    : Starting ObjectCacheApplication v0.0.1-SNAPSHOT on 
VM-W2K8-50-168 with PID 14176 (C:\Users\Administrator\ 
Documents\Work\server\target
\server-ignite-l2cache-poc-0. 0.1-SNAPSHOT.jar started by Administrator in 
C:\Users\Administrator)
...
...
INFO:

>>> +- -- ---+
>>> Ignite ver. 2.0.0#20170430-sha1: d4eef3c68ff116ee34bc13648cd82c 640b3ea072
>>> +- -- ---+
>>> OS name: Windows Server 2008 R2 6.1 amd64
>>> CPU(s): 4
>>> Heap: 3.6GB
>>> VM name: 14176@VM-W2K8-50-168
>>> Ignite instance name: myBatisObjectGrid
>>> Local node [ID=96746C45-779D-4792-A3A1- 17C88C2A70A1, order=100, 
>>> clientMode=false]
>>> Local node addresses: [VM-W2K8-50-168.englab. brocade.com/0:0:0:0:0:0:0:1, 
>>> VM-W2K8-50-168.englab.brocade. com/10.24.50.168, 
>>> VM-W2K8-50-168.englab.brocade. com/127.0.0.1, /192.168.56.1, 
>>> /2620:100:0:fe07:2c72:f331: 9245:123d]
>>> Local ports: TCP:11211 TCP:47100 UDP:47400 TCP:47500
May 26, 2017 1:00:36 AM org.apache.ignite.logger.java. JavaLogger info
INFO: Topology snapshot [ver=100, servers=1, clients=0, CPUs=4, heap=3.6GB]
2017-05-26 01:00:36.760  INFO 14176 --- [   main] o.s.b.f.xml. 
XmlBeanDefinitionReader  : Loading XML bean definitions from file 
[C:\Users\Administrator\ config\default-config.xml]
2017-05-26 01:00:36.762  WARN 14176 --- [   main] o.m.caches.ignite. 
IgniteCacheAdapter : Initializing the default cache. Consider properly 
configuring 'config/default-config.xml' instead.
May 26, 2017 1:00:36 AM org.apache.ignite.logger.java. JavaLogger info
INFO: Started cache [name=com.brocade.dcm.domain. mapper.PostsMapper, 
memoryPolicyName=null, mode=PARTITIONED]

 

Regards,
Muthu

-- The latest fact in modern technology isn't that machines will begin to think 
like people, but that people will begin to think like machines.
-- Nothing exists except atoms and empty space, everything else is opinion - 
Democritus
On Thu, May 25, 2017 at 2:33 AM, Roman Shtykh [via Apache Ignite Users] 
<[hidden email]> wrote:

 
If you move you config/default-config.xml to have it under server/ (I am 
talking only about Intellij IDEA here), it will pick up your file. Otherwise, 
the default configuration will be used.
-- Roman


On Thursday, May 25, 2017 5:51 PM, Muthu <[hidden email]> wrote:
 

 
Okay one thing i have confirmed again now (i am running a windows vm) for 
mybatis-ignite if i do not download ignite (apache-ignite-fabric-2.0.0-bi n), 
set IGNITE_HOME to the downloaded location & copy my default-config.xml to the 
config directory of the IGNITE_HOME the ignite configuration in that file is 
never read..below is the console log for it where i have marked some lines with 
a marker (??--) to highlight the same...i also see this 
stated as a requirement in the code for mybatis ignite cache adapter..see 
http://www.mybatis.org/ignite- cache/jacoco/org.mybatis.cache 
s.ignite/IgniteCacheAdapter. java.html. Are you sure in your case it picked up 
the default-config.xml or did it just start ignite with defaults just like the 
below.


[01:30:20] (wrn) Failed to resolve IGNITE_HOME automatically for class codebase 
[class=class o.a.i.i.util.IgniteUtils, e=URI is not hierarchical]
??--[01:30 :20] (wrn) Default Spring XML file not found (is 
IGNITE_HOME set?): config/default-config.xml ??--
2017-05-25 01:30:20.921 ERROR 12204 --- [   main]   
    : Failed to resolve default logging config file: 
config/java.util.logging.prope rties
Console logging handler is not configured.
2017-05-25 01:30:22.048  INFO 12204 --- [   main] 
org.apache.ignite.internal.Ign iteKernal  :

>>>    __  
>>>   /  _/ ___/ |/ /  _/_  __/ __/
>>>  _/ // (7 7    // /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/
>>>
>>> ver. 2.0.0#20170430-sha1:d4eef3c6
>>> 2017 Copyright(C) Apache Software Foundation
>>>
>>> Ignite documentation: http://ignite.apache.org

2017-05-25 01:30:22.049  INFO 12204 --- [   main] 
org.apache.ignite.internal.Ign iteKernal  : Config URL: n/a
2017-05-25 01:30:22.049  INFO 12204 --- [   main] 
org.apache.ignite.internal.Ign

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

sorcmd.{sh|bat}
2017-05-25 01:30:28.275  INFO 12204 --- [   main] 
org.apache.ignite.internal.IgniteKernal  :
2017-05-25 01:30:28.279  INFO 12204 --- [   main] 
org.apache.ignite.internal.IgniteKernal  :

>>> +--+
>>> Ignite ver. 2.0.0#20170430-sha1:d4eef3c68ff116ee34bc13648cd82c640b3ea072
>>> +--+
>>> OS name: Windows Server 2008 R2 6.1 amd64
>>> CPU(s): 4
>>> Heap: 3.6GB
>>> VM name: 12204@VM-W2K8-50-168
??-->>> Local node 
[ID=0EA5FC00-C34E-417D-8FCE-0615F9EEC00B, order=94, clientMode=false] 
??--
>>> Local node addresses: [VM-W2K8-50-168.englab.brocade.com/0:0:0:0:0:0:0:1, 
>>> VM-W2K8-50-168.englab.brocade.com/10.24.50.168, 
>>> VM-W2K8-50-168.englab.brocade.com/127.0.0.1, /192.168.56.1, 
>>> /2620:100:0:fe07:2c72:f331:9245:123d]
>>> Local ports: TCP:11211 TCP:47100 UDP:47400 TCP:47500

2017-05-25 01:30:28.296  INFO 12204 --- [   main] 
o.a.i.i.m.d.GridDiscoveryManager : Topology snapshot [ver=94, 
servers=1, clients=0, CPUs=4, heap=3.6GB]
2017-05-25 01:30:28.313  INFO 12204 --- [   main] 
o.s.b.f.xml.XmlBeanDefinitionReader  : Loading XML bean definitions from 
file [C:\Users\Administrator\Documents\Work\server\config\default-config.xml]
??--2017-05-25 01:30:28.315  WARN 12204 --- [   
main] o.m.caches.ignite.IgniteCacheAdapter : Initializing the default 
cache. Consider properly configuring 'config/default-config.xml' instead. 
??--
??????--2017-05-25 01:30:28.466  INFO 12204 --- 
[orker-#30%null%] o.a.i.i.p.cache.GridCacheProcessor   : Started cache 
[name=com.brocade.dcm.domain.mapper.PostsMapper, memoryPolicyName=null, 
mode=PARTITIONED] ??--

Regards,
Muthu

On Thu, May 25, 2017 at 12:58 AM, Roman Shtykh  wrote:

I didn't download and start any other node -- one server node is started 
according to your configuration (default-config.xml) when you use MyBatis 
caching. So it was only one node.If you have an Ignite cluster and want your 
new node (you start for L2 cache), please make sure that your L2 cache have 
identical configuration.
No warnings, just a normal Ignite start.
-- Roman




On Thursday, May 25, 2017 3:57 PM, mlekshma  
wrote:
 

 
Hmm...so its something in my environment then?also couple of
questions..did you have to first download ignite & setup IGNITE_HOME env
variable? Also did you first start ignite from the command line by placing
the default-config.xml from the project (under config dir of server project)
in the IGNITE_HOME config dir? Do you see mybatis ignite cache adapter
picking up the configuration from it?...or do you see something like this in
the logs "Initializing the default cache. Consider properly configuring
'config/default-config.xml' instead."and when the objects are cached are
they being part of the configured grid?



--
View this message in context: http://apache-ignite-users. 
70518.x6.nabble.com/MyBatis- Ignite-L2-cache-Integration- 
does-not-work-with-Ignite-2-0- tp13126p13137.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   



   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

I didn't download and start any other node -- one server node is started 
according to your configuration (default-config.xml) when you use MyBatis 
caching. So it was only one node.If you have an Ignite cluster and want your 
new node (you start for L2 cache), please make sure that your L2 cache have 
identical configuration.
No warnings, just a normal Ignite start.
-- Roman




On Thursday, May 25, 2017 3:57 PM, mlekshma  
wrote:
 

 
Hmm...so its something in my environment then?also couple of
questions..did you have to first download ignite & setup IGNITE_HOME env
variable? Also did you first start ignite from the command line by placing
the default-config.xml from the project (under config dir of server project)
in the IGNITE_HOME config dir? Do you see mybatis ignite cache adapter
picking up the configuration from it?...or do you see something like this in
the logs "Initializing the default cache. Consider properly configuring
'config/default-config.xml' instead."and when the objects are cached are
they being part of the configured grid?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126p13137.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

Muthu,
Ok, I used your code, created the table in mysql for posts and inserted one 
line.
On accessing http://localhost:8080/dcm/posts?id=123 what I have in console

 in ObjectCacheService.getPostById  for id : 123
 in ObjectCacheService.getPostById  for searchQuery : 
 in ObjectCacheService.getPostById  returning : 
[com.brocade.dcm.domain.model.Posts@982ecc4]

and the data for the post is correctly displayed in the browser.I also checked 
if Ignite cache is called. No hanging.
-- Roman


On Thursday, May 25, 2017 2:40 PM, Roman Shtykh  wrote:
 

 Muthu,
It would be great to have a much smaller project with detailed steps on how to 
reproduce it.Also, will it hang when you change the cache to the default L2 
cache ()?
-- Roman


On Thursday, May 25, 2017 2:24 PM, mlekshma  
wrote:
 

 Hi Roman,

Thanks for the pointer to the dependencies i will take a re-look at it. The
application starts finebut the db get call never returns. For example if
you try using the single rest point (/dcm/posts?id=1) to make a db get it
will never return...that's the problem.





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126p13134.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

Muthu,
It would be great to have a much smaller project with detailed steps on how to 
reproduce it.Also, will it hang when you change the cache to the default L2 
cache ()?
-- Roman


On Thursday, May 25, 2017 2:24 PM, mlekshma  
wrote:
 

 Hi Roman,

Thanks for the pointer to the dependencies i will take a re-look at it. The
application starts finebut the db get call never returns. For example if
you try using the single rest point (/dcm/posts?id=1) to make a db get it
will never return...that's the problem.





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126p13134.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

Muthu,
I could successfully start your application in IntelliJ IDEA via 
ObjectCacheApplication#main -- Spring and Ignite are started, no errors. I 
haven't populated the db though.
I also re-checked mybatis-ignite on a simpler project - it works as expected.

>From your error log, it looks like you have to fix your dependencies.
-- Roman


On Thursday, May 25, 2017 12:27 PM, mlekshma  
wrote:
 

 Sure Roman..thanks for the response. Here is the git repo,
https://github.com/softwarebrahma/MyBatis-Ignite-L2-cache-POC

I have placed all the info there...please let me know if you need any quick
info.

Thanks
Muthu



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126p13128.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

Muthu, thank you! I will have a look!
Roman


On Thursday, May 25, 2017 12:27 PM, mlekshma  
wrote:
 

 Sure Roman..thanks for the response. Here is the git repo,
https://github.com/softwarebrahma/MyBatis-Ignite-L2-cache-POC

I have placed all the info there...please let me know if you need any quick
info.

Thanks
Muthu



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126p13128.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: MyBatis Ignite L2 cache Integration does not work with Ignite 2.0

[Roman Shtykh]

Hi,
Can you please share a piece of code that reproduces this (on github, for 
instance)? I can have a look.
-- Roman




On Thursday, May 25, 2017 10:48 AM, mlekshma  
wrote:
 

 Following the steps mentioned at mybatis-ignite integration page @
mybatis-ignite with Ignite 2.0, i see that the call to the mapper hangs &
never returns. This is after working around several other issues like
requiring ignite-cache configuration to be placed in
IGNITE_HOME/config/default-config.xml which still doesn't get picked up
unless i place it in a physical location in the project dir (otherwise i see
the error in the log "Initializing the default cache. Consider properly
configuring 'config/default-config.xml' instead.") which again also seems to
have no effect.

Since the integration seems to have several issues i am not sure if it is
still supported..any thoughts from any one who has successfully done this or
from the mybatis-ignite team would be great.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: Issue in starting IgniteSinkConnector with Distributed Worker mode

[Roman Shtykh]

The connector is not created and no connection to your Ignite cluster is done 
in a distributed mode, if you pass connector configuration on the command 
line.In a distributed mode, you have to use REST API, like below.
$ curl -X POST -H "Content-Type: application/json" --data '{"name": 
"string-ignite-connector", "config": 
{"connector.class":"org.apache.ignite.stream.kafka.connect.IgniteSinkConnector",
 
"tasks.max":"2","topics":"test","cacheName":"cache1","igniteCfg":"path_to_/ignite.xml"}}'
 http://localhost:8083/connectors

Hope this helps.
Roman

On Tuesday, March 14, 2017 4:45 PM, dkarachentsev 
 wrote:
 

 Hi,

Could you please attach logs and thread dumps (in case of hang) if problem
is still relevant?

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Issue-in-starting-IgniteSinkConnector-with-Distributed-Worker-mode-tp10647p11161.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

[Roman Shtykh]

MyBatis Ignite cache is updated. The new version is 
1.0.4.http://www.mybatis.org/ignite-cache/

Best regards,Roman


On Wednesday, March 8, 2017 4:50 AM, Denis Magda  wrote:
 

 Andrey,
Excellent! Thanks for keeping an eye on this. Please let us know what you do 
the same for Zeppelin.
*Raul*, *Roman*, could you update Camel and MyBatis integrations 
respectively?https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations
—Denis

On Mar 7, 2017, at 11:47 AM, Andrey Gura  wrote:
JFYI

Also today Vert.x 3.4.0 was released with Apache Ignite 1.9 based
cluster manager for Vert.x in HA/Clustered mode.

On Tue, Mar 7, 2017 at 3:10 AM, Denis Magda  wrote:

The Apache Ignite Community is pleased to announce the release of Apache Ignite 
1.9.0.

Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
distributed in-memory platform for computing and transacting on large-scale 
data sets in real-time, orders of magnitude faster than possible with 
traditional disk-based or flash-based technologies.

The Fabric is a collection of independent and well integrated components some 
of which are the following:
Data Grid
SQL Grid
Compute Grid
Streaming & CEP
Service Grid


In this release the community provided an integration with Kubernetes cluster 
manager, improved performance of core and SQL Grid components, expanded Data 
Modification Language support to the level of .NET and C++ API, integrated with 
.NET TransactionScope API and more.

Learn more details from our blog post: 
https://blogs.apache.org/ignite/entry/apache-ignite-1-9-released

The full list of the changes can be found here [2].

Please visit this page if you’re ready to try the release out:
https://ignite.apache.org/download.cgi

Please let us know [3] if you encounter any problems.

Regards,

The Apache Ignite Community

[1] https://ignite.apache.org
[2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
[3] https://ignite.apache.org/community/resources.html#ask





   

Re: Flink Streamer

[Roman Shtykh]

Hi,
Can you check your logs and see if "Ignition.start(igniteCfgFile)" line of the 
Holder [1] starts the grid without failures?

[1] 
https://github.com/apache/ignite/blob/master/modules/flink/src/main/java/org/apache/ignite/sink/flink/IgniteSink.java
-Roman
 

On Thursday, February 16, 2017 7:16 PM, dkarachentsev 
 wrote:
 

 Hi,

I'm not quite familiar with Flink and Kafka connectors, but I'm going to
figure them out and come back to help you.

Thanks!

-Dmitry.



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


   

Re: Python Client for Apache Ignite

[Roman Shtykh]

Hi Piali,
If you have just to store/retrieve keys/values, you might consider Python Redis 
client. Currently supported commands are listed here [1].
[1] http://apacheignite.gridgain.org/docs/redis


Roman
 

On Friday, December 16, 2016 10:16 AM, piali  
wrote:
 

 Hi,

I would like to know if there is python client for Apache Ignite.
If not then can you please let us know if there is any plan for that in
future releases.

Regard,
Piali



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


   

Re: Kafka - Failed to stream a record with null key

[Roman Shtykh]

I will add the functionality to transform Kafka values. Please follow it on 
Jira.
-Roman
 

On Wednesday, November 9, 2016 8:27 PM, vdpyatkov  
wrote:
 

 Hi,

In my view, you try to do something strange. You have got exception at
compile time, how are you want assign new reference onto return value?

Please, create a ticket on Ignite Jira[1], as Roman said.

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



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-tp8731p8824.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: Kafka - Failed to stream a record with null key

[Roman Shtykh]

Hi Austin,
FileStreamSourceTask [1] does not parse file lines and insert them into Kafka 
with null keys (and does not have the properties you mentioned).

To use connectors in your case, I see two ways, and both require code 
modifications:1. Create your own FileStreamSourceTask (or propose a 
modification to Kafka community)2. Create a Jira issue for Ignite (and possibly 
contribute) to have a functionality to extract keys from values (file lines in 
your case).
[1] 
https://github.com/confluentinc/kafka/blob/trunk/connect/file/src/main/java/org/apache/kafka/connect/file/FileStreamSourceTask.java
[2] https://issues.apache.org/jira/browse/IGNITE
- Roman

 

On Tuesday, November 8, 2016 3:47 PM, austin solomon 
 wrote:
 

 Hi Roman,

Is it possible to give the configuration properties parse.key=true &
key.separator=, in producer, because when I start the
FileStreamSourceConnector I could see the following values 

INFO ProducerConfig values: 
    acks = all
    batch.size = 16384
    block.on.buffer.full = false
    bootstrap.servers = [localhost:9092]
    buffer.memory = 33554432
    client.id = producer-4
    compression.type = none
    connections.max.idle.ms = 54
    interceptor.classes = null
    key.serializer = class
org.apache.kafka.common.serialization.ByteArraySerializer
    linger.ms = 0
    max.block.ms = 9223372036854775807
    max.in.flight.requests.per.connection = 1
    max.request.size = 1048576
    metadata.fetch.timeout.ms = 6
    metadata.max.age.ms = 30
    metric.reporters = []
    metrics.num.samples = 2
    metrics.sample.window.ms = 3
    partitioner.class = class
org.apache.kafka.clients.producer.internals.DefaultPartitioner
    receive.buffer.bytes = 32768
    reconnect.backoff.ms = 50
    request.timeout.ms = 2147483647
    retries = 2147483647
    retry.backoff.ms = 100
    sasl.kerberos.kinit.cmd = /usr/bin/kinit
    sasl.kerberos.min.time.before.relogin = 6
    sasl.kerberos.service.name = null
    sasl.kerberos.ticket.renew.jitter = 0.05
    sasl.kerberos.ticket.renew.window.factor = 0.8
    sasl.mechanism = GSSAPI
    security.protocol = PLAINTEXT
    send.buffer.bytes = 131072
    ssl.cipher.suites = null
    ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
    ssl.endpoint.identification.algorithm = null
    ssl.key.password = null
    ssl.keymanager.algorithm = SunX509
    ssl.keystore.location = null
    ssl.keystore.password = null
    ssl.keystore.type = JKS
    ssl.protocol = TLS
    ssl.provider = null
    ssl.secure.random.implementation = null
    ssl.trustmanager.algorithm = PKIX
    ssl.truststore.location = null
    ssl.truststore.password = null
    ssl.truststore.type = JKS
    timeout.ms = 3
    value.serializer = class
org.apache.kafka.common.serialization.ByteArraySerializer

Thanks,
Austin




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-tp8731p8766.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: Kafka - Failed to stream a record with null key

[Roman Shtykh]

Hi Austin,
Sorry, I don't quite understand your problem. The key is what you specify as 
the key in your ProducerRecord when you put your data into Kafka (you can see 
it from IgniteSinkConnectorTest).What is your key and value? Is your key null 
and you try to create a key from value before streaming the data into Ignite?
-Roman
 

On Tuesday, November 8, 2016 1:50 PM, austin solomon 
 wrote:
 

 Hi Roman,

Thanks for your reply.

Can you please tell me how to put values to record key.

Regards,
Austin




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-tp8731p8761.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: Kafka - Failed to stream a record with null key

[Roman Shtykh]

Hi Austin,
The record key is null and it cannot be submitted to Ignite. Please make sure 
your key is not null.
Btw, "parse.key" and "key.separator" are ConsoleProducer's properties, not 
Worker's.

-Roman
 

On Monday, November 7, 2016 10:26 PM, austin solomon 
 wrote:
 

 Hi,

I am using Kafka Streamer module to pump the data from Kafka to Ignite
cache, by following the documentation given in the below link

https://apacheignite.readme.io/docs/kafka-streamer

I could able to sink the data in ignite's cache. However when i tried to
achieve the same Confluent I got the following error

ERROR Failed to stream a record with null key!
(org.apache.ignite.stream.kafka.connect.IgniteSinkTask:98)

@SuppressWarnings("unchecked")
    @Override public void put(Collection records) {
        try {
            for (SinkRecord record : records) {
                if (record.key() != null) {
                    // Data is flushed asynchronously when
CACHE_PER_NODE_DATA_SIZE is reached.
                    StreamerContext.getStreamer().addData(record.key(),
record.value());
                }
                else {
                    log.error("Failed to stream a record with null key!");
                }

            }
        }
        catch (ConnectException e) {
            log.error("Failed adding record", e);

            throw new ConnectException(e);
        }
    }

After some analysis I found that this problem might be occurred since I have
not provided  the properties like 
--property parse.key=true --property key.separator=,

My question here is, Is it possible to pass this properties in kafka's
worker configuration file like connect.standalone ?

Thanks in advance !!
Austin

  




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-tp8731.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


   

Re: Ignite - How to check if ignite instance has already started

[Roman Shtykh]

Hi,
How about using Ignition.getOrStart(...)?
-Roman
 

On Tuesday, September 27, 2016 10:44 AM, M Singh  
wrote:
 

 Hi Folks:
I am using Ignition.start() and if Ignite has already been started, it shows an 
IgniteException indicating that the default grid has already been started:
org.apache.ignite.IgniteCheckedException: Default Ignite instance has already 
been started.
Is there a way to check if Ignite has already been started so that I can skip 
this call ? If not, is there a specific exception that can indicate the same ?
Thanks

   

Re: mybatis-ignite

[Roman Shtykh]

Hi all,
The issue with starting an Ignite instance is fixed with mybatis-ignite 1.0.2 
release.
-Roman
 

On Tuesday, July 19, 2016 6:26 AM, vkulichenko 
 wrote:
 

 Hi,

First of all, please properly subscribe to the mailing list so that the
community can receive email notifications for you messages. Here is the
instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1

As for the issue, looks like IgniteCacheAdapter provided by mybatis always
starts the Ignite instance, which is not really good. But in your case you
can simply remove Ignite's ServletContextListenerStartup and let
IgniteCacheAdapter do its job.

Let me know if this helps.

-Val



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


   

Re: Kafka Listener and Computing

[Roman Shtykh]

Hi Venkat,
I am not sure what kind of processing you want to do, but for getting data from 
Kafka topics and injecting to Ignite cluster, please see 
http://apacheignite.gridgain.org/v1.7/docs/kafka-streamerOnce you have data in 
the cache, you can do your compute part.
-Roman

 

On Wednesday, August 10, 2016 9:13 AM, vmuthus  wrote:
 

 
 We are trying t find a write platofrm to do realtime data processing in
memory.
Need few suggestions.

Our Data is cached in the grid. for our request I need the listener part of
the same Ignite Grid listening to a Kafka topic and process the message and
compute certain task.
How do I do it.

I do not want to update the cache just od the computation for every kafka
message and spit the output to another queue. Also I want the same Grid will
do the computation without creating client node/process.

Any help is appreciated.

Thanks
Venkat




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Listener-and-Computing-tp6891.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


  

Re: Unexpexted exception

[Roman Shtykh]

Hi,
Your Externalizable StringWrapper does not have a default constructor and is 
not saved.
Please enable logging to see the error messages.
-Roman
 

On Friday, May 13, 2016 8:36 PM, kajzur  wrote:
 

 Hi, 
thanks for response. This is link for git repository -
https://gitlab.com/kajzur/temp.git - repository has no access restrictions,
so every one can clone it. 

My config is in first mail :)

Thanks!



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


  

Re: Unexpexted exception

[Roman Shtykh]

Hi,
Do you have an MRE on github or elsewhere I can reproduce it?
-Roman
 

On Thursday, May 12, 2016 3:23 AM, kajzur  wrote:
 

 Hi, 
thank, now it's working, but now I have other problem. 

All is working but my session isn't saved. I have HttpSession object and in
one servler setting an attr and in other servler I trying to get this attr
and it's not there. I checked in debugger - my session is WebSession from
ingniter. 

Have you got, maybe, aby idea, why it's not working?

I have four servers:
[18:13:58,879][INFO][disco-event-worker-#44%null%][GridDiscoveryManager]
Topology snapshot [ver=148, servers=4, clients=0, CPUs=6, heap=4.7GB]




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


   

Re: Unexpexted exception

[Roman Shtykh]

I think you have to1. Have  with your 
CacheConfiguration inside IgniteConfiguration in your default-config.xml2. Have 
 in your default-config.xml 
and specify the grid name with IgniteWebSessionsGridName at web.xml
-Roman 

Re: Unexpexted exception

[Roman Shtykh]

It is possible to see the full log? As the error message says, grid is not 
started.
-Roman
 

On Wednesday, May 11, 2016 12:14 AM, kajzur  wrote:
 

 Hi!
Thanks for response, but is still the same error :(



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


   

Re: jpoint presentation

[Roman Shtykh]

Yakov,
I would like to see it too.
-Roman
 

On Tuesday, May 10, 2016 3:56 PM, Yakov Zhdanov  
wrote:
 

 Nick, I am not sure if apache lists allow attachments. So, I will send you 
personal email.

Thanks!--
Yakov Zhdanov, Director R&D
GridGain Systems
www.gridgain.com
2016-05-05 13:52 GMT+06:00 Nick Pavlov :

Hi Yakov,

Could you share your presentation from jpoint?



   

Re: Unexpexted exception

[Roman Shtykh]

How about adding
to CacheConfiguration in your default-config.xml?
-Roman
 

On Tuesday, May 10, 2016 3:13 AM, kajzur  wrote:
 

 Hi!
I'm trying to setup a "Web Session Clustering" in Tomcat 7. I followed by
http://apacheignite.gridgain.org/v1.5/docs/web-session-clustering with
replicated cacheMode. And I'm getting an exception:


And this is my web.xml:


and my default-config.xml:


And ofcourse my pom.xml:


I will be very grateful if some one could help me with it :)

Best regards!



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


  

CacheLoadOnlyStoreAdapter's use example for cache preloading

[Roman Shtykh]

CacheLoadOnlyStoreAdapter's use example was added and can be found in 
examples/src/main/java/org/apache/ignite/examples/datagrid/store/.

It illustrates how one can pre-load a cache from text or file of any other 
format.
-Roman

Re: MyBatis-Ignite integration release

[Roman Shtykh]

Dear community,
GA release of MyBatis integration release is done now.http://blog.mybatis.org/

-Roman

  On Thursday, February 11, 2016 9:15 PM, Roman Shtykh 
 wrote:
 Dmitriy,
Let's see if we have some feedback from users (that is mostly the intention I 
share here too). After that I'll call for a vote among MyBatis devs and they 
will help with the release.
-Roman



  

Re: Exception during streams processing

[Roman Shtykh]

btw, do you have the same issues on starting a basic Ignite setup (without 
stream processing)?

Can you share your /etc/hosts and the server log with more details 
(particularly "TcpDiscoveryNode" parts)?

With this information, I think you can get some more advice.


-Roman





On Monday, February 22, 2016 12:03 AM, Roman Shtykh  wrote:
Hi Saurabh,

As a quick fix, will setting "-Djava.net.preferIPv4Stack=true" help?

-Roman





On Sunday, February 21, 2016 10:50 PM, Saurabh Sharma  
wrote:




Hi,

I am reading streams from Kafka topic (using ConsumerConnector with a thread 
count 4). I observed that stream processing is very slow and sometimes I am 
getting following exception. Could you please let me know what could be the 
reason of this slow processing.

I am trying to read a log file with a record count of 200K.

SEVERE: Failed to request nodes addresses.
java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound 
to any interface
at 
java.net.TwoStacksPlainDatagramSocketImpl.socketSetOption(Native Method)
at 
java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:309)
at 
java.net.MulticastSocket.setInterface(MulticastSocket.java:467)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.requestAddresses(TcpDiscoveryMulticastIpFinder.java:544)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.access$700(TcpDiscoveryMulticastIpFinder.java:80)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder$AddressReceiver.body(TcpDiscoveryMulticastIpFinder.java:755)
at 
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)


Thanks

Re: Exception during streams processing

[Roman Shtykh]

Hi Saurabh,

As a quick fix, will setting "-Djava.net.preferIPv4Stack=true" help?

-Roman




On Sunday, February 21, 2016 10:50 PM, Saurabh Sharma  
wrote:




Hi,
 
I am reading streams from Kafka topic (using ConsumerConnector with a thread 
count 4). I observed that stream processing is very slow and sometimes I am 
getting following exception. Could you please let me know what could be the 
reason of this slow processing.
 
I am trying to read a log file with a record count of 200K.
 
SEVERE: Failed to request nodes addresses.
java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound 
to any interface
at 
java.net.TwoStacksPlainDatagramSocketImpl.socketSetOption(Native Method)
at 
java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:309)
at 
java.net.MulticastSocket.setInterface(MulticastSocket.java:467)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.requestAddresses(TcpDiscoveryMulticastIpFinder.java:544)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.access$700(TcpDiscoveryMulticastIpFinder.java:80)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder$AddressReceiver.body(TcpDiscoveryMulticastIpFinder.java:755)
at 
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
 
 
Thanks

Re: MyBatis-Ignite integration release

[Roman Shtykh]

Dmitriy,
Let's see if we have some feedback from users (that is mostly the intention I 
share here too). After that I'll call for a vote among MyBatis devs and they 
will help with the release.
-Roman
 

On Thursday, February 11, 2016 5:39 PM, Dmitriy Setrakyan 
 wrote:
 

 Thanks Roman, this is awesome news! 
Do you know what is the process at MyBatis to move from beta into a final GA 
release?
D.
On Wed, Feb 10, 2016 at 11:41 PM, Roman Shtykh  wrote:

Dear community,

I would like to share the news about MyBatis-Ignite integration release, as a 
result of the collaboration between Ignite and MyBatis teams.

http://blog.mybatis.org/2016/02/mybatis-ignite-released.html

>From now please consider using Apache Ignite as your 2nd level MaBatis cache.

Best regards,
Roman




  

MyBatis-Ignite integration release

[Roman Shtykh]

Dear community,

I would like to share the news about MyBatis-Ignite integration release, as a 
result of the collaboration between Ignite and MyBatis teams.

http://blog.mybatis.org/2016/02/mybatis-ignite-released.html

>From now please consider using Apache Ignite as your 2nd level MaBatis cache.

Best regards,
Roman

Re: Issue while extending out of the box classes

[Roman Shtykh]

Hi Saurabh,
This may be not an answer to your question, but from the bean id I guess you 
try to implement a Kafka streamer.Please check if [1] will work for you.
[1] 
https://ignite.apache.org/releases/1.5.0.final/javadoc/org/apache/ignite/stream/kafka/KafkaStreamer.html
-Roman