Hi
I following the instructions in
http://smartkey.co.uk/development/securing-an-apache-ignite-cluster/ and
implemented a custom GridSecurityProcessor plugin. I got Ignite to recognize
the custom provider and the provider is returning my custom
GridSecurityProcessor like this:
@Nullable
Er...
In my opinion, readthrough synchronizes data from hbase to ignite cache. Even
though readthrough doesn't get any data from hbase, it also synchronizes data.
As a result, nullpointerexception comes out.
As I mentioned before, I use hbase without ignite to execute that line,
console will
Hi,
What are my options to refresh ignite cache from underlying persistent
store on a scheduled basis. My use case is I have a server node that loads
data from underlying store to cache and I have a couple of client nodes
that perform computations reading cache data. I understand using Eviction
Hi, Denis. Yes, actually this line "All the operations that are performed on
server nodes and use exchange rates in their calculation won’t need to go to
some primary node to load an exchange rate because all the data will be
located locally" answers my question.
I was just thinking about my use
Hi,
This line has nothing to do with Ignite. What is null - hbaseBean or hTable?
Most likely there is an initialization issue and you should check the cache
store factory that you're using. It has to properly initialize HBase
connections when the store is created.
-Val
--
View this message
Hi,
Replicated cache is used in cases when you need to store a small data set or
data set that is not updated frequently.
In banks area dictionaries with exchange rates are usually stored in replicated
caches because they are not updated frequently and they are relatively small.
All the
Alexei, but I still trying to understand the use case for the REPLICATED
cache.
As for the computing job, I would use the affinity collocation, so my job
will utilize the local cache anyway.
If I use the Ignite in the client mode (which means my client node doesn't
hold any data), it still has
Alexei, Abraham,
Eviction policy configuration doesn't make sense for OFFHEAP_TIERED mode.
Eviction policy works only for on heap entries in order to evict entries to
offheap.
For eviction of entries from offheap memory Ignite internaly uses other LRU
eviction policy and there is no way to
Thank you for your interest to the project!
Unfortunately, I have no idea what is wrong with your case. Can you please
share logs from all Ignite nodes so I can get minimal idea on what is going
on? Do you see exceptions in logs?
--Yakov
2016-05-13 14:12 GMT+06:00 georgeg
Yes, it's my code.
rs=hbaseBean.hTable.get(new Get(Bytes.toBytes(key)));
It's Hbase's api.
If I only use hbase without ignite to execute that line, console will return a
null value. But when I use ignite readthrough, console return a
nullpointerexception you have known.
I guess the really
10 matches
Mail list logo