I would say that memory consumption is individual and may vary depending on
configuration parameters. I agree with Val's points, but I would also
advice you to load your caches (with smaller test data set at least) and
take a look at heap dumps.
--Yakov
2015-08-19 8:27 GMT+03:00 vkulichenko
I like the article.
Couple of points, though:
1. Annotations and XML configs are not identical. XML states that ID is
UUID, but annotations listing states that it is primitive long.
2. I would prefer example that example can be copied-and-pasted and
launched. Can we add cache config, indexes, and
Ability to set consistentId will appear in next release.
--Yakov
2015-08-05 18:21 GMT+03:00 avk andrewkor...@hotmail.com:
Val,
I can't seem to be able to find the class that provides setConsistentId()
method. I checked the latest code as well as the 1.3.2 release...
Could you please point
Val, I think you provided the wrong link to the ticket. Can you please
recheck?
--Yakov
2015-08-04 10:43 GMT+03:00 vkulichenko valentin.kuliche...@gmail.com:
Alexander Hohlov wrote
Hi All
Is it possible to see Spring Data support for GridGain Fabric in the
future?
Is anyone
You created cache configuration, but do not use it. This makes all your
entries stored onheap.
Pls do:
cache = ignite.getOrCreateCache(cache, myCfg);
--Yakov
2015-07-30 4:55 GMT+03:00 javadevmtl java.dev@gmail.com:
Using Ignite 1.3.0 with Java 1.8_45 on Ubuntu 14.04
Writing a micro
It seems you start continuous query and there is a field of IgniteCache in
your remote filter. Can you try removing it for now? As far as permanent
fix - let us investigate.
--Yakov
2015-07-29 16:52 GMT+03:00 Mirko Raner mi...@raner.ws:
After some application code changes, we're seeing the
Cross-posting to dev. Sergey E., can you take a look and finish with this?
Valery, thanks for pointing out.
--Yakov
2015-07-17 9:24 GMT+03:00 shibaevv shibaev.val...@gmail.com:
This fix with JTA is working if I keep ignite config outside of my war file
(e.g. $JBOSS_HOME/config).
But if I
We are in the end of QA cycle and will make community edition available in
a day which should contain JTA fix.
You can also give a try to RC available here:
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.3.0-rc2/
--Yakov
2015-07-15 6:47 GMT+03:00 shibaevv shibaev.val...@gmail.com:
This seems to be networking issue between the machines used in tests.
Can you please make sure that TCP connection can be established between the
machines? Please also turn off all antivirus and firewall software for the
tests.
--Yakov
2015-07-09 23:07 GMT+03:00 dsetrakyan
Mario,
Although client discovery is in code it has never been announced. It will
be dropped in the upcoming release and client mode will appear for ordinary
tcp disco.
As far as reconnection - you raised a very good question. It is currently
under development in new API and will be available
Isaeed, priority queue and sorted structures are no supported at the moment.
As far as your approach - it should work. However, let me think a bit and
come back to you in a couple of days.
--Yakov
2015-06-15 16:39 GMT+03:00 Isaeed Mohanna isae...@gmail.com:
Hi
I need a Distributed sorted
Alex,
You can use S3 IP finder for such deployment. Please note that nodes from
AWS should be able to connect to private network as well as private nodes
should be able to connect to AWS. This can be solved via VPN.
Please also take a look at org.apache.ignite.configuration.AddressResolver.
May
should not hit the issue.
You can inject Ignite instance to your job, closure, predicate, etc with
org.apache.ignite.resources.IgniteInstanceResource annotation. For details
please refer to corresponding documentation.
--Yakov
2015-06-10 17:44 GMT+03:00 Yakov Zhdanov yzhda...@apache.org:
This seems
This seems to be a race condition which should be trivial to fix. I suspect
that DataStructuredProcessor has not yet received onKernalStarted, but
started processing messages. I created a ticket -
https://issues.apache.org/jira/browse/IGNITE-1007
--Yakov
2015-06-10 1:16 GMT+03:00 dstieglitz
Hi! I reproduced the issue and filed a ticket:
https://issues.apache.org/jira/browse/IGNITE-976
In the meantime, turn off peer-loading and make all classes available on
all nodes. This configuration is much better from performance standpoint
and is recommended in production.
I am also
Correct link is https://issues.apache.org/jira/browse/IGNITE-975
--Yakov
2015-06-02 13:03 GMT+03:00 Yakov Zhdanov yzhda...@apache.org:
Hi! I reproduced the issue and filed a ticket:
https://issues.apache.org/jira/browse/IGNITE-976
In the meantime, turn off peer-loading and make all classes
, Jun 2, 2015, 08:04 yakov [via Apache Ignite Users] [hidden
email] http:///user/SendEmail.jtp?type=nodenode=442i=1 wrote:
Correct link is https://issues.apache.org/jira/browse/IGNITE-975
--Yakov
2015-06-02 13:03 GMT+03:00 Yakov Zhdanov [hidden email]
http:///user/SendEmail.jtp?type=nodenode
Ognen,
UUID is not a requirement for id fields at all. Ignite does not have such
limitations. You can use any field name, any type, etc
When I run your original code I have:
Exception in thread main
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
(retry update if
As far as publishing a book we don't have such plans for the nearest future
--
Yakov Zhdanov, Director RD
*GridGain Systems*
www.gridgain.com
2015-05-25 15:28 GMT+03:00 yakov yzhda...@apache.org:
Did you check readme io documentation?
http://apacheignite.readme.io/v1.0/docs
--
View
;)
Thanks,
Ognen
On Mon, May 25, 2015 at 7:44 AM, Yakov Zhdanov yzhda...@gridgain.com
wrote:
As far as publishing a book we don't have such plans for the nearest
future
--
Yakov Zhdanov, Director RD
*GridGain Systems*
www.gridgain.com
2015-05-25 15:28 GMT+03:00 yakov yzhda...@apache.org
Ognen, this message is output by Discovery SPI in case if it has not
received ack for discovery message from peer node. This may be caused by:
1. (most probably) GC pause on peer
2. network problem, esp if you are running in virtual env
3. (less probably) - by extremely high network and/or CPU
Romain,
Can you please explain the use case a bit. Version has always been a
private class and user access to it is not a common scenario.
As you noticed, CacheEntry in JCache is very simple and does not carry any
additional information/functionality, so we removed ability to get version
as
Can you please share your code?
--Yakov
2015-05-20 15:51 GMT+03:00 ali ali.che...@gmail.com:
Hi
I'm trying to use ignite to perform some computations over a large size of
data (3M objects)
and quickly hit the GC overhead limit memory.
In order to test i'm using a single machine with one
Yes, your network should be bi-directional.
--
Yakov Zhdanov, Director RD
*GridGain Systems*
www.gridgain.com
2015-05-20 14:51 GMT+03:00 Isaeed Mohanna isae...@gmail.com:
Hi,
As i understood the AddressResolver will allow me to map internal ip
address to external up addresses, however my
Currently Ignite has an issue with page size and scan query. If your scan
query does not use any predicates, can you please switch to iteration over
entrySet() for now?
Here is the ticket you can track -
https://issues.apache.org/jira/browse/IGNITE-872
--Yakov
2015-05-20 16:33 GMT+03:00 ali
Ali this seems to be reproducible with scan queries only when local server
carries the data and is in the query topology
--Yakov
2015-05-20 17:22 GMT+03:00 Yakov Zhdanov yzhda...@apache.org:
Currently Ignite has an issue with page size and scan query. If your scan
query does not use any
Isaeed, you can configure load balancer in your network and all clients
will be automatically routed to keep balance.
For exposing functionality via REST you can do:
1. Use distributed services (as discussed)
2. Simply run Jetty (or any other container), launch Ignite on context
startup and
27 matches
Mail list logo
