simply about difficult
There is a lot of pre-configured metrics in Ignite that disabled for default. If you want to see them, you may pass instance of LogExporterSpi to IgniteConfiguration like that: You can work with Ignite metrics by some number of ways, not only through the logging system. For example: JMX SQL Views OpenCensus Please, refer to […]
READ MORELet’s assume, that you already have configured SLF4J in your project. It remains to do two things. Add dependency: Configure Ignite:
READ MOREIf you want to limit outbound message queue size, you just need to create instance of TcpCommunicationSpi, and pass it to IgniteConfiguration:
READ MOREThere is three synchronization modes in Apache Ignite: FULL_ASYNC FULL_SYNC PRIMARY_SYNC You can switch them by this way:
READ MORESuppose that when starting the application, you encounter the following exception: It is assumed, that the /tmp/ignite/work directory is located on the local file system. If the application is running on a cluster, then Ignite will try to create such a folder on each node of the cluster. Exception reasons: The account under which the […]
READ MOREFull text of the exception in Apache Ignite: The code that uses the reentrant lock looks something like this: Check that when creating a lock, the last argument = true is passed to the reentrantLock method: If the error is still repeated, then this is a bug: https://issues.apache.org/jira/browse/IGNITE-3386. It appears when one of the server […]
READ MORE