Re: failureDetectionTimeout tuning
We will try this and get back to you. Does it mean that usually the node recovers from it, if it were due to GC? Would we also have to remove joinTimeout? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/failureDetectionTimeout-tuning-tp7374p7473.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: IgniteCompute.broadcast() stuck
Also, it was stuck like this for hours. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteCompute-broadcast-stuck-tp7255p7472.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: IgniteCompute.broadcast() stuck
Val, this dump was from the client node which I sent on the original email. the zipped up dumps were from all the server nodes that participate in the distributed cache. anyways, changing it to run() fixed the issue. But we never understand the root cause of the hanging, its always that the alternative suggestion works. And we move on to it without understanding why what we tried first did not work. Thanks, Binti -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteCompute-broadcast-stuck-tp7255p7471.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite Cache Update(k,v)
IgniteCluster API provides startNodes() method that allows to do this programmatically on the remote machines (it uses SSH connection). Can you please give me full examples? or a link for this? thanks again -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-Update-k-v-tp7296p7470.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Yarn Ignite Container Automatically exit when other yarn application running
but from yarn contains, i can't find any errors. sometimes the yarn am ignite was shutdown down(and sometimes restart a new AM, i don't know why)? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Yarn-Ignite-Container-Automatically-exit-when-other-yarn-application-running-tp7335p7469.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Reassign partitions
Hi, We have no global DB behind the grid. We marked our Store with @CacheLocalStore annotation. But Ignite does not move stored entries when rebalancig partitions. So we should have more control of partition assignment to be able to change the assignment manually after storage synchronization. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Reassign-partitions-tp7461p7468.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Fail to compile apache-ignite-1.7.0
Hi, Your Maven tries to access a repo which is not provided by Ignite build. I guess it's somewhere in your Maven settings. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Fail-to-compile-apache-ignite-1-7-0-tp7458p7467.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Overall desgn question
Hi Scott, How many caches are you going to have? Basically, the recommended way is to have a cache per data type - this makes life easier in most cases. But keep in mind that each cache will require around 20MB of *heap* memory per node for its internals. So hundreds of caches can introduce high memory consumption and you may consider merging some caches in this case. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Overall-desgn-question-tp7459p7466.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Server and Client mode per cache
Hi, You can use CacheConfiguration.setNodeFilter(..) property to specify where the particular cache will be deployed. If not set, it will be deployed on all server nodes. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Server-and-Client-mode-per-cache-tp7460p7465.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Reassign partitions
Hi, Can you please clarify why would you need this? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Reassign-partitions-tp7461p7464.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Access cache entries in C++ via JNI call
Hi, You can try using Ignite C++ client. If you describe your use-case some more I'll be able to provide you with some more specific advice. What for are you using Ignite for and why do you need to make JNI calls? Best Regards, Igor On Thu, Sep 1, 2016 at 10:21 PM, Caio Nishibewrote: > Hi, I'm trying to implement a biometric identification system using Ignite. > The first version was not good enough because in my job, for each cache > entry, I was calling a C++ method through JNI to process that entry and the > time to transfer all the data from Java to C++ was killing the performance > of the threads. I've tried to create a C++ Client inside my Java job to run > a ScanQuery, but did not work and I discovered that I cannot create another > JVM instance inside a JNI call. Is it possible to access all the cache > entries in C++ inside a JNI call? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Access-cache-entries-in-C-via-JNI-call-tp7462.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
Access cache entries in C++ via JNI call
Hi, I'm trying to implement a biometric identification system using Ignite. The first version was not good enough because in my job, for each cache entry, I was calling a C++ method through JNI to process that entry and the time to transfer all the data from Java to C++ was killing the performance of the threads. I've tried to create a C++ Client inside my Java job to run a ScanQuery, but did not work and I discovered that I cannot create another JVM instance inside a JNI call. Is it possible to access all the cache entries in C++ inside a JNI call? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Access-cache-entries-in-C-via-JNI-call-tp7462.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Reassign partitions
The AffinityFunction.assignPartitions method is called when a server node joins or left the topology. Is there a way to reassign partitions for a cache without changing the topology (e.g. to move a backup partition from one node to another)? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Reassign-partitions-tp7461.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Server and Client mode per cache
Hi, I am trying to configure ignite that cache A data will be on all nodes and cache B data on some subset of nodes. In other words for cache A ignite will be in server mode for all nodes and for cache B ignite will in server mode for some nodes and in client mode for others. I think it could be done implementing AffinityFunction API, but I am not sure is this is a right way to do this. Is there better way to solve this issue? Thanks. -- Yitzhak Molko
Overall desgn question
We will be employing a data grid off heap, replication implementation. We are estimating with the 30% index cache alllowance that we will need 7 gig of ram per ignite server node there will be two. We have two options. Create many smaller caches or put everything in a collection using one cache. Are there any recommendations that someone might have as to the best approach? This message is intended for use only by the person(s) addressed above and may contain privileged and confidential information. Disclosure or use of this message by any other person is strictly prohibited. If this message is received in error, please notify the sender immediately and delete this message.
Fail to compile apache-ignite-1.7.0
Hi, This is first time I touch apache-ignite. When I try to comply it as by instractions from https://apacheignite.readme.io/docs/getting-started (without LGPL dependencies) I am getting following error: [INFO] ignite-jta . FAILURE [ 7.287 s] ... [ERROR] Failed to execute goal on project ignite-jta: Could not resolve dependencies for project org.apache.ignite:ignite-jta:jar:1.7.0: Failed to collect dependencies at org.ow2.jotm:jotm-core:jar:2.1.9 -> org.ow2.carol:carol:jar:3.0.6 -> org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Failed to read artifact descriptor for org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Could not transfer artifact org.jacorb:jacorb:pom:2.2.3-jonas-patch-20071018 from/to central (http://hki-repo01.comptel.com:8081/artifactory/repo/): Access denied to: http://hki-repo01.comptel.com:8081/artifactory/repo/org/jacorb/jacorb/2.2.3-jonas-patch-20071018/jacorb-2.2.3-jonas-patch-20071018.pom , ReasonPhrase:Forbidden. -> [Help 1] Did anyone else experienced this error ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Fail-to-compile-apache-ignite-1-7-0-tp7458.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Combine SQL and Text Query
Hello, If you specify type on IndexTypes property[1] SQL will be work, but without indexes. The resume field do not be visible from SQL. Text query do not work together with SQL. [1]: https://apacheignite.readme.io/docs/sql-queries#configuring-sql-indexes-by-annotations On Thu, Sep 1, 2016 at 1:43 PM, WhiteAncientwrote: > If I have the classic POJO > > class Person{ > @QuerySqlField > private String genotype; > > @QueryTextField > private String resume; > } > > How do I query "where genotype = 'male' and resume like '%Hello%'" so that > it hits the lucene index? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Combine-SQL-and-Text-Query-tp7455.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
Combine SQL and Text Query
If I have the classic POJO class Person{ @QuerySqlField private String genotype; @QueryTextField private String resume; } How do I query "where genotype = 'male' and resume like '%Hello%'" so that it hits the lucene index? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Combine-SQL-and-Text-Query-tp7455.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Stopping local node according to configured segmentation policy.
Hello, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. The reason of segmentation in most cases is a delays: like network problem, lock process on several time by operation system, GC pause or blocking traffic by firewall. Please, check the instructions and try to avoid this issues. If you have checked already, provide whole logs from all cluster nodes. scq wrote > who can help me ,one of nodes close? > logs as follows. > > [14:13:03,074][WARNING][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] > Node is out of topology (probably, due to short-time network problems). > [14:13:03,076][WARNING][disco-event-worker-#138%null%][GridDiscoveryManager] > Local node SEGMENTED: TcpDiscoveryNode > [id=3a4f760a-3b4d-4afb-98b2-56117e7ada57, addrs=[0:0:0:0:0:0:0:1%lo, > 127.0.0.1, 172.28.88.25], sockAddrs=[ed-test25/172.28.88.25:59504, > /0:0:0:0:0:0:0:1%lo:59504, /127.0.0.1:59504], discPort=59504, order=143, > intOrder=76, lastExchangeTime=1472623983071, loc=true, > ver=1.7.0#20160801-sha1:383273e3, isClient=false] > [14:13:03,088][WARNING][disco-event-worker-#138%null%][GridDiscoveryManager] > Stopping local node according to configured segmentation policy. > [14:13:03,089][WARNING][disco-event-worker-#138%null%][GridDiscoveryManager] > Node FAILED: TcpDiscoveryNode [id=adfdc6f1-0c3e-450a-92ff-dbbb6c38d7c4, > addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.28.88.25], > sockAddrs=[ed-test25/172.28.88.25:59502, /0:0:0:0:0:0:0:1%lo:59502, > /127.0.0.1:59502], discPort=59502, order=119, intOrder=62, > lastExchangeTime=1472623523722, loc=false, > ver=1.7.0#20160801-sha1:383273e3, isClient=false] > [14:13:03,090][INFO][disco-event-worker-#138%null%][GridDiscoveryManager] > Topology snapshot [ver=151, servers=1, clients=0, CPUs=24, heap=14.0GB] > [14:13:03,095][INFO][Thread-10][GridTcpRestProtocol] Command protocol > successfully stopped: TCP binary -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Stopping-local-node-according-to-configured-segmentation-policy-tp7431p7453.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: jdbc connection URL with more than 1 cache
i was wrong. i solved with cross-cache-query functions -sy -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/jdbc-connection-URL-with-more-than-1-cache-tp7446p7451.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: is there a interface let client know the change of assignment(like topology version)?
Hello, You can subscribe to event[1] and handle EVT_CACHE_REBALANCE_STARTED and EVT_CACHE_REBALANCE_STOPPED events on client node. [1]: https://apacheignite.readme.io/docs/events On Thu, Sep 1, 2016 at 5:17 AM, bluehuwrote: > for example, C is a client, X and Y are ignite server, then server Z join > in: > > topologyVersion changed immediately, and then rebalance start, a > CacheAffinityChangeMessage will sent after rebalance finished, then > assignment changed. > > is there a interface let client know the change of assignment(like topology > version)? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/is-there-a-interface-let-client-know- > the-change-of-assignment-like-topology-version-tp7444.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
Re: Can not find schema for object with compact footer
Fix version suggest it is in 1.8 which is yet to be released. Is there any interim solution meanwhile. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-not-find-schema-for-object-with-compact-footer-tp7406p7448.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: javax.cache.CacheException: Failed to find mapping description
hi Alexey, Thanks for logging the issue. But still I am facing the same issue: public class CacheConfig { /** * Create JDBC type for inventory_orders. * * @param cacheName Cache name. * @return Configured JDBC type. */ private static JdbcType jdbcTypeInventoryOrders(String cacheName) { JdbcType jdbcType = new JdbcType(); jdbcType.setCacheName(cacheName); System.out.println("cache name in jdbcType : "+cacheName); jdbcType.setDatabaseSchema("default"); jdbcType.setDatabaseTable("inventory_orders"); jdbcType.setKeyType("org.infocepts.ignite.hiveCache.InventoryOrdersKey"); jdbcType.setValueType("org.infocepts.ignite.hiveCache.InventoryOrders"); *// Key fields for inventory_orders. Collection keys = new ArrayList<>(); keys.add(new JdbcTypeField(Types.INTEGER, "ITEM_ID", Integer.class, "itemId")); jdbcType.setKeyFields(keys.toArray(new JdbcTypeField[keys.size()])); // Value fields for inventory_orders. Collection vals = new ArrayList<>(); vals.add(new JdbcTypeField(Types.INTEGER, "MONTH_ID", Integer.class, "monthId")); vals.add(new JdbcTypeField(Types.INTEGER, "ITEM_ID", Integer.class, "itemId")); vals.add(new JdbcTypeField(Types.DOUBLE, "UNITS_RECEIVED", Double.class, "unitsReceived")); vals.add(new JdbcTypeField(Types.INTEGER, "MONTH_DURATION", *Integer.class, "monthDuration")); jdbcType.setValueFields(vals.toArray(new JdbcTypeField[vals.size()])); System.out.println("JdbcType Values: "+ jdbcType.getCacheName()); return jdbcType; } /** * Create SQL Query descriptor for inventory_orders. * * @return Configured query entity. */ private static QueryEntity queryEntityInventoryOrders() { QueryEntity qryEntity = new QueryEntity(); qryEntity.setKeyType("org.infocepts.ignite.hiveCache.InventoryOrdersKey"); qryEntity.setValueType("org.infocepts.ignite.hiveCache.InventoryOrders"); // Query fields for inventory_orders. LinkedHashMapfields = new LinkedHashMap<>(); fields.put("monthId", "java.lang.Integer"); fields.put("itemId", "java.lang.Integer"); fields.put("unitsReceived", "java.lang.Double"); fields.put("monthDuration", "java.lang.Integer"); qryEntity.setFields(fields); // Aliases for fields. Map aliases = new HashMap<>(); *aliases.put("monthId", "MONTH_ID"); aliases.put("itemId", "ITEM_ID"); aliases.put("unitsReceived", "UNITS_RECEIVED"); aliases.put("monthDuration", "MONTH_DURATION");* qryEntity.setAliases(aliases); return qryEntity; } -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/javax-cache-CacheException-Failed-to-find-mapping-description-tp7350p7447.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
jdbc connection URL with more than 1 cache
hi, i'm learing and testing ignite for feasibility. during test i met the following problem. when i define jdbc connection url with 2 params (2 caches) as follows, i got errors at executeQuery. however if i defie just 1 cache, it works fine. try { Class.forName("org.apache.ignite.IgniteJdbcDriver"); //Connection conn = DriverManager.getConnection("jdbc:ignite://192.168.10.57:11211/Person"); Connection conn = DriverManager.getConnection("jdbc:ignite:cfg://cache=Person:cache=Organization@file://" + args[0]); ... java.sql.SQLException: Failed to query Ignite. at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(JdbcStatement.java:115) at org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:53) at JdbcCnt.main(JdbcCnt.java:44) ... Caused by: org.h2.jdbc.JdbcSQLException: Table "PERSON" not found; SQL statement: select count(*) from Person [42102-191] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:179) ... must i define only 1 cache for jdbc connection? or is there any way to define sevral caches? could anyone help me on this? -sy -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/jdbc-connection-URL-with-more-than-1-cache-tp7446.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.