Hi all:
I got a ignite active error when i start my ignite server node with
multiple data regions configuration below:
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setConsistentId("test");
cfg.setIgniteInstanceName("oneDataGrid");
cfg.setClientMode(false);
Hi all:
I got a ignite active error when i start my ignite server node with
multiple data regions configuration below:
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setConsistentId("test");
cfg.setIgniteInstanceName("oneDataGrid");
cfg.setClientMode(false);
Hi Slava
I did it, and could see the cache /tables thru both IgniteVisor and Sqlline
However, when I tried to query the data, I am getting below error
Error: class org.apache.ignite.binary.BinaryObjectException: Custom objects
are not supported (state=5,code=0)
java.sql.SQLException: class o
> You can configure both native persistence and cache store
I think this is not officially supported, I believe
On Mon, Dec 25, 2017 at 3:05 PM, siva wrote:
> Do you really need both persistent stores enabled?
> Yes
>
> Do you use the SQL server store to integrate with other apps?
> Yes
>
>
>
>
Do you really need both persistent stores enabled?
Yes
Do you use the SQL server store to integrate with other apps?
Yes
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
You can configure both native persistence and cache store with
write-through policy but it will not provide you consistency guarantees: it
would be possible that some data is persisted in one store but not the
other if a failure occurred.
Do you really need both persistent stores enabled? Do you u
Cache#invoke(key, entryProcessor) executes the "entryProcessor" on a node
where the "key" is stored. This is called "colocated processing" that
allows you to offload processing from client to server nodes and avoid
transferring the "key" and result over the network (although now we have to
transfer
Naveen,
I am not sure I understand you correctly.
Ignite off-heap usage is a part of your VIRT "top" output. You can add DATA
column to "top" output to better visualize memory usage of pure
on-heap+off-heap data only.
Please run Ignite with different memory settings and see the memory
footprint.
