date:20200220

Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"

2020-02-20 Thread Taras Ledkov


Hi,

Ignite uses H2 version 1.4.197 (see [1]).


[1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74

On 20.02.2020 4:36, Andrew Munn wrote:
I'm building/running my client app w/Gradle and I'm seeing this 
error.  Am I overloading the Ingite H2 fork with the real H2 or 
something?  It appears I have the latest h2:


[.gradle]$ find ./ -name *h2*
./caches/modules-2/metadata-2.82/descriptors/com.h2database
./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
./caches/modules-2/files-2.1/com.h2database
./caches/modules-2/files-2.1/com.h2database/h2
./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar



2020-02-19 19:59:28.229 ERROR 102356 --- [           main] 
o.a.i.internal.IgniteKernal%dev-cluster  : Exception during start 
processors, node will be stopped and close connections
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed 
to initialize system DB connection: 
jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
        at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434) 
~[ignite-indexing-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699) 
~[ignite-indexing-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646) 
~[ignite-indexing-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257) 
~[ignite-indexing-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700) 
~[ignite-core-2.7.6.jar:2.7.6]
        at org.apache.ignite.Ignition.start(Ignition.java:348) 
~[ignite-core-2.7.6.jar:2.7.6]
        at 
com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14) 
~[main/:na]
Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: 
Unsupported connection setting "MULTI_THREADED" [90113-200]
        at 
org.h2.message.DbException.getJdbcSQLException(DbException.java:622) 
~[h2-1.4.200.jar:1.4.200]


--
Taras Ledkov
Mail-To: tled...@gridgain.com

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

2020-02-20 Thread Ilya Kasnacheev

Hello!

For example, you can do a SQL request with large result set, such as SELECT
* without WHERE clause, which may cause server node to run out of memory.

Regards,
-- 
Ilya Kasnacheev


чт, 20 февр. 2020 г. в 06:23, wentat :

> Hi Ilya,
>
> Thank you for your response. I have checked my client side load testing
> library (I am using YCSB btw) and I found a potential memory leak. However,
> can the client side using too much heap cause the server to fail? There is
> no other applications running on the Apache Ignite servers
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Serialisation issue.

2020-02-20 Thread Ilya Kasnacheev

Hello!

I, for one, do not recommend using new Collection() {{ }} in your 
configurations.

It will create a non-static anonymous class, which may bind arbitrary amount of 
symbols from current lexical content, which will then need to be serialized to 
be sent to other nodes.

Please use other ways to create pre-populated collections, such as Commons 
Collect.

Regards,

On 2020/02/07 12:16:23, adipro  wrote: 
> cache = ignite.getOrCreateCache(new CacheConfiguration<>()
> .setName("DOCIDS")
> .setStoreKeepBinary(true)
> .setQueryEntities(Collections.unmodifiableList(new
> ArrayList(){{
> QueryEntity entity = new QueryEntity();
> entity.setKeyType(String.class.getName());
> entity.setValueType(DOCIDS_CLASS.class.getName());
> entity.setFields(new
> LinkedHashMap(){{
> put("docid",Long.class.getName());
> put("url",String.class.getName());
> }});
> entity.setIndexes(Collections.unmodifiableList(new
> ArrayList(){{
> add(new QueryIndex("docid"));
> }}));
> add(entity);
> }}))
> .setCacheMode(CacheMode.REPLICATED));
> 
> When executing the above statements, we are getting below exception:
> 
> 
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> serialize object: CacheConfiguration [name=DOCIDS, grpName=null,
> memPlcName=null, storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1,
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null,
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0,
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null,
> writeSync=null, storeFactory=null, storeKeepBinary=true, loadPrevVal=false,
> aff=null, cacheMode=REPLICATED, atomicityMode=null, backups=0,
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC,
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2,
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false,
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000,
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512,
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null,
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null,
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true,
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true,
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false,
> encryptionEnabled=false]
>   at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal0(JdkMarshaller.java:102)
>   at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:69)
>   at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal0(JdkMarshaller.java:116)
>   at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:57)
>   at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10131)
>   at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$11.applyx(GridCacheProcessor.java:5419)
>   ... 19 more
> Caused by: java.io.NotSerializableException:
> org.apache.ignite.configuration.IgniteConfiguration
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
>   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at
> java.io.ObjectO

Re: Ignite yarn resources keep on increasing

2020-02-20 Thread Ilya Kasnacheev

Hello!

I still have trouble understanding where does your problem lie, in Ignite
terms (as opposed to Yarn or ZooKeeper terms).

Why did your negative scenario fail? What is the difference in procedure
used?

Regards,
-- 
Ilya Kasnacheev


чт, 20 февр. 2020 г. в 08:37, ChandanS :

> Hi Ilya,
>
> Yes, I start the ignite in client mode and my other applications access
> this
> ignite cluster. I use to start the ignite cluster with 40-executors -and
> 2-cores. Usually, in success scenario my starting ignite and data loading
> finish within 5/6 minutes. The logs are for negative scenario, while my
> jobs
> are running for long time  and I have killed the long running job.
>
> Below config xml I have used for ignite:
>
> http://www.springframework.org/schema/beans";
>xmlns:util="http://www.springframework.org/schema/util";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>
> classpath:/org/springframework/beans/factory/xml/spring-beans-4.3.xsd">
>
>
>   
>   
>   
>
>   
>   class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> 
> 
>  
>   
>
>   
>   class="org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi">
>  value="x.int.westgroup.com:2181,x.int.westgroup.com:2181,
> x.int.westgroup.com:2181"/>
> 
>  value="/apacheIgnite-titan-resourceUP"/>
>  
>   
>
>   
>   class="org.apache.ignite.configuration.ClientConnectorConfiguration">
> 
> 
>  
>   
>
>   
>   class="org.apache.ignite.configuration.TransactionConfiguration">
>  value="6"/>
>  
>   
>
> 
>
>
> Thanks,
> Chandan
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Issue with signed SSL CERT.

2020-02-20 Thread Ilya Kasnacheev

Hello!

Can you please show me how it looks from your web browser? Please note that
you will need a proper HTTPS certificate for correct domain for this to
work.

Regards,
-- 
Ilya Kasnacheev


чт, 20 февр. 2020 г. в 00:31, npopov :

> Hi all.
> Having issue with installing SSL certificate with Jetty configuration:
>
>
> cache.xml snippet:
>
>
> jetty-ssl.xml snipppet:
>
>
> Apparently the certificate loads correctly, but the browser complains about
> "your connection is not private" and NET::ERR_CERT_COMMON_NAME_INVALID.
>
> The certificate is issued to *host-name-IGN02* and it has the same name as
> CN value.
> Certification path have all the certs to the Root CA.
>
> Any help or hint is appreciated.
>
> Regards,
> -Nick
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Loading cache from Oracle Table

2020-02-20 Thread Ilya Kasnacheev

Hello!

20 minutes for 40 mln entries seems in reasonable ballpark to me. What's
the CPU usage on Ignite nodes at that time?

Regards,
-- 
Ilya Kasnacheev


ср, 19 февр. 2020 г. в 19:43, Prasad Bhalerao :

> Hi,
> I am using partition aware loading to load big tables using 4-8 threads on
> each nodes.
> I have around 16 caches. 2 caches have 38-40 million entries. It takes
> around approx 21 minutes to load the caches on 6 nodes.
> I have kept the backup count to 2.
>
> Will share the code tomorrow.
>
> Regards,
> Prasad
>
>
> On Tue 18 Feb, 2020, 6:08 PM nithin91 <
> nithinbharadwaj.govindar...@franklintempleton.com wrote:
>
>> Hi Prasad,
>>
>> Is there a improvement in performance. If so can you please share the
>> sample
>> code as i am also looking for a similar solution.
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

REST API requests hang with no response

2020-02-20 Thread Devin Anderson


Hi all,

I'm seeing issues wherein the Apache Ignite REST API appears to accept 
requests, but doesn't ever reply.  This doesn't always happen; for example, if 
I make a request that I expect the API to reject, I get back a response:


--

# curl -v -X GET 'http://127.0.0.1:8080/ignite'
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /ignite HTTP/1.1
> User-Agent: curl/7.35.0
> Host: 127.0.0.1:8080
> Accept: */*
>
< HTTP/1.1 400 Bad Request
< Date: Thu, 20 Feb 2020 11:21:22 GMT
< Content-Type: application/json;charset=utf-8
< Content-Length: 0
* Server Jetty(9.4.11.v20180605) is not blacklisted
< Server: Jetty(9.4.11.v20180605)
<
* Connection #0 to host 127.0.0.1 left intact

--

I expect the (above) request above to fail because I don't supply the required 
`cmd` parameter.


However, if I make a request that I believe should succeed, I never receive a 
response:


--

# curl -v 'http://127.0.0.1:8080/ignite?cmd=version'
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /ignite?cmd=version HTTP/1.1
> User-Agent: curl/7.35.0
> Host: 127.0.0.1:8080
> Accept: */*
>

--

`curl` will wait forever for a response that never arrives.

I tried looking for logs output by the REST API so that I could debug the 
issue, but failed to find any log entries emitted from the REST API.


Given that I'm new to Apache Ignite, I suspect that I'm almost certainly doing 
something wrong, but I have absolutely no idea what that could be.


I have a few questions:

1.) Has anyone encountered an issue similar to this with the REST API?  If so, 
how did you solve it?

2.) Can anyone tell me where I might find REST API log entries?
3.) I have persistence enabled in the XML configuration.  Would that conflict 
with the REST API?
4.) I have additional nodes (3 nodes in total) in the XML configuration.  
AFAICT from log entries and some liberal use of `ss`, the nodes are 
communicating with each other.  Would having multiple nodes conflict with the 
REST API?
5.) Is there anything else I'm missing that might not be obvious to me because 
I'm new to Apache Ignite?


Other than (3) and (4), I think the configuration file I'm using is rather 
bland:

--

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

    
  
    
    
  
    
    
    
    
  
    
  
    

    
  
    
  
    
  
    [other node address][other node 
address]

  
    
  
    
  
    

  


--

(Obviously, each instance of '[other node address]' is substituted with a real 
IP address in the actual files I'm using.)


Thanks in advance for any help.

--
Devin

Re: REST API requests hang with no response

2020-02-20 Thread Ilya Kasnacheev

Hello!

Please collect thread dump (jstack) from affected node, share it with us.

Regards,
-- 
Ilya Kasnacheev


чт, 20 февр. 2020 г. в 16:17, Devin Anderson :

> Hi all,
>
> I'm seeing issues wherein the Apache Ignite REST API appears to accept
> requests, but doesn't ever reply.  This doesn't always happen; for
> example, if
> I make a request that I expect the API to reject, I get back a response:
>
> --
>
> # curl -v -X GET 'http://127.0.0.1:8080/ignite'
> * Hostname was NOT found in DNS cache
> *   Trying 127.0.0.1...
> * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
>  > GET /ignite HTTP/1.1
>  > User-Agent: curl/7.35.0
>  > Host: 127.0.0.1:8080
>  > Accept: */*
>  >
> < HTTP/1.1 400 Bad Request
> < Date: Thu, 20 Feb 2020 11:21:22 GMT
> < Content-Type: application/json;charset=utf-8
> < Content-Length: 0
> * Server Jetty(9.4.11.v20180605) is not blacklisted
> < Server: Jetty(9.4.11.v20180605)
> <
> * Connection #0 to host 127.0.0.1 left intact
>
> --
>
> I expect the (above) request above to fail because I don't supply the
> required
> `cmd` parameter.
>
> However, if I make a request that I believe should succeed, I never
> receive a
> response:
>
> --
>
> # curl -v 'http://127.0.0.1:8080/ignite?cmd=version'
> * Hostname was NOT found in DNS cache
> *   Trying 127.0.0.1...
> * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
>  > GET /ignite?cmd=version HTTP/1.1
>  > User-Agent: curl/7.35.0
>  > Host: 127.0.0.1:8080
>  > Accept: */*
>  >
>
> --
>
> `curl` will wait forever for a response that never arrives.
>
> I tried looking for logs output by the REST API so that I could debug the
> issue, but failed to find any log entries emitted from the REST API.
>
> Given that I'm new to Apache Ignite, I suspect that I'm almost certainly
> doing
> something wrong, but I have absolutely no idea what that could be.
>
> I have a few questions:
>
> 1.) Has anyone encountered an issue similar to this with the REST API?  If
> so,
> how did you solve it?
> 2.) Can anyone tell me where I might find REST API log entries?
> 3.) I have persistence enabled in the XML configuration.  Would that
> conflict
> with the REST API?
> 4.) I have additional nodes (3 nodes in total) in the XML configuration.
> AFAICT from log entries and some liberal use of `ss`, the nodes are
> communicating with each other.  Would having multiple nodes conflict with
> the
> REST API?
> 5.) Is there anything else I'm missing that might not be obvious to me
> because
> I'm new to Apache Ignite?
>
> Other than (3) and (4), I think the configuration file I'm using is rather
> bland:
>
> --
>
> http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="
>  http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd";>
>
>
>  
> class="org.apache.ignite.configuration.DataStorageConfiguration">
>  
>  
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>  
>  
>  
>  
>
>  
>
>  
>
>  
>
>  
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>  
>
>  [other node address][other node
> address]
>
>  
>
>  
>
>  
>
>
> 
>
> --
>
> (Obviously, each instance of '[other node address]' is substituted with a
> real
> IP address in the actual files I'm using.)
>
> Thanks in advance for any help.
>
> --
> Devin
>
>

Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"

2020-02-20 Thread Andrew Munn

Thanks.  Adding this runtime dependency to build.gradle fixed it:

dependencies {
runtime("com.h2database:h2:1.4.197")
...
compile group: 'org.apache.ignite', name: 'ignite-spring', version:
'2.7.6'
compile group: 'org.apache.ignite', name: 'ignite-core', version:
'2.7.6'
}

But I suspect this should be getting enforced automatically if using h2
ver1.4.200 breaks something.  Am I specifying the Ignite dependency
incorrectly?


On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov  wrote:

> Hi,
>
> Ignite uses H2 version 1.4.197 (see [1]).
>
>
> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>
> On 20.02.2020 4:36, Andrew Munn wrote:
> > I'm building/running my client app w/Gradle and I'm seeing this
> > error.  Am I overloading the Ingite H2 fork with the real H2 or
> > something?  It appears I have the latest h2:
> >
> > [.gradle]$ find ./ -name *h2*
> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
> > ./caches/modules-2/files-2.1/com.h2database
> > ./caches/modules-2/files-2.1/com.h2database/h2
> >
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
> >
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
> >
> >
> >
> > 2020-02-19 19:59:28.229 ERROR 102356 --- [   main]
> > o.a.i.internal.IgniteKernal%dev-cluster  : Exception during start
> > processors, node will be stopped and close connections
> > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> > to initialize system DB connection:
> >
> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at org.apache.ignite.Ignition.start(Ignition.java:348)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
> > ~[main/:na]
> > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
> > Unsupported connection setting "MULTI_THREADED" [90113-200]
> > at
> > org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
> > ~[h2-1.4.200.jar:1.4.200]
>
> --
> Taras Ledkov
> Mail-To: tled...@gridgain.com
>
>

How to configure primary data in memory and backup data on disk?

2020-02-20 Thread joseheitor

How do I configure Primary data in RAM and backup copies to disk?

The goal is to store backup copies on disk, leaving max RAM available for
primary partitions only.



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

Re: Offheap memory consumption + enabled persistence

2020-02-20 Thread ezhuravlev

>But I am still confused. Did I understood properly that each node should 
have enough memory to store full data set? 
No, it's not the case. It's just preallocating this memory with internal
structures and shows it in the metrics.



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

Re: tailing Ignite cache for events?

2020-02-20 Thread Evgenii Zhuravlev

No, it's not possible to do in Visor. You can use a client node to start
this Continuous Query. For this purpose you can also register listeners for
events: https://apacheignite.readme.io/docs/events. It can be done for one
of the Lifecycle events.

Evgenii

ср, 19 февр. 2020 г. в 17:40, Andrew Munn :

> Can you easily register a continuous query using Visor or something?  I
> would like to see all cache activity including the before and after
> toString() representation of objects being modified.  I just want to
> eyeball it during development, not pipe it into another application etc
>
> On Wed, Feb 19, 2020 at 6:03 PM Evgenii Zhuravlev <
> e.zhuravlev...@gmail.com> wrote:
>
>> Hi,
>>
>> Usually it's Continuous Queries:
>> https://www.gridgain.com/docs/latest/developers-guide/key-value-api/continuous-queries,
>> but it depends on your use case. What do you want to do with these events?
>>
>> Best Regards,
>> Evgenii
>>
>> ср, 19 февр. 2020 г. в 14:54, Andrew Munn :
>>
>>> What's the best way to watch a cache for insert/update/delete events?
>>>
>>

Getting error while extracting Date Fields from ignite cache using node express

2020-02-20 Thread nithin91

Hi,

We have an Oracle Table for which a corresponding cache/table is created in
ignite and loaded using Cache JDBC POJO Store. On top of this cache a Rest
API is built  using node express.

We are fetching the data from the cache using sql fields query and the
programming language used is node js. We are able to fetch all the fields
except the Date Fields and when we are trying to fetch the date fields we
are getting the following *error *after execution of the statement const
data=await  cursorProductDetails.getAll();


*Error: Type type code -2 is not supported*

Java Data type for this Field is java.sql.Date


In if i cast the date field as varchar in sql fields query this error is not
encountered.Even i didnt encounter this error when i am fetching the data
using Java and Python.Can anyone please let me know how to resolve this
issue without doing a cast as varchar and also the reason on why i am
getting this error while using node express alone.



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

Re: Data Load from Oracle to Ignite is very slow

2020-02-20 Thread nithin91

Hi 

When i executed on the server , Data is getting loaded very fast.Thanks for
the inputs.

With respect to Data Steamer, it would be really helpful if you can share
any sample code other than the one provided in documentation.



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

Re: How to configure primary data in memory and backup data on disk?

2020-02-20 Thread Mikhail

You can not do this, Apache Ignite even can use the same memory page to store
primary records and backup records, however, don't worry, Ignite will keep
in memory the most recently used memory pages:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-Random-2-LRU

Thanks,
Mike.



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

Re: REST API requests hang with no response

2020-02-20 Thread Devin Anderson

Hi Ilya,

I'm attaching the `jstack` dump to this message.  When I took the dump, there 
were ten requests that had been made to the Apache Ignite REST API using POST 
data of the form:

    cmd=add&key=[key]&value=[value]

... where [key] and [value] were proper URI encoded data.

Thanks in advance for any help.  I'll take a look as well and try to figure out 
what's going on.

Devin

On 2/20/20 5:43 AM, Ilya Kasnacheev wrote:

Hello!

Please collect thread dump (jstack) from affected node, share it with us.

Regards,
--
Ilya Kasnacheev

чт, 20 февр. 2020 г. в 16:17, Devin Anderson >:

Hi all,

I'm seeing issues wherein the Apache Ignite REST API appears to accept
requests, but doesn't ever reply.  This doesn't always happen; for
example, if
I make a request that I expect the API to reject, I get back a response:

--

# curl -v -X GET 'http://127.0.0.1:8080/ignite

'
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
 > GET /ignite HTTP/1.1
 > User-Agent: curl/7.35.0
 > Host: 127.0.0.1:8080

 > Accept: */*
 >
< HTTP/1.1 400 Bad Request
< Date: Thu, 20 Feb 2020 11:21:22 GMT
< Content-Type: application/json;charset=utf-8
< Content-Length: 0
* Server Jetty(9.4.11.v20180605) is not blacklisted
< Server: Jetty(9.4.11.v20180605)
<
* Connection #0 to host 127.0.0.1 left intact

--

I expect the (above) request above to fail because I don't supply the
required
`cmd` parameter.

However, if I make a request that I believe should succeed, I never
receive a
response:

--

# curl -v 'http://127.0.0.1:8080/ignite?cmd=version

'
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
 > GET /ignite?cmd=version HTTP/1.1
 > User-Agent: curl/7.35.0
 > Host: 127.0.0.1:8080

 > Accept: */*
 >

--

`curl` will wait forever for a response that never arrives.

I tried looking for logs output by the REST API so that I could debug the
issue, but failed to find any log entries emitted from the REST API.

Given that I'm new to Apache Ignite, I suspect that I'm almost certainly
doing
something wrong, but I have absolutely no idea what that could be.

I have a few questions:

1.) Has anyone encountered an issue similar to this with the REST API? 
If so,
how did you solve it?
2.) Can anyone tell me where I might find REST API log entries?
3.) I have persistence enabled in the XML configuration. Would that conflict
with the REST API?
4.) I have additional nodes (3 nodes in total) in the XML configuration.
AFAICT from log entries and some liberal use of `ss`, the nodes are
communicating with each other.  Would having multiple nodes conflict with
the
REST API?
5.) Is there anything else I'm missing that might not be obvious to me
because
I'm new to Apache Ignite?

Other than (3) and (4), I think the configuration file I'm using is
rather bland:

--

http://www.springframework.org/schema/beans

"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance

"
    xsi:schemaLocation="
http://www.springframework.org/schema/beans

Connection reset by peer

2020-02-20 Thread hulitao198758

^-- System thread pool [active=0, idle=6, qSize=0]
[16:57:36,455][SEVERE][grid-nio-worker-tcp-comm-3-#50%SubScriptionCluster%][TcpCommunicationSpi]
Failed to process selector key [ses=GridSelectorNioSessionImpl
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=3,
bytesRcvd=4878431, bytesSent=2691434, bytesRcvd0=0, bytesSent0=0,
select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-3,
igniteInstanceName=SubScriptionCluster, finished=false, hashCode=1064068859,
interrupted=false,
runner=grid-nio-worker-tcp-comm-3-#50%SubScriptionCluster%]]],
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
inRecovery=GridNioRecoveryDescriptor [acked=1316, resendCnt=0, rcvCnt=1426,
sentCnt=1316, reserved=true, lastAck=1426, nodeLeft=false,
node=TcpDiscoveryNode [id=f019bbc8-7c8e-469c-ae4b-a89b19afbbed,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.16.7.19],
sockAddrs=[/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /172.16.7.19:0], discPort=0,
order=40, intOrder=24, lastExchangeTime=1581909203338, loc=false,
ver=2.6.0#20180710-sha1:669feacc, isClient=true], connected=true,
connectCnt=0, queueLimit=4096, reserveCnt=3, pairedConnections=false],
outRecovery=GridNioRecoveryDescriptor [acked=1316, resendCnt=0, rcvCnt=1426,
sentCnt=1316, reserved=true, lastAck=1426, nodeLeft=false,
node=TcpDiscoveryNode [id=f019bbc8-7c8e-469c-ae4b-a89b19afbbed,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.16.7.19],
sockAddrs=[/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /172.16.7.19:0], discPort=0,
order=40, intOrder=24, lastExchangeTime=1581909203338, loc=false,
ver=2.6.0#20180710-sha1:669feacc, isClient=true], connected=true,
connectCnt=0, queueLimit=4096, reserveCnt=3, pairedConnections=false],
super=GridNioSessionImpl [locAddr=/10.122.64.127:48339,
rmtAddr=/10.122.23.172:57818, createTime=1581971404618, closeTime=0,
bytesSent=1128312, bytesRcvd=849644, bytesSent0=0, bytesRcvd0=0,
sndSchedTime=1582217852002, lastSndTime=1582196198388,
lastRcvTime=1582217852002, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@6b3aff0d, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true]]]
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1250)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2339)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2110)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
[16:57:36,457][WARNING][grid-nio-worker-tcp-comm-3-#50%SubScriptionCluster%][TcpCommunicationSpi]
Closing NIO session because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Connection reset by peer]


The ignite server is 3 nodes. It is deployed on the server as a database to
use and enable persistence. The client node is deployed in a k8s container.
This error occurs after running for a while. Why?





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

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

2020-02-20 Thread wentat

Hi Ilya, 

at the time of running the experiments in the logs, there was no queries
running in the background. Just 30 servers and no clients. What could have
caused such high heap usage?




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

Re: Connection reset by peer

2020-02-20 Thread hulitao198758

Detailed error message：

Established outgoing communication connection [locAddr=/10.122.64.129:40870,
rmtAddr=/10.122.64.128:48339]
[01:01:59,775][SEVERE][grid-nio-worker-tcp-comm-1-#48%SubScriptionCluster%][TcpCommunicationSpi]
Failed to process selector key [ses=GridSelectorNioSessionImpl
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=1,
bytesRcvd=1151627, bytesSent=2289496, bytesRcvd0=64, bytesSent0=537,
select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-1,
igniteInstanceName=SubScriptionCluster, finished=false, hashCode=440471613,
interrupted=false,
runner=grid-nio-worker-tcp-comm-1-#48%SubScriptionCluster%]]],
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
inRecovery=GridNioRecoveryDescriptor [acked=2651, resendCnt=0, rcvCnt=2752,
sentCnt=2652, reserved=true, lastAck=2752, nodeLeft=false,
node=TcpDiscoveryNode [id=09e38b03-ea63-47bf-a27b-661a0f0ab8d8,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.16.99.27],
sockAddrs=[/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /172.16.99.27:0],
discPort=0, order=44, intOrder=26, lastExchangeTime=1581939704719,
loc=false, ver=2.6.0#20180710-sha1:669feacc, isClient=true], connected=true,
connectCnt=0, queueLimit=4096, reserveCnt=225, pairedConnections=false],
outRecovery=GridNioRecoveryDescriptor [acked=2651, resendCnt=0, rcvCnt=2752,
sentCnt=2652, reserved=true, lastAck=2752, nodeLeft=false,
node=TcpDiscoveryNode [id=09e38b03-ea63-47bf-a27b-661a0f0ab8d8,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.16.99.27],
sockAddrs=[/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /172.16.99.27:0],
discPort=0, order=44, intOrder=26, lastExchangeTime=1581939704719,
loc=false, ver=2.6.0#20180710-sha1:669feacc, isClient=true], connected=true,
connectCnt=0, queueLimit=4096, reserveCnt=225, pairedConnections=false],
super=GridNioSessionImpl [locAddr=/10.122.64.129:48339,
rmtAddr=/10.122.23.179:33052, createTime=1582183927690, closeTime=0,
bytesSent=33096, bytesRcvd=29254, bytesSent0=211, bytesRcvd0=0,
sndSchedTime=1582246566604, lastSndTime=1582246918763,
lastRcvTime=1582246566604, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@7419c93, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true]]]
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1250)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2339)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2110)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
[01:01:59,776][WARNING][grid-nio-worker-tcp-comm-1-#48%SubScriptionCluster%][TcpCommunicationSpi]
Closing NIO session because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Connection reset by peer]
[01:02:14,897][WARNING][tcp-comm-worker-#1%SubScriptionCluster%][TcpCommunicationSpi]
Connect timed out (consider increasing 'failureDetectionTimeout'
configuration property) [addr=/172.16.99.27:47100,
failureDetectionTimeout=10]
[01:02:14,898][WARNING][tcp-comm-worker-#1%SubScriptionCluster%][TcpCommunicationSpi]
Connect timed out (consider increasing 'failureDetectionTimeout'
configuration property) [addr=/0:0:0:0:0:0:0:1%lo:47100,
failureDetectionTimeout=10]
[01:02:14,898][WARNING][tcp-comm-worker-#1%SubScriptionCluster%][TcpCommunicationSpi]
Connect timed out (consider increasing 'failureDetectionTimeout'
configuration property) [addr=/127.0.0.1:47100,
failureDetectionTimeout=10]

[01:02:14,898][WARNING][tcp-comm-worker-#1%SubScriptionCluster%][TcpCommunicationSpi]
Failed to connect to a remote node (make sure that destination node is alive
and operating system firewall is disabled on local and remote hosts)
[addrs=[/172.16.99.27:47100, /0:0:0:0:0:0:0:1%lo:47100, /127.0.0.1:47100]]
[01:02:14,899][INFO][tcp-comm-worker-#1%SubScriptionCluster%][TcpDiscoverySpi]
Pinging node: 09e38b03-ea63-47bf-a27b-661a0f0ab8d8
[01:02:14,917][INFO][tcp-comm-worker-#1%SubScriptionCluster%][TcpDiscoverySpi]
Finished node ping [nodeId=09e38b03-ea63-47bf-a27b-661a0f0ab8d8, res=true,
time=19ms]
[01:02:14,985][WARNING][grid-timeout-worker-#45%SubScriptionCluster%][G] >>>
Possible starvation in striped pool.
Thread name: sys-stripe-3-#4%SubScrip

How to access IGFS file written one node from other node in cluster ??

2020-02-20 Thread Preeti Nidgunde

 I have written IGFS java application. I want to write shared file such that
if I write file from one node then it is accessible to all other node in
cluster. How to do that ?? 
I referred stack overflow and configured discovery spi to shared file system
but then also it is not working. The program written is accessible to only
the node who written that file not to other node (Other terminal). 
When I tried to read by giving IGFS path to the file then I received
IGFS file not found exception. Where IGFS store this file. 


public class FileExample
{
public static void main(String[] args) throws Exception
{
Ignite ignite =
Ignition.start("/root/apache-ignite-fabric-2.6.0-bin/examples/config/filesystem/example-igfs.xml");


System.out.println("\n");
System.out.println("IGFS example started.");

IgniteFileSystem fs = ignite.fileSystem("myFileSystem");
IgfsPath dir = new
IgfsPath("myFileSystem://192.168.1.5:9060/Preeti");
fs.mkdirs(dir);

IgfsPath file = new IgfsPath(dir, "myFile.txt");

System.out.println(fs.info(file));


try (OutputStream out = fs.create(file, true))
{
OutputStreamWriter outputStreamWriter = new
OutputStreamWriter(out);
outputStreamWriter.write("This is Apache ignite file
system example  Preeri Nidgunde ..Veriats Infoscale  VXVM");
System.out.println("Done .");
outputStreamWriter.close();
}catch(Exception e){}


try (InputStream in = fs.open(file))
 {
Reader inputStreamReader = new
InputStreamReader(in);
int data = inputStreamReader.read();
while(data != -1)
{
 char theChar = (char) data;
System.out.print(theChar);
 data = inputStreamReader.read();
}

inputStreamReader.close();
}catch(Exception e){}

System.out.println("Read data from file");
}
}

On other node I am trying to read file like

public class ReadFile
{
public static void main(String[] args) throws Exception
{
Ignite ignite =
Ignition.start("/root/apache-ignite-fabric-2.6.0-bin/examples/config/filesystem/example-igfs.xml");

System.out.println("\n");
System.out.println("IGFS Read example started.");

IgniteFileSystem fs = ignite.fileSystem("myFileSystem");

try (InputStream in = fs.open(new
IgfsPath("myFileSystem://192.168.1.5:9060/Preeti/myFile.txt")))
 {
Reader inputStreamReader = new
InputStreamReader(in);
int data = inputStreamReader.read();
while(data != -1)
{
 char theChar = (char) data;
System.out.print(theChar);
 data = inputStreamReader.read();
}

inputStreamReader.close();
}catch(Exception e){e.printStackTrace();}

System.out.println("Read data from file");
}
}
But it is not working.

I have written file on one node and I want to access that written file from
other node. 

Please help me.



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

Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Re: Serialisation issue.

Re: Ignite yarn resources keep on increasing

Re: Issue with signed SSL CERT.

Re: Loading cache from Oracle Table

REST API requests hang with no response

Re: REST API requests hang with no response

Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"

How to configure primary data in memory and backup data on disk?

Re: Offheap memory consumption + enabled persistence

Re: tailing Ignite cache for events?

Getting error while extracting Date Fields from ignite cache using node express

Re: Data Load from Oracle to Ignite is very slow

Re: How to configure primary data in memory and backup data on disk?

Re: REST API requests hang with no response

Connection reset by peer

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Re: Connection reset by peer

How to access IGFS file written one node from other node in cluster ??

20 matches

Site Navigation

Mail list logo

Footer information