Hi Sumit,
Did you have a chance to very the build by the link I sent to you?
Might be you can share a reproducer so I can verify it my own?
Thanks,
Mike.
пн, 9 мар. 2020 г. в 09:26, Mikhail :
> Hello,
>
> Looks like it was fixed in GridGain Community edition:
>
Thanks Dennis.
I am sorry if this is obvious and I am missing it but I fail to see how one
would go about getting the metadata information such as the java type for
each each field in a binaryobject for a table defined by a queryentity.
On Fri, Mar 13, 2020 at 12:26 AM Denis Magda wrote:
>
Hi Ashish,
Yes, a transaction will be rolled back if it closed without a successful
commit.
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Kumar,
Ignite need to sync memory and disk time to time, if you write rate is
bigger than disk speed that means Ignite will never able to sync memory and
disk, that's why it starts to throttle your writes.
So ignite added 1.6ms delay to each write, to be more accurate, not for each
writes,
Hi,
Follow the recommendations for persistence tuning here:
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/persistence-tuning
How much data is being saved to disk? Are you able to adjust the rate of
data flow and see whether it makes a difference. Can you try using
Hi,
Can you attach a reproducer along w/exact version #s and we will take a
look.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Follow the recommendations for persistence tuning here:
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/persistence-tuning
How much data is being saved to disk? Are you able to adjust the rate of
data flow and see whether it makes a difference. Can you try using
sorry, but it's public user list, it's not a paid helpdesk, it's important to
keep conversations public, to allow other people google answers and resolve
similar problems.
I believe you problem can be described without hostnames, IP addresses,
passwords or other sensitive information.
--
Sent
Closing is enough and an explicit rollback is not necessary.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Dominik,
You don't need to configure thread pools manually, you should do this only
if you have some particular problem and think that this can be resolved by
changing pool sizes.
Ignite in 95% of cases automatically configure correct pools' sizes.
So you didn't understand it correctly:
The
Hi Mikhail,
Thanks for the quick response.
Sure..will provide more details if it is ensured that this thread doesn't go
public.
Please confirm.
Thanks,
Sriveena
-Original Message-
From: Mikhail
Sent: 13 March 2020 23:50
To: user@ignite.apache.org
Subject: RE: Security threat due to H2
Hi Sriveena,
I do no quite understand your concerns, Apache Ignite is just a java
application which you can be run under any user account with restricted
privileges.
Could you please describe you question in more detail?
>Which means user can execute any kind of system functions like filewrite,
I'm not sure, because the final overhead depends on the object sizes. There
is a buffer for CQ, which stores 1000 entries by default, but you can
decrease it using property IGNITE_CONTINUOUS_QUERY_SERVER_BUFFER_SIZE
Evgenii
вт, 18 февр. 2020 г. в 18:09, narges saleh :
> Hi Evgeni,
>
> There
Hello Sriveena,
We're looking into this and keep you posted on a solution.
-
Denis
On Fri, Mar 13, 2020 at 2:47 AM Sriveena Mattaparthi <
sriveena.mattapar...@ekaplus.com> wrote:
> Please suggest on ways to override the ignite configurations to start h2
> database user with a custom user who
Hi,
AI 2.7.6 doesn't contain a bug with aggregation of cache hits/misses.
I don't sure that described problem is related with IGNITE-3495 [1].
So it makes sense to file an issue.
[1] https://issues.apache.org/jira/browse/IGNITE-3495
On Thu, Mar 12, 2020 at 8:21 PM Dominik Przybysz wrote:
>
>
It’s this: https://issues.apache.org/jira/browse/IGNITE-10577
It’s fixed in 2.8 but the workaround is to include ignite-rest-http as an
additional module.
Regards,
Stephen
> On 13 Mar 2020, at 10:07, Juili Bandgar wrote:
>
> Getting below error while creating ignite v2.7.6 cluster in
HI Ilya,
Thank you for the invite. I will be very happy to debug and develop for
Ignite.
For the issue mentioned, I will debug a bit more and then file a ticket,
regards,
Veena.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Getting below error while creating ignite v2.7.6 cluster in kubernetes
1.16.6:
Let me know what's wrong.
[09:59:07]__
[09:59:07] / _/ ___/ |/ / _/_ __/ __/
[09:59:07] _/ // (7 7// / / / / _/
[09:59:07] /___/\___/_/|_/___/ /_/ /___/
[09:59:07]
Please suggest on ways to override the ignite configurations to start h2
database user with a custom user who has low privileges.
Thanks,
Sriveena
From: Sriveena Mattaparthi
Sent: 12 March 2020 15:42
To: user@ignite.apache.org
Subject: Security threat due to H2 admin privileges for Ignite
Hi,
Hi,
I read the thread pool documentation (
https://apacheignite.readme.io/docs/thread-pools) but I need more
information which thread pools I should configure/tune for my setup.
I have 2 server nodes (partitioned cache) and some clients (without near or
local chaches) which add cache entries via
Hi All - I see this message in the logs
[2020-03-12 15:23:29,896][INFO
][comcastprod-1-StoreFlushWorker-7][PageMemoryImpl] Throttling is applied to
page modifications [*percentOfPartTime=0.54*, markDirty=8185 pages/sec,
checkpointWrite=14893 pages/sec, estIdealMarkDirty=8182 pages/sec,
For below code snippet, if exception occurs do I need to rollback the
transaction? Or closing the transaction takes care of it?
try (Transaction tx = transactions.txStart()) {
Integer hello = cache.get("Hello");
if (hello == 1)
cache.put("Hello", 11);
cache.put("World",
Hi All - I see this message in the logs
[2020-03-12 15:23:29,896][INFO
][comcastprod-1-StoreFlushWorker-7][PageMemoryImpl] Throttling is applied to
page modifications [*percentOfPartTime=0.54*, markDirty=8185 pages/sec,
checkpointWrite=14893 pages/sec, estIdealMarkDirty=8182 pages/sec,
23 matches
Mail list logo
