Re: Failed to wait for initial partition map exchange

[Jason]

No fix or workaround for this so far.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p7536.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Failed to wait for initial partition map exchange

[Ignitebie]

Jason
Scenario that you shared is same as ours and we face similar issue for large
heap servers grid where one of node in restart keeps waiting on initial
partition map exchange.

Have you received a fix or were able to hack a solution. Please share.

Thanks.




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p7535.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Not able to retrieve data from cache

[chevy]

Hi,

 I am adding data to cache in below format -

"cache.putAll(finalMap)" and cache is of format "IgniteCache cache". "finalMap" looks like "finalMap.put(storeId,
salesModel)". SalesModel structure is shown below. I am not able to get data
using any of the "rest-api" provided or JDBC api and I have confirmed that
salesModel contains data before adding. Please let me know the reason and
what can be done to fetch data.

package com.target.ignite.model.sales;

import java.io.Serializable;
import java.sql.Date;

import org.apache.ignite.cache.query.annotations.QuerySqlField;

public class SalesModel implements Serializable {

private static final long serialVersionUID = 1L;

/** SalesModel: id (not-indexed). */
@QuerySqlField
public String id;

/** SalesModel: storeId (not-indexed). */
@QuerySqlField
public int storeId;

/** SalesModel: date (not-indexed). */
@QuerySqlField
public String date;

/** TdyFeedModel: tdy (not-indexed). */
@QuerySqlField
public TdyFeedModel day;

/** YstFeedModel: yst (not-indexed). */
@QuerySqlField
public WtdFeedModel previousDay;

/** WtdFeedModel: wtd (not-indexed). */
@QuerySqlField
public WtdFeedModel weekToDate;

/** MtdFeedModel: mtd (not-indexed). */
@QuerySqlField
public MtdFeedModel monthToDate;

//setters and getters for all variables
}





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Not-able-to-retrieve-data-from-cache-tp7533.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

JVM tuning

[Caio Nishibe]

As I've mentioned  here

 
, I'm trying to use Ignite within a biometric identification system to store
fingerprint templates in memory and to use Ignite's compute grid capability
to perform matching operations, given an input fingerprint. My
identification task creates one job per cluster node and each job runs a
scan query through local cache entries performing fingerprint comparisons.
The problem is, even though I've created as many threads as cores, the cpu
only rises up to 20%. The comparison algorithm is very cpu intensive. I'm
using the jvm tunning suggested for OFF_HEAP caches. Any ideas or system
tunning hints to get to 100% cpu utilization? 



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

Note that large topology

[Ignitebie]

Hi,

We get following warning when we restart a client node trying to connect a
grid of 7 servers.

'2016-09-05 13:39:00 [WARN] [Thread=main]
[class=org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] Node has not
been connected to topology and will repeat join process. Check remote nodes
logs for possible error messages. Note that large topology may require
significant time to start. Increase 'TcpDiscoverySpi.networkTimeout'
configuration property if getting this message on the starting nodes
[networkTimeout=6]

Do we know cause for this and why it waits so long. Is there a configuration
issue that we need to look at.

thanks.



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

Re: javax.cache.CacheException: Failed to find mapping description

[Alexey Kuznetsov]

Hello @vikramT.

I prepared example that worked for me with H2 database, but it should work
with your DB also.
Take a look and try to run (I also put h2 database in zip).

demo-with-h2.zip
  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/javax-cache-CacheException-Failed-to-find-mapping-description-tp7350p7530.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: why allocated containers much more than INGNITE_NODE_COUNT?

[shirely]

well, Thanks for your advise. examples for yarn works. and I have figured it
out. It seems the ignite yarn deployment is not a good choice for windows. 

The ignite source code override the onContainersAllocated function,  and
when it tried ctx.setEnvironment(env) where env=System.getenv(); it caused
the problem.

In cmd, %=d:% has special meaning and can not be set.

Besides, the source code below can also cause errors:
ctx.setCommands(

Collections.singletonList(

(props.licencePath() != null ? "cp
gridgain-license.xml ./ignite/*/ || true && " : "")

+ "cp -r ./libs/* ./ignite/*/libs/ || true && "

+ "./ignite/*/bin/ignite.sh "

+ "./ignite-config.xml"

+ " -J-Xmx" + ((int)props.memoryPerNode()) + "m"

+ " -J-Xms" + ((int)props.memoryPerNode()) + "m"

+ IgniteYarnUtils.YARN_LOG_OUT

));





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/why-allocated-containers-much-more-than-INGNITE-NODE-COUNT-tp7226p7529.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: CacheJdbcPojoStoreExampleFactory for Maria DB

[Vasiliy Sisko]

Hello @seyeony. 

The idiomatic ways of data source usage with CacheJdbcPojoStoreFactory are
specification of data source bean name or implementation of data source
factory class.

NOTE: When you implement data source bean factory class it should be
available in classpath for every node. F.e.:

public class MyDataSourceFactory implements Factory {
@Override public DataSource create() {
JdbcDataSource dataSource = new JdbcDataSource();
dataSource.setURL("jdbc:...");
dataSource.setUser("username");
dataSource.setPassword("password");
return dataSource;
}
}
…
CacheJdbcPojoStoreFactory storeFactoryJdbcPojo = new
CacheJdbcPojoStoreFactory();

storeFactoryJdbcPojo.setDataSourceFactory(new MyDataSourceFactory());
…
NOTE: When you specify data source bean name bean with that name should be
described in spring configuration for every node. F.e:
   







...




…




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