Hi,any update on the issue ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
For the requested full ignite log, where would this be found if we are running
using local mode? We are not explicitly running a separate ignite node, and our
WorkDirectory does not seem to have any logs
From: user@ignite.apache.org At: 12/03/19 19:00:18To: user@ignite.apache.org
Subject: Re:
For our configuration properties, our DataRegion initialSize and MaxSize was
set to 11 MB and persistence was enabled. For DataStorage, our pageSize was set
to 8192 instead of 4096. For Cache, write behind is disabled, on heap cache is
disabled, and Atomicity Mode is Atomic
From:
Ok thanks.
I have managed to get the times down to 13 seconds write and 7.5 seconds
read, basically double your times, on my 12 processor Intel i7-8850 laptop
which is running 100% so you must have some good kit!
Does Java version have any bearing on performance?
--
Sent from:
Is there any way we can get complete keyset or values from a near cache.
Something like cache.keyset()
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I am using Cassandra Ignite integration. In this integration, one is
able to provide specific "mapping" in persistence xml so a key is e.g.
a primitive and value is POJO.
Now, I was quite surprised (as a lot of other people too as I read
more about this), that it is not possible to do SQL
Hi Mitchell,
Looks like it could be easily reproduced on low off-heap sizes, I tried with
simple puts and got the same exception:
class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to
find a page for eviction [segmentCapacity=1580, loaded=619,
maxDirtyPages=465,
Hi,
Near cache makes sense only for key-value access, SQL doesn't work with
near caches at all.
Evgenii
вт, 3 дек. 2019 г. в 04:20, Hemambara :
> If I run sql with out where condition on near caches, query will hit server
> node correct ? It wont fetch from near cache in local node. Is this a
We are running Ignite in LOCAL mode currently and have persistence enabled. For
this specific test, the off heap memory was set to as low as possible (~10 MB)
to test on-disk performance. We have multiple caches sharing the same
DataRegion. For the test, we basically write synchronously to
Hi Humphrey! Checked in chrome and firefox - the link is alive and
registration works. Please try again
https://www.gridgain.com/resources/webinars/how-migrate-your-data-schema-apache-ignite
If you still can not access the page please email me and I'll register you
from our side.
Regards,
Kseniya
I've tried your code and got similar numbers (11s to write, 3s to read).
Profiler shows that serialization takes 90% of the streaming time (40% is
your WriteBinaryInternal method, the rest is Ignite internals)
Actual size of serialized object is 161 bytes, and
DataRegionMetris.TotalAllocatedSize
Hi Ivan,
Thank you for the confirmation.
In the link, I can see that the issue will be resolved in Ignite 3.0 version.
When will Ignite 3.0 be released? Is there any tentative date?
Regards,
Shravya Nethula,
BigData Developer,
[cid:2a5e6893-c131-4622-bebf-2deef20e1f50]
Hyderabad.
Hi Shravya,
It is a know issue. You can find more details in ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-6611
вт, 3 дек. 2019 г. в 07:54, Shravya Nethula <
shravya.neth...@aline-consulting.com>:
> Hi,
>
> I added a new column in an existing table using the following query:
>
If I run sql with out where condition on near caches, query will hit server
node correct ? It wont fetch from near cache in local node. Is this a true
statement?
Ex: select _key from cachename;
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
I've re-checked your case, and I think it's due to the known issue
https://issues.apache.org/jira/browse/IGNITE-11161
This is because of incorrect default in Thin Client. You need to change the
following:
ClientConfiguration cfg = new ClientConfiguration().setAddresses(HOST
+ ":" +
I want to start from a specific offset of the Kafka partition, it is possible
with KafkaStreamer?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
16 matches
Mail list logo