Hello,
I am developing a messaging system with notifications via WebSockets (When
the user 'A' sends a message to the user 'B' I need to show a notification
for the user 'B' about a new message). Different users are connected to
different servers. I wonder to know if Apache Ignite is suitable for
Thank you Val. this is really helpful.
On 20 October 2016 at 23:32, vkulichenko
wrote:
> Hi,
>
> This is the name of local Ignite instance within current JVM. This allows
> you to start several nodes within one JVM and access different instances
> within one
Hi Warm-hearted person,
Thanks for your help.
According to your advice, I will query some field not using select *. I
will add the index in the cache.
To Vladislav Pyatkov,
In previous mail, you said "you are always can copy data to another cache
(with index) and drop this",
Hi,
This is the name of local Ignite instance within current JVM. This allows
you to start several nodes within one JVM and access different instances
within one application using Ignition.ignite(name) method. If you always
have single node per JVM, you should just use default (null) name
Hi Labard,
You can create your own Factory implementation and create the store in any
way you want within this implementation.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Factory-Builder-For-Persistent-Store-tp8382p8387.html
Sent from the Apache
Hi Dan,
When a job is cancelled, the thread running it is interrupted. So all these
rules are applied in the same way.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Killing-jobs-on-cluster-safe-allowed-tp8385p8386.html
Sent from the Apache Ignite Users
Hi group:
Are compute jobs submitted to ignite subject to the same restrictions as
Thread with respect to killing running processes?
For example, killing threads via API, (e.g., .stop()) are not allowed in
Java, you have to code special conditionals into the thread to stop it
cleanly, but does
Hi Piali,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
piali wrote
> Can you please let me know that what is
This looks like a class loading issue. Do you have peer class loading
enabled? Are you running within an application server or other environment
with multiple class loaders? I recommend to set a breakpoint inside the
get() method and check why there are classes loaded by different class
loaders.
Hello.
I want to make Persistent Store for my Cache. But my implementation of
CacheStoreAdapter should get some
parameters(dbName,Table,ConnectionProperties) in constructor. And
FactoryBuilder which I use in ignite config file want no-args constructor.
What should I do?
Labard
--
View this
This command completely destroys the cache with all its data. Can you clarify
what you mean by "release" here?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/What-is-the-purpose-of-command-cache-stop-tp8378p8381.html
Sent from the Apache Ignite Users
Hello,
is there any significance to grid name in ignite configuration file.
1.
URL resource = CacheManager.class.getResource("/ignite.xml");
Ignition.start(resource);
Ignite ignite = Ignition.ignite("my-grid");
2.
Connection conn =
I want to release the cache space by command in tool ignitevisorcmd.
I tried to the command "cache stop", after I inputted the command , I could
not find the cache, but the cache space seems not be released.
What is the purpose of command "cache stop"?
--
View this message in context:
hi, i am getting ClassCastException while fetching data from IgniteCache.
below is the code fragment:
CacheConfiguration cacheCfg
= new CacheConfiguration(CACHE_NAME);
...
IgniteCache cache =
I've checked the command you provided.
It works, though it really does not add any objects to DB. However,
I've added some prints to TestTableStore#writeAll() and I can see that
all 100 entires are passed to it to be written. It seems that there is
some issue with your implementation of this
Bob, can you please also tell what is your benchmark scenario? Do you have
enough warm-up cycles to bring your app to some steady state?
--Yakov
2016-10-20 12:40 GMT+03:00 Vladislav Pyatkov :
> Hi Bob,
>
> One way to do SQL faster this is adding indexes.
> 1) I do not
Hi Bob,
One way to do SQL faster this is adding indexes.
1) I do not think what the estimation will be a lot improve without index.
Because of the need to serialize, deserialize and move in network data.
2) Ignite does not create index on existing data, but you are always can
copy data to
Bob,
1) Did you create index on Ignite cache?
2) Could you attach you cluster and cache configs?
I also agree with Jörn Franke, that such simple query (no joins, simple
"where condition") is not very suitable for benchmarking (unless all in
your app you are using such queries a lot).
--
Thanks Shamim.
Information provided was very useful.
I was able to query the cache using DBeaver.
- Ganesh
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/GUI-based-SQL-Client-for-Apache-Ignite-tp8283p8372.html
Sent from the Apache Ignite Users mailing list
You have to understand for what the database cache is good: lookups of
single/few rows. This is due to the data structure of a cache. In this sense
you use the cache wrongly. Aside of this I think select * is really the worst
way to do professional performance evaluation of your architecture.
Hi, everyone
My test environment: Ignite cluster has 8 nodes, every node has 8 cores CPU
and 30G memory. Their network has 1000M speed.
Oracle is deployed in the machine which has 32G memory and 8 cores CPU.
My db table has 47535542 rows with 99 columns.
When no index, the
21 matches
Mail list logo