Reducing the port range (to a single port) and lowering the
IgniteConfiguration.setFailureDetectionTimeout to 1000 helped speed up
everybody joining the topology and I was able to get a pi estimator
run on 64 nodes.
Thanks again for the help, I'm over the current hurdle.
Joe
Quoting d...@
Hi Yuri,
Is there a chance you can create a small github project reproducing this?
You don’t need to have 15 caches, I think 1 cache would suffice.
If the above is not possible, then we will have to investigate by looking
at logs, code, etc., which would take more time.
D.
On Mon, Oct 26, 2015
Hi All,
we are using Ignite 1.3.3 in win server environment.
*Caches configuration*
Each Ignite node has ~15 caches ~1M records each of Integer-to-Object
entries (total memory required ~7Gb), configured as "REPLICATED",
readFromBackup flag is set to "true", transaction mode is "ATOMIC", all the
Thanks Artem,
You are right, I think I only subscribed to the user list after creating
this thread.
Nico
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-tp1656p1709.html
Sent from the Apache Ignite Users mailing list archive a
I've created an issue for Hibernate 5 support. You can track status there:
https://issues.apache.org/jira/browse/IGNITE-1794.
P.S. Please also subscribe to user list in order to other users to be
notified
about your questions.
--
View this message in context:
http://apache-ignite-users.70518.x
Thank you both for your responses. I have a better understanding of the stack
and its characteristics now.
James
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Native-NET-tp1689p1706.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Thanks for the quick response Denis.
I did a port range of 10 ports. I'll take a look at the
failureDetectionTimeout and networkTimeout.
Side question: Is there an easy way to map between the programmatic
API and the spring XML properties? For instance I was trying to find
the correct xml
Hi,
Is it possible with Ignite to index or query fields of entity children ?
An example would be two structures, one embedded into another.
When I query for ProductSpecification entity, I'd also like to return
catalogId value or possibly search on those fields ? But I couldn't
find any relevant do
On Sun, Oct 25, 2015 at 6:17 PM, Edison wrote:
> It's pretty simple. In the top API, they'll call method like read(String
> sql, List parameters), then I'll use Ignite to read from the cache
> or db(if not hit).
>
Hm… not sure how you can know if SQL is a hit or a miss. What if you only
have a p
As far as I can tell, the only potential overhead in Ignite .NET support
vs. Java is the JNI layer. However, we have been testing it internally, and
in distributed tests (2+ nodes) we have not seen any performance
degradation due to JNI. The reason is that JNI overhead becomes largely
negligible co
James,
Yes, you described Ignite.NET architecture correctly. It provides native
.NET API and marshalling layer. All infrastructure-related work is
performed by C++/Java code.
Vladimir.
On Mon, Oct 26, 2015 at 12:52 PM, jamesgibbs100
wrote:
> Vladimir,
>
> Thank you for taking the time to get b
Hi, Joe,
>I also haven't been seeing the expected performance using the hdfs api to
access ignite.
Regarding the slow IGFS, please create another topic for that problem, since
this may not be related to discovery issues in large cluster. Can you please
send us configs you have used to test IGFS sp
You can find examples here:
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/streaming/StreamTransformerExample.java.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/StreamTransformer-usage-issue-How-to-get-value-of-i
Hi,
StreamerTransformer javadoc says "Convenience adapter to transform update
existing values in streaming cache based on the previously cached value.".
So, you see right behavior.
I recommend you look at StreamTransformerExample for examples of usage
StreamerTransformer.
So, for your use-case S
endian675,
1. we cannot remove current REST API since we have its users
2. but we can deprecate it after we implement new version with mentioned
improvements.
Can you please file a JIRA issue and contribute new REST API to Ignite?
--Yakov
2015-10-21 19:06 GMT+03:00 endian675 :
> Agreed. It lo
James,
My last statement is a bit confusing. What I wanted to say is that normally
both Java and .Net spend comparable time on serialization.
On Mon, Oct 26, 2015 at 10:38 AM, Vladimir Ozerov
wrote:
> James,
>
> Ignite is distributed application and both Java and .Net require
> marshalling to p
James,
Ignite is distributed application and both Java and .Net require
marshalling to pass data between nodes. Therefore, in the vast majority of
scenarios .Net has marshalling overhead comparable to Java version.
Vladimir.
On Sun, Oct 25, 2015 at 8:46 PM, James Gibbs
wrote:
> Hi there
>
> I'
Hi Joe,
How big is a port range, that you specified in your discovery
configuration, for a every single node?
Please take into account that the discovery may iterate over every port
from the range before one node connects to the other and depending on
the TCP related settings of your network i
18 matches
Mail list logo