Re: BinaryInvalidTypeException: Requesting mapping from grid failed for error reading cache

Joan, If persistence is not used then remove/move your work dir completely and restart. Check that your classpath doesn't contain duplicate classes for the same type. These might be in separate jars w/the same package and name, but be different inside. Take a look at

Re: BinaryInvalidTypeException: Requesting mapping from grid failed for error reading cache

Hi, The error is coming from here: https://github.com/apache/ignite/blob/9c2ba403fae5079201e9df6bc7b7eea5bacdf4c0/modules/core/src/main/java/org/apache/ignite/internal/MarshallerContextImpl.java#L386 This means that the model class metadata is missing/corrupt. It is located in

Re: Data synchronization after node restart

The case you are referring to is a baseline node being offline for a period of time. Like I mentioned before, once this node comes back online it will undergo historical rebalancing to catch on data it missed. like you said, idle_verify is a tool used to determine if there are inconsistencies

Re: kafka-connect and apache-ignite

The Ignite servers should be set in the discovery section. 127.0.0.1:49500..49520 see: https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery The

Re: kafka-connect and apache-ignite

Hi, You do not need to run the sink connector and ignite cluster on the same node. The igniteCfg property points to the connector's ignite configuration file. https://ignite.apache.org/docs/latest/extensions-and-integrations/streaming/kafka-streamer (see step 3) Use the discovery

Re: when persistence enabled,MaxDirectMemorySize = walSegmentSize * 4

Hi, Make sure that -XX:+DisableExplicitGC is not used to avoid facing https://bugs.openjdk.java.net/browse/JDK-8142537. Also use -XX:-HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=.. to take a heap dump and see where memory is being consumed. see:

Re: slow drop table

Hi, You need to examine the logs to see where the delay is. Check that you have enough memory, and that the system is not thrashing (constantly going to disk to retrieve data). Look into Garbage Collector logs to get more insight into your app performance. see:

Re: Data synchronization after node restart

Hi, You are referring to a persistent node failing while being a part of a baseline topology. When that same node comes back, it will load only the delta(differential per your definition) from the time that it was down. This is called historical rebalancing. Read more here:

Re: ignite 2.10 index type change

Hi, The only way to change the type of an existing field in a type is to destroy all caches that contains this type, remove the associated metadata and recreate the aforementioned caches w/the new type. You can remove an index.bin file and Ignite will rebuild it w/whatever is in the associated

Re: Ignite Client crashes JVM while Connecting to cluster

Hi, Make sure you are using the java.net.preferIPv4Stack property on the server side as well. Check your firewall config, to make sure that all listed ports are open. The issue is w/the communication SPI which, by default is using 47100 and up port range see:

Re: Long transaction suspended

I would also recommend taking a thread dump to see where this suspension is coming from. Attach this thread dump here along w/the reproducer. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Long transaction suspended

Hi, Make sure that your code is not suspending these transactions under high load conditions. https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/transactions/Transaction.html#suspend-- See this guide: https://ignite.apache.org/docs/latest/key-value-api/transactions Try

Re: Ignite cluster issue

Hi, It looks like one node did not see each other. You need to make sure that discovery is correctly set up. See: https://ignite.apache.org/docs/latest/clustering/clustering https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery Thanks, Alex -- Sent from:

Re: Ignite Startup Warnings

Hi, These are legacy warnings that could be ignored. The are coming because of this code:

Re: Query System Views Ignite 2.9.1

Hi, You can use any of your caches to perform the query, or alternatively create a new one like so: ignite.getOrCreateCache("MY_TEST_CACHE").query(new SqlFieldsQuery("SELECT * FROM SYS.NODES")).getAll() Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: rebalancing and jobs

Hi, You can monitor rebalance programmatically using JMX, https://ignite.apache.org/docs/latest/monitoring-metrics/metrics#monitoring-rebalancing or events: https://ignite.apache.org/docs/latest/events/events#cache-rebalancing-events and have your app react accordingly. You can set

Re: cpu usage is %10 while running query on ignite

Hi, QueryParallelism only help in certain specific instances(queries with table scans and aggregations). Described more here: https://ignite.apache.org/docs/latest/SQL/sql-tuning#query-parallelism The best way to speed up your query is to add appropriate indexes, and if you are using a

Re: [2.9.1]in SYS.METRICS View some data is always 0

Hi, there is not a view called metrics, only node_metrics, see below Here are the docs for those views: https://ignite.apache.org/docs/latest/monitoring-metrics/system-views Looks like you might be referring to an SQL view, in which case there is a realtime one which will only show values when

Re: Slow cache loading with an object key using affinity key

Hi, Can you actually see what the data distribution of itemid is. AffinityKey will direct Ignite to use that specific column (itemid) for partition mapping. If the data in itemid is in a narrow range, then all data will be put into fewer partitions. This might affect loading times.

Re: Slow cache loading with an object key using affinity key

Hi, Can you give more context regarding your data load. How big is your cluster?* Are the load times comparable if you use only one node for both use cases? * If you remove the affinity column in the second use case, does the load speed up in a cluster env? If you lower the amount

Re: Join between replicated and partitioned caches

Hi, What matters is how the data is finally distributed after all affinity keys (or lack thereof)are taken into account. If you are joining using an affinity key column then it is called a collocated join as each set of data can be fully retrieved from a single node, then added together. If you

Re: rebalancing and jobs

Hi, You can monitor using JMX as described here: https://ignite.apache.org/docs/latest/monitoring-metrics/metrics#monitoring-rebalancing you can also visually monitor rebalance via a special widget in control center:

Re: SqlFieldsQuery With Variable Number of Arguments

Hi, Take a look at this example: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/sql/SqlQueriesExample.java Use this as a template: String sql = "select * from Person where salary > ? and salary <= ?"; // Execute queries for

Re: C#/.NET: Possible to assign different nodes different roles?

Hi, You could use node filters: https://ignite.apache.org/docs/latest/services/services#node-filter example of node filter: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java In general, it is

Re: ThinClient issues

Hi, use: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setConsistentId-java.io.Serializable- to set the consistent id. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ThinClient issues

Hi, The connection parameters are set by the thin client connector. see: https://ignite.apache.org/docs/latest/thin-clients/getting-started-with-thin-clients#configuring-thin-client-connector all attributes are listed here:

Re: expiry policy

Hi, Expiry policies are designed to set the lifetime of an entry. If you configure your data region to have a small max size, and load more data than the max size of the data region, then most of your entries will be kept in persistent storage. After configuring your data region, set your

Re: KafkaStreamer, how to manage (stop consumming, resume) on client disconnection

flush() guarantees completion of all futures returned by addData(Object, Object) https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html#flush-- flush() will send the batch, but it is still possible for the server to crash before the message reaches it. If you

Re: KafkaStreamer, how to manage (stop consumming, resume) on client disconnection

Hi, I think listening to events would be a good solution for you. There are two discovery events that are triggered on the client node when it is disconnected from or reconnected to the cluster: EVT_CLIENT_NODE_DISCONNECTED EVT_CLIENT_NODE_RECONNECTED see:

Re: KafkaStreamer, how to manage (stop consumming, resume) on client disconnection

Hi, You can use disconnect events/exception, and then use KafkaStreamer.stop. see: https://ignite.apache.org/docs/latest/clustering/connect-client-nodes#client-disconnectedreconnected-events https://ignite.apache.org/docs/latest/clustering/connect-client-nodes Here look for: While a

Re: tcp-disco-msg-worker system-critical error

Hi, This might be due a network error or a GC pause. Use this guide to collect GC logs and look for long gc pauses: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/troubleshooting#detailed-gc-logs [threadName=tcp-comm-worker, *blockedFor=110s]*

Re: Server created remotely, C# client not able to connect to cluster with IP address

Follow the example here: https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/examples/Apache.Ignite.Examples/ThinClient/ThinClientPutGetExample.cs if you are running your server on host ABC then set the cfg as var cfg = new IgniteClientConfiguration("ABC"); see:

Re: Server created remotely, C# client not able to connect to cluster with IP address

To see that an IP is reachable from the client node, try using telnet from the client host. In your case the port should be 10800 and the IP is the one you are starting the server from. The discovery section tells Ignite where to find other nodes needed to form a cluster. If there is a node on

Re: Server created remotely, C# client not able to connect to cluster with IP address

message: because connected host has failed to respond. 171.159.66.12:10800 Ignite would need to be started on 171.159.66.12 in this case. The discovery section in tells the server where to find other nodes. see : https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery Check

Re: Server created remotely, C# client not able to connect to cluster with IP address

Hi, Looks like you either did not set the discovery section correctly, there is a network issue preventing the C# thin client from connecting, or the server itself has not started or is not responding. message: because connected host has failed to respond. 171.159.66.12:10800 Make sure

Re: Connecting to RDBMS - Failed to instantiate Spring XML application context

Hi, If you look at the message, on the very bottom it tells you: Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.jdbc2.optional.MysqlDataSource This means that the class in question is not on the classpath of the Java VM. Add the relevant library to the classpath and it

Re: client hangs forever trying to join the cluster (ClientImp joinLatch.await())

The latch not being notified is a bit odd. If this happens regularly, send the steps to reproduce. It might be network related. See if you could monitor the network to determine whether all hosts have continual access to each other. If you see gaps, adjust failureDetectionTimeout (or other

Re: client hangs forever trying to join the cluster (ClientImp joinLatch.await())

Hi, It does look like nework issues. You might want to adjust network timeout to fit your use case: https://ignite.apache.org/docs/latest/clustering/network-configuration#connection-timeouts The main setting is IgniteConfiguration.failureDetectionTimeout more useful details here:

Re: Question about baseline topology and cluster activation

Hi, What I forgot is to put in a check if the cluster is already activated and do not do activation. If you don't activate the first time then the cluster will remain in an inactive state and will not process requests to store/read data:

Re: Issue while starting the Ignite node in wildfly server

Hi, Looks like an error w/the classpath, IgniteUtils is in the same mode as the Ignition class therefore this looks like the igntie-core was not loaded correctly. Ignite 2.7 is an old version. I would try to simplify the scenario by loading the latest Ignite version

Re: Client App Object Allocation Rate

Hi, There is no documentation per se which states whether/how many objects are allocated in memory as this varies as new builds/versions are released. That being said, you can control the load/throughput/memory/enabled feature set/etc.., and therefore manage object allocation

Re: "Node with same ID" error

Hi, You might be experiencing the following scenario: 1. Node tried to connect to the cluster 2. Node is is added to the cluster 3. During the join process the node is timed out due to network issues (the default timeout is set via ackTimeout) 4. The node is dropped from the cluster 5.

Re: backup

Hi, Ignite is in the process of developing backup/snapshots capability see: https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteSnapshot.java and: https://cwiki.apache.org/confluence/display/IGNITE/IEP-43%3A+Cluster+snapshots also checkout:

Re: Ignite failing to start with linkerd?

Hi, The K8 IP finder does an equivalent of kubectl get endpoints and then tries to discover the equivalent nodes based on the results. see:

Re: Issue with serialization data security - 2.5.0

Hi, 2.5.0 is a bit outdated. I suggest you upgrade to the latest version and retry. If it is still an issue using the latest version, please include a reproducer and we will take a look. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 : Server cluster node startup issue

Veena, Ignite shouldn't be waiting for the storage spi. It first starts all its components and when an Event is ready to be recorded, the storage SPI is invoked. This scenario tests out ok. Send a reproducer and I'll take a look. Thanks, Alex -- Sent from:

Re: 2.8.1 : Server cluster node startup issue

Veena, I am not getting the same issue/thread dump when I run a similar use case. In your case it looks like Ignite has not fully started before Ignition.ignite() has been called. The check inside that function is specifically designed to prevent such cases. Here is the function you are

Re: Why does CacheBasedDataSet destroy the cache it is given

Courtney, The CacheBasedDataset.close() method below only destroys the helper cache derived from the original data, and used to train the model. It does not touch the original data set. @Override public void close() { datasetCache.destroy(); // destroy the helper cache derived from the

Re: Local node is not added in baseline topology

Hi, Please see here re baseline topology: https://apacheignite.readme.io/docs/baseline-topology The first activation is manual. You need to start as many nodes as necessary, wait until they have all initialized and are showing "cluster is inactive" in the log then issue an activation

Re: Size of Data(Keys) are doubled when using CACHE in REPLICATED mode

Hi, When all baseline nodes have joined the cluster it will self-activate. After self-activation Ignite::isActive() will return true https://ignite.apache.org/releases/latest/cppdoc/classignite_1_1Ignite.html#a5455dd6d8f8453073fbd32c60fe0c3af When isActive() returns true it means, by

Re: Ignite partitioned

Hi, As long as you see state=ACTIVE and servers=(number of nodes in your config), the cluster has been formed and is active. You can check by executing sql queries and putting data into it. If you are having issues w/your existing cluster then send the logs from all nodes on startup. Let

Re: 2.8.1 : Server cluster node startup issue

Hi, Going by the thread dump, the event api thread is holding a lock others need to proceed, while event storage thread is itself waiting for another condition to proceed. The method you are calling determined that you are not accessing ignite from the same thread that started it and is

Re: Ignite ML random forest questions

Hi, The model(s) learn a correlation between the label(s) and the features. In the Random Forest Classification example the Labeled feature represents the class that a wine belongs to based on a given set of features. see: The labeled feature is defined here:

Re: Apache Ignite with istio/envoy mTLS

Hi, At this point(2.8.1), Apache Ignite does not support Thick clients being outside of the K8 cluster. while servers being in the cluster. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 - Loading Plugin Provider - Conflicting documentation

Veena, The recommended way is to use the service provider as detailed here: https://apacheignite.readme.io/docs/plugins Service Provider does not use IgniteConfiguration.getPluginConfiguration inside of itself. Here is a link of the function that does the loading:

Re: 2.8.1 - Loading Plugin Provider

Veena, Per my previous note, the preferred way is to use the service provider as noted in the documentation page: https://apacheignite.readme.io/docs/plugins That is how the ML and directIO plugins are designed. see: https://github.com/apache/ignite/tree/master/modules/ml and:

Re: ContinuousQueryWithTransformer with custom return type

Hi, Looks like you are not correctly setting up your code: Take a look at: https://apacheignite.readme.io/docs/continuous-queries#remote-transformer see: https://github.com/apache/ignite/blob/master/example

Re: 2.8.1 - Loading Plugin Provider

Hi, You don't need to load the the plugin provider through the service loader of the JDK in addition to using setPluginProvider. It is preferable to use the service loader alone like in MLPlugin see:

Re: How to evaluate memory consumption of indexes

Hi, Use metrics to see what data regions are using off heap. https://apacheignite.readme.io/docs/iodataregiondata_region_name A small index should not consume that much memory. Try turning on persistence to see exactly how large your index.bin files are.

Re: Setting expiry on the fly via Data Streamers

Hi, You can use a Stream Receiver(visitor implementation) to intercept incoming entries and create an expiry policy on the fly. see:https://apacheignite.readme.io/docs/data-streamers#streamvisitor example: CacheConfiguration cfg = new CacheConfiguration("wordCache");

Re: Durable Memory Setting(Off-Heap)

Hi, See: https://apacheignite.readme.io/docs/durable-memory and https://apacheignite.readme.io/docs/durable-memory-tuning Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: native persistence

Hi, Indexes are stored in the same place as the data, in a file called index.bin You can't change the relative location of the index file(s). Only the storage path/wal path/wal archive path(s) could be specified. See:

Re: Ignite on AKS and RBAC issue

Hi, I see that you've bound everything to the "default" namespace. kubectl describe serviceaccount ignite Name:ignite Namespace: default Make everything in the "ignite" namespace as described here: https://apacheignite.readme.io/docs/rbac-authorization

Re: Ignite server of perNodeParallelOperatoins ?

Hi, A dataStreamer collects entries into a buffer, and when it is full, sends the buffer over to a server node.. see: perNodeBufferSize(int) https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html#perNodeBufferSize-int- perNodeParallelOperations is a

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

Manu, Can you set up the lightest load/simplest topology possible, send the Ignite logs from all nodes(server and clients), including the GC logs, and we will take a look. https://apacheignite.readme.io/docs/jvm-and-system-tuning#detailed-garbage-collection-stats Thanks, Alex -- Sent

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

Hi, Looks like the system is being slowed down for some reason. Many Ignite operations are taking a long time(>30 sec) where they should complete much quicker. Are you able to go back to 2.7.6 on the exact same config/setup, run the system for a period of time then go to 2.8.1 and

Re: Thread starvations

Hi, In your case, striped pool starvation messages are showing that some Ignite related tasks are taking longer then a preconfigured threshold. (See https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#getFailureDetectionTimeout--)

Re: Ignite SSL security

Hi, Internally, Ignite will use new File(keyStoreFilePath) ... This will interpret the keyStoreFilePath relative to the process working directory. Use: System.out.println("Working Directory = " + System.getProperty("user.dir")); to determine your working dir. Then use:

Re: Thread starvations

Hi, Starvation messages contain queue information, showing which tasks are pending. Looks like you are overloading the system w/too many requests/queries that are taking a long time. Send over log/reproducer/config/version #s/heap sizes and I'll take a look. Take a thread dump using

Re: Problem with writeBehind Apache Ignite 2.8.1

Hi, This shouldn't be happening. Please attach a reproducer and I'll take a look. Describe the steps you take to reproduce scenario. Include version #'s for all affected components. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Achieve uniform data distribution easily

Hi, see: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html Can you see the key to partition mappings: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html#mapKeyToPrimaryAndBackups-K- to see what

Re: Size of an object in Ignite cache

Hi, Ignite converts your object to a binaryObject before storing it: https://apacheignite.readme.io/docs/binary-marshaller You can take a look at the binary object format: https://cwiki.apache.org/confluence/display/IGNITE/Binary+object+format Also see this answer:

Re: Data streamer hangs

Hi, Are you seeing pool starvation messages? How long does it stay in this state? Are you not seeing any data saved, even when you close the jdbc connection? Are you able to reproduce this scenario? If so please describe steps/send a reproducer and send full logs. Data Streamer

Re: PIVOT with SQL

Hi, At present, PIVOT functionn is not supported. SQL function reference: https://apacheignite-sql.readme.io/docs/sql-reference-overview Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Questions Regarding Critical Workkers Health Check

Hi, Question-1: Does the above log mean that the thread is really blocked? or is it just busy doing something else? The thread in question might be busy doing something else and did not update its heartbeat timestamp. See:

Re: Default order of SQL result when Order By is not present

Hi, Ignite makes no guarantees as far as unordered retrieval is concerned. What you describe is emergent behavior, but it is not backed by an API contract. It also depends on whether cache in question is PARTITIONED or not, and on whether Page replacement algorithms are in effect,

Re: NPE during printing failure information

Hi, This looks like a communication problem. GridWorker [name=grid-nio-worker-tcp-comm-3 Make sure all nodes can see each other. Test it with a minimum number of nodes. If it still doesn't work then describe your test and send the full logs and Ignite condifg. Thanks, Alex --

Re: Can you pass host name to ignite visor?

Hi, use: ignitevisorcmd.sh -cfg= to connect with specified configuration. use ignitevisorcmd -help to see all command line options. see: https://apacheignite-tools.readme.io/docs/batch-mode Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Spring Integration

Hi, Send over your ignite config(include all beans), full Ignite logs and I'll take a look. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Zookeeper discovery in mix environments.

Limit your env to two nodes. Try using --net=host for docker containers. If that works, limiting to use setLocalHost for TcpCommunicationSPI, and configure ZooKeeper to use address translation/or bind to a specific address. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: What does: Failed to send DHT near response mean?

You can use setlocalHost to bind a node to one address only. see: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setLocalHost-java.lang.String- -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: What does: Failed to send DHT near response mean?

Hello, It means that a node was not able to exchange message w/another node because of network or firewall issues. It lists the node in question inside the message. Check to make sure that the node is available and is in working order. *Failed to send DHT near response *[futId=16392,

Re: Zookeeper discovery in mix environments.

In terms of TcpCommunicationSPI it might help: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setLocalAddress-java.lang.String- Also look into setting the localaddress:

Re: Ignite node log file setup

Hi, Update the file appender, and put cache-node-01 into the filename property as below. Use env variables in your appenders, or re-config at run time as need be. see: https://apacheignite.readme.io/docs/logging#log4j2 You can also pro-grammatically create the

Re: Ignite SystemViews DataRegion

Hi, There is a DATA_REGION_NAME in the CACHES and CACHE_GROUPS view mapping a cache/cache group to a data region. https://apacheignite.readme.io/docs/caches data region metrics: https://apacheignite.readme.io/docs/iodataregiondata_region_name

Re: Help with ignite cluster

Hi, Fail to find data nodes for cache: * means that a call to a partitioned cache is not finding any nodes w/data for that cache. Either the nodes are down, are unresponsive or unreachable. If this scenario is reproducible, send the logs from all nodes, a reproducer, a list of steps

Re: Semaphore Lock Not Acquired. Race issue?

Also wanted to mention that there is a working semaphore example available: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datastructures/IgniteSemaphoreExample.java -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Semaphore Lock Not Acquired. Race issue?

Hi, In an older version there was an issue that caused this condition https://issues.apache.org/jira/browse/IGNITE-8987 Send a reproducer, mention the version you are using, along with Ignite logs(from both nodes) and a stack trace of both servers when this condition occurs. How to

Re: Unable to enable ML inference storage

Courtney, This config should be enough It will load the ML plugin and initialize model storage. You can send me a reproducer and I'll take a look. Thanks, Alex -- Sent from:

Re: ignite load Cache and cluster warm up

Hi, - loadCache has to be called only after cluster have reached a minimum amount of nodes (currently 3 nodes) You can use events to see when nodes join, or use the cluster api to see how many servers/clients are online, and then call loadCache() cluster api:

Re: Segregating Ignite client discovery and heartbeat exchange on different networks

Hi, An example of isolated cluster is provided here: https://apacheignite.readme.io/docs/tcpip-discovery#isolated-ignite-clusters-on-same-set-of-machines You can try binding specific IPs to a different networks use: CommunicationSpi:

Re: Zookeeper discovery in mix environments.

It is possible. All discovery communication is through ZooKeeper, but yes private docker IPs (172.. ) might be leaked over. Would need to see the full logs(Ignite and Zookeper) which contain the IPs of the node and the particular one used for a given communication. Try running docker w/--net=host

Re: Zookeeper discovery in mix environments.

Hi, ZookeperDiscoverySpi uses ZooKeeper to transmit discovery messages. You can specify a comma separated host:port pairs, each corresponding to a zooKeeper server here:

Re: Slow query from PHP PDO with auhentication enabled

Hi, I am not seeing such differences. Once an authenticated session is established, the extra processing is minimal. Run the following experiment use this example (or create your own)

Re: Ignite Spark - Error - Did you call Ignition.start(..)?

Hi, This is a know issue w/IgniteSparkSession.builder() see: https://issues.apache.org/jira/browse/IGNITE-12637 use: https://apacheignite-fs.readme.io/docs/ignite-data-frame Please add your reproducer project to IGNITE-12637 to help fix the issue. Thanks, Alex -- Sent from:

Re: Slow query from PHP PDO with auhentication enabled

can you attach a reproducer project that prints out these measurements, and I'll take a look. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Slow query from PHP PDO with auhentication enabled

Hi, Queries should not be slower. Send a reproducer project/logs and timings for queries w/and w/out authentication enabled. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: partition loss policy

Hi, See: https://apacheignite.readme.io/docs/partition-loss-policies Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Retrieve object from cache triggers ClassNotFoundException

Hi, This test works in my setup, but its best if you left the deserialization to ignite via ignite.cache(..).get(...) Try modifying the example:

Re: Why does CacheBasedDataSet destroy the cache it is given

Hi, This is the way CacheBasedDataset has been designed. It has been made w/an eye toward training the implemented ML models: https://apacheignite.readme.io/docs/model-updating You are free to create an implementation to fit your needs. Use these examples to test your design:

  1   2   >