Hi Ilya,
Yes, I start the ignite in client mode and my other applications access this
ignite cluster. I use to start the ignite cluster with 40-executors -and
2-cores. Usually, in success scenario my starting ignite and data loading
finish within 5/6 minutes. The logs are for negative scenario,
Hi Ilya,
Thank you for your response. I have checked my client side load testing
library (I am using YCSB btw) and I found a potential memory leak. However,
can the client side using too much heap cause the server to fail? There is
no other applications running on the Apache Ignite servers
--
Can you easily register a continuous query using Visor or something? I
would like to see all cache activity including the before and after
toString() representation of objects being modified. I just want to
eyeball it during development, not pipe it into another application etc
On Wed, Feb 19,
I'm building/running my client app w/Gradle and I'm seeing this error. Am
I overloading the Ingite H2 fork with the real H2 or something? It appears
I have the latest h2:
[.gradle]$ find ./ -name *h2*
./caches/modules-2/metadata-2.82/descriptors/com.h2database
Hi,
Usually it's Continuous Queries:
https://www.gridgain.com/docs/latest/developers-guide/key-value-api/continuous-queries,
but it depends on your use case. What do you want to do with these events?
Best Regards,
Evgenii
ср, 19 февр. 2020 г. в 14:54, Andrew Munn :
> What's the best way to
What's the best way to watch a cache for insert/update/delete events?
Hi all.
Having issue with installing SSL certificate with Jetty configuration:
cache.xml snippet:
jetty-ssl.xml snipppet:
Apparently the certificate loads correctly, but the browser complains about
"your connection is not private" and NET::ERR_CERT_COMMON_NAME_INVALID.
The certificate is
Hello,
There is no need to restart the cluster if you want to create a new cache as
dynamic cache creation is supported:
https://apacheignite.readme.io/docs/jcache#section-dynamic-cache
Do you use native persistence or do you run in-memory?
If this doesn't work for you, could you please
Hi,
I am using partition aware loading to load big tables using 4-8 threads on
each nodes.
I have around 16 caches. 2 caches have 38-40 million entries. It takes
around approx 21 minutes to load the caches on 6 nodes.
I have kept the backup count to 2.
Will share the code tomorrow.
Regards,
Hi Ilya,
Yes, I start the ignite in client mode and my other applications access this
ignite cluster. I use to start the ignite cluster with 40-executors -and
2-cores. Usually, in success scenario my starting ignite and data loading
finish within 5/6 minutes. The logs are for negative scenario,
Should be fixed now. Thanks for reporting!
> On 19 Feb 2020, at 09:33, Stephen Darlington
> wrote:
>
> I forwarded to the developer mailing list.
>
>> On 18 Feb 2020, at 20:28, Devin Anderson wrote:
>>
>> ::Bump::
>>
>> Devin
>>
>> On 2/17/20 5:42 PM, Devin Anderson wrote:
>>> Hi all,
>>>
Helo!
I can see that clientMode is true, this means that it has to find some
server nodes ot join.
GridDiscoveryManager fails to start because you interrupt it. Ditto the Zk
connection that you quote next.
Regards,
--
Ilya Kasnacheev
ср, 19 февр. 2020 г. в 15:03, ChandanS :
> Hi Ilya,
>
>
Hi Ilya,
When it doesn't fine existing ignite cluster, I use to create a new one. If
you see the logs, you will get
>>> Starting Ignite Client with cluster name: titan-resourceUP
You can also see ignite initial start logs as well:
>>>__
>>> / _/ ___/ |/ /
Hello!
There's no way you will load 20,000 records in 25 minutes. That's 10
records per second. I just can't think of any reason why it might take such
monumental amount of time.
With regards to data streamer, as I have said I recommend partitioning your
data and loading every segment from its
Hello!
>From this log:
[17:19:09,949][WARNING][jvm-pause-detector-worker][IgniteKernal] Possible
too long JVM pause: 1405 milliseconds.
[17:19:12,237][WARNING][jvm-pause-detector-worker][IgniteKernal] Possible
too long JVM pause: 1983 milliseconds.
Hello!
I think you can refer to this ticket:
https://issues.apache.org/jira/browse/IGNITE-1943
mcompact functionality:
When node leave we can get gap in variable names. For example: node command
show @n1, @n2, @n3 variables, then nodes @n1 and @n2 leave. node command
show only @n3 After mcompact
I forwarded to the developer mailing list.
> On 18 Feb 2020, at 20:28, Devin Anderson wrote:
>
> ::Bump::
>
> Devin
>
> On 2/17/20 5:42 PM, Devin Anderson wrote:
>> Hi all,
>>
>> I'm not sure if this is the correct mailing list to bring up this issue. If
>> I'm writing the wrong mailing
Hi Ilya,
>From my spark application, I am trying to do two things:
First, start Ignite yarn cluster using ignite-yarn.jar
Second, load data to ignite cluster.
In the first step, I have my own method to submit another spark job with
YarnConfiguration to start the ignite. In second step, I use to
18 matches
Mail list logo