Hello all,
I actually found what the problem was.
I accessed the fields of the BinaryObject in that way:
IgniteCache cacheAsBinary =
cache.withNoRetries().withSkipStore().withKeepBinary();
///Do a million times
BinaryObject bo = cacheAsBinary .get(key);
Long field1 = o.field("field1");
but I
Hi Denis,
We thought it would have the same performance impact as DROP TABLE. Hence we
didn’t used it.
May be we will try that option and get back to you.
Thanks & Regards,
Sriveena
From: Denis Magda [mailto:dma...@apache.org]
Sent: Thursday, August 30, 2018 11:06 AM
To: user@ignite.apache.org
Yes, Ignite is an excellent alternative to GemFire. I personally came
across many replacements in various organizations.
--
Denis
On Mon, Aug 27, 2018 at 2:26 AM Nilesh
wrote:
> Hello,
>
> We are looking for Apache Ignite for Gemfire replacement. Current we are
> facing following issues in
>
> Next time if there is change in the data from the data source in terms of
> addition of new column or delete column...Then we drop the table in ignite
> and recreate it.
Is there any reason why you can't use ALTER TABLE command for the addition
or remove of columns in runtime? It will be
Eugene,
Just want to be sure you know about the existence of the following pages
which elaborate on Ignite memory architecture in details:
-
Ignite 2.5
Is there a way to ensure grid nodes don't serve any requests until they are
caught up with the replicated state in the cluster?
Thanks
--
Anirudha P. Jadhav
Ignite 2.5 - fully replicated 8 node cluster
When running load tests with 1 unique key, only one of the servers gets all
the requests.
Is there something to be enabled in configuration for balancing load
between all machines.
Thanks
--
Anirudha P. Jadhav
Thanks Denis for getting back to me much appreciated.
The use case we have is we have millions of data points which is updated by
the other teams in separate databases. Whenever this happens we receive a
message upon update and it triggers the load cache process in ignite.
Until now we did not
Lokesh, looking at the javadocs of [1] you can subscribe for EVT_NODE_FAILED
and EVT_NODE_SEGMENTED events.
>From my personal experience SegmentationPolicy.NOOP is required in very rare
cases. My approach would be to STOP the node in most of the cases when the
segment happens or you can RESTART
Method ignite.cluster().active() shows whether or not a cluster was
activated.
To check started/stopped state you can use method
Ignition.state(igniteInstanceName).
ср, 29 авг. 2018 г. в 19:36, Paolo Di Tommaso :
> Hi Igniters,
>
> What's the suggested way to check if the grid is stopped. I'm
(Full logs and test class should be attached at the bottom..)
I am running ver. 2.5.0 in client/server mode and am calling
ignite.compute().call(..) on an IgniteCallable.
Server node does not have any of my code on its classpath, but peer class
loading it set to true on both the server and the
For the ones having the same problem, I've managed to switch this message
off adding the following line just before initialising ignite
Logger.getLogger('').setLevel( Level.OFF )
Cheers, p
On Mon, Aug 13, 2018 at 10:09 AM Evgenii Zhuravlev
wrote:
> It's a class loading problem for
Hi Igniters,
What's the suggested way to check if the grid is stopped. I'm trying
ignite.cluster().active()
but it's throwing the following exception.
java.lang.IllegalStateException: Grid is in invalid state to perform this
operation. It either not started yet or has already being or have
Hi Dave,
> The DataStreamer is unordered
Yes, that is absolutely correct.
If I understand correctly, the initial use case is the following:
- there is an initial payload that is streamed into the cluster via
data streamer.
- during that operation, new updates arrive and corresponding
Where does this call for a custom plugin need to be done?
i.e
TcpDiscoverySpi discoSpi = new TcpDiscoverySpi();
discoSpi.setAuthenticator(new TokenAuthenticator());
igniteConfig.setDiscoverySpi(discoSpi);
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, try to play with current KMeans from master
I hope this bug was detected correctly and fixed in
https://issues.apache.org/jira/browse/IGNITE-9393
Could you post any results of your experiments here?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Sorry, my bad. Here’s the method. Basically I am directly invoking the
Ignition.ignite() with expiry policy.
public static Cache getOrCreateCache(String name, Factory factory)
{
CacheConfiguration cc = newCacheConfig(name);
cc.setExpiryPolicyFactory(factory);
What does the *getOrCreateCache* method do internally?
Denis
ср, 29 авг. 2018 г. в 5:52, HEWA WIDANA GAMAGE, SUBASH <
subash.hewawidanagam...@fmr.com>:
> Hi all,
>
> Is there any possibility for this to happen ? We’re using Ignite 1.9.0
>
>
>
> Following is the code we use to obtain the cache.
If you use a cache store, and change values in the underlying database,
then they won't be propagated to Ignite, and old values will be used.
There is no mechanism, that can notify the cache about updates on the
3rd-party DB.
But if you didn't have this value in the cache, and read-through
Hi Taras
I am slightly confused. You are mentioning sslcontext and looking at those
related classes it doesn't appear to offer authentication and authorization.
Here is where i currently am with this project.
I have a white list plugin that i will apply to server nodes when they join.
I have
The SQL interface does not allow you to configure details of the cache
except via templates. The use case is I want to start with the cluster
specific defaults for a cache, and add some others.
I can create a empty real cache that has the defaults, and use its
configuration in the
Thanks for the docs.
The docs says "EVT_NODE_SEGMENTED" is
Generated when node determines that it runs in invalid network segment.
But when I disconnected 1 node from a cluster of 2 nodes, none of the 2
nodes generated that event. They both released only "EVT_NODE_FAIL" event.
On Wed, Aug 29,
The DataStreamer is unordered. If you have duplicate keys with different
values, and you don't flush or take other action, then you will get an
arbitrary result. AllowOverwrite is not a solution.
Adding to the streamer returns a Future, and all of those futures are
notified when the buffer
Hey :)
Actually I use the java api in order to query the ignite DB and I managed to
reduce the query time by using setLocal(true).
But my real question is that according to documentation it should work the
same whether I use local or replicated, So why with replicated it takes so
much longer?
Ilya,
Thank you for all clarifications!
Best regards
Michal
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Lokesh, see [1] how node will act when the segmentation will occur. You have
to register for EVT_NODE_SEGMENTED events. Ignite plugins contains all this
information as well.
[1] SegmentationPolicy
Hello,
I don't think there is a way to do that check. Moreover, it seems to me
that is useless in any case.
The thing that allows you to achieve the desired behavior is
`allowOverwrite` flag [1].
By default, the data streamer will not overwrite existing data, which means
that if it will encounter
Thanks Luqman
This is what I'm looking for. I'm stuck on one thing though. What's the
difference between EVT_NODE_FAIL and EVT_NODE_SEGMENTED? I want to restart
the detached node. I created 2 nodes to experiment. I detached them and
both the nodes received EVT_NODE_FAIL but none of them received
anyone from anyone would be highly appreciated
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thank you so much Evgenii for the pointer.
Will try this option and get back to you.
Regards,
Sriveena
From: Evgenii Zhuravlev [mailto:e.zhuravlev...@gmail.com]
Sent: Wednesday, August 29, 2018 2:03 PM
To: user@ignite.apache.org
Subject: Re: Example for server client configuration in ignite
Hello!
Why don't you just use CREATE TABLE for that? I doubt there will be any
significant overhead even if you never use any SQL and only use Cache API
after that.
Regards,
--
Ilya Kasnacheev
вт, 28 авг. 2018 г. в 17:37, Dave Harvey :
> I did a suggested edit adding the Spring configuration
Join performed on the server nodes where data placed. To reduce the overall
size of the reduce set on the client you can use lazy flag for result set:
https://apacheignite-sql.readme.io/docs/performance-and-debugging#section-result-set-lazy-load
Evgenii
пн, 27 авг. 2018 г. в 19:44, Sriveena
>
> I mainly want to know whether the detached need would join the cluster
> automatically after the network is back or not?
>
*need = node
I tests such a situation, and found that the detached node is not joining
the cluster. Instead it produces following errors:
2018-08-29 12:35:25.625 ERROR
33 matches
Mail list logo