Is it possible to have the Ignite Queue data be persisted via some sort of
Store? I've looked at the docs and can't seem to find any info on how queues
(and Sets for that matter) relate to the CacheStore and read/write
through/behind - how does this work? Essentially, I'd like for the data in
the
Hi Roger,
You can use Ignite-Cassandra integration module. In case you need to load
specific portion of you Cassandra dataset into Ignite you can use
*loadCache(...)* method of Ignite cache API, providing it appropriate CQL
query.
Igor
On Tue, Jul 11, 2017 at 8:29 PM, Roger Fischer (CW)
Hello,
I have seen the page on using Cassandra as the persistent store for Ignite. Are
the same concepts / classes applicable when using Cassandra as the backing
database?
I have a large data set in Cassandra. At system start I want to load the most
recent (ie. most used) data into Ignite.
Hi Lucky,
You can start the console by first executing the following command:
And then in the same console
It will open automatically a browser for you.
Cheers,
Humphrey
--
View this message in context:
Hi,
I saw this remark on the mailing list from vkulichenko:
>> Generally CacheStore is designed to be a single store shared between all
>> nodes.
I want to develop my own CacheStore implementation to a data store.
The data store will have a "contact point" or client running on each Ignite
node
Hi,
I think the scheduler processor does not match the expected processor
interface. This results to a bad state.
IgniteKernal is responsible to start each processors :
org.apache.ignite.internal.IgniteKernal.startProcessor(GridProcessor):
proc.start(cfg.isActiveOnStart());
But the
Hi,
I have created my own plugin to override some defaults in the Ignite.
For configuration purposes I have got a class xxxPluginConfiguration which
is implementing PluginConfiguration. This class has got all the
configuration related settings to my plugin.
Custom plugin provider I have got a
Sorry if the message appears twice.
I figured out my account was not ready to post when I send my first message
:
Hi,
I think the scheduler processor does not match the expected processor
interface. This results to a bad state.
IgniteKernal is responsible to start each processors :
Adding those line of code just after the startup solved the pb (very
temporarily).
ignite = Ignition.start(conf);
if (ignite instanceof IgniteKernal) {
IgniteScheduleProcessorAdapter scheduler = ((IgniteKernal)
ignite).context().schedule();
if (scheduler instanceof
Hi thanks for the reply.
We can't filter data.
public class NodeFilter implements IgnitePredicate {
private static final long serialVersionUID = 0L;
public NodeFilter() {
System.out.println("Start NodeFilter");
}
@Override public boolean apply(ClusterNode node) {
Thank again, Val
I have got the answer, but will write more info about our use-case, since it
might be useful for someone in the future.
We need to return value, but it will take some time (seconds, minutes) to
process those requests. The IgniteServices gives us decoupling from
knowledge about
Hi,
Possibly, H2 planned use different indices for these queries.
Try to use HINTS [1] if it is impossible to make H2 use proper index
without breaking other queries.
[1]
https://apacheignite.readme.io/docs/sql-performance-and-debugging#section-index-hints
On Tue, Jul 11, 2017 at 2:47 PM,
Also field a in A_CACHE.Rank (r) is indexed
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/query-performance-degrade-when-adding-a-filter-criteria-order-by-tp14624p14625.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi All
Our below query is working fine SELECT r.uniqueSkuId FROM A_CACHE.Rank as
r, B_CACHE.Item as T WHERE T.id = r.id AND T.b=? AND T.c=? AND T.d=? order
by r.rank desc limit 3
but when we add additional criteria (r.a=?) as below the time increase from
10 ms to ~500 ms
SELECT
Hi Andrew,
We have observed that following method(segment.access()) blocks ignite
data caching using data streamers(For single ignite instance). This limits
our resource utilization i.e. CPU, MEM are not fully utilized. How can we
avoid this blocking so that we can get maximum performance out
Hi,
IgniteSpringBean encapsulates lifecycle management and in general provides
a more convenient way of Ignite instance creation. For more details please
refer to the Java docs of the class.
Kind regards,
Alex
10 июля 2017 г. 8:05 PM пользователь "Humphrey [via Apache Ignite Users]" <
Yes,I had study the document many times.
But the document is too simple.
I still have two question:
1.How to set the IGNITE_H2_DEBUG_CONSOLE property? modified ignite.sh ? Maybe a
particular setting is perfect to me.
2.what is the URL if I open browser?
By the way,the web console is too heavy
Hi did you look here?
https://apacheignite.readme.io/docs/sql-performance-and-debugging
You can also use the web console to have it explain.
https://ignite.apache.org/addons.html#web-console
--
View this message in context:
Hello Humphrey,
I don't think that is the issue here. Still i checked with ur suggestion,
but the same exception is coming in the server logs(the exception is shown
in the previous mail).
I'm just not able to understand what i'm doing wrong here. Still thanks for
ur suggestions.
Aiden
--
Hi:
I want to analysis sql explain and debug sql .
How to start up H2 Console?
My server OS is centos6. IP is 192.168.1.2
Thanks.
Hi,
Thanks for the response. I executed the program which starts the gridgain as
below ie I set -Xms3G -Xmx10GB.
/usr/java/jdk1.8.0_121/bin/java -DIGNITE_QUIET=false -Xms3G -Xmx10G -classpath
21 matches
Mail list logo
