JDBC discovery adds 127.0.0.1 to tbl_addrss causing communication failure notices

2017-08-16 Thread Yasser
I am using ignite 2.1. There are two nodes with jdbc discovery. I had the sys admins open a port 19080 for cluster communication and configured the tcpdiscoveryapi to use it. The problem I see is that the table tbl_addrs has three entries (for two nodes). The third entry is 127.0.0.1. I think due

Re: Off-Heap and Eviction policy questions

2017-08-03 Thread Yasser
Thank you! I resolved by moving the data load operation outside the server cluster. Thanks, Yasser On Thu, Aug 3, 2017 at 10:01 AM, slava.koptilin wrote: > Hi Yasser, > > Well, you are using IgniteDataStreamer in order to load data into cache. > The IgniteDataStreamer actually buf

Re: Off-Heap and Eviction policy questions

2017-08-02 Thread Yasser
("Writing key {}", entry.getKey()); jdbcTemplate.update(storeOneQuery, entry.getKey(), entry.getValue()); } public List getAllKeys() { log.info("Getting all keys to load"); return jdbcTemplate.queryForList(getAllKeysQuery, String.class); } }

Off-Heap and Eviction policy questions

2017-08-01 Thread Yasser
ject... args) { log.info("In loadcache"); jdbcTemplate.query(loadAllQuery, (rs, rownNum) -> { closure.apply(rs.getString(1), rs.getString(2)); return null; }); } } Thanks, Yasser