Pavel Tupitsyn created IGNITE-12720:
---
Summary: .NET: CachePeekMode is not treated as Flags
Key: IGNITE-12720
URL: https://issues.apache.org/jira/browse/IGNITE-12720
Project: Ignite
Issue Ty
Hello!
My suggestion is to use org.apache.ignite.configuration.IgniteConfiguration
and avoid introducing your own classes, etc. Cut out the middle man.
Regards,
--
Ilya Kasnacheev
чт, 27 февр. 2020 г. в 05:36, Sunny Chan, CLSA :
> Hi Ilya,
>
> For the IgniteConfiguration interface, do we pref
Just to make it clear, you prefer the option 1 in my suggestion? That is listed
out all the potential configurable for thread pool for each thread pools in
Ignite?
I do see that we have setDataStorageConfiguration where the parameters for data
storage is grouped together into a configuration ob
Currently have no idea about ODBC (what suite is assumed?). Comparison
success and failed NuGet runs shows that it always fails when
configured to run with Java 9 and higher. No answers so far, but some
questions I do not know answers for:
1. Does Ignite .NET work fine with java 9+?
2. Is it possib
Hi Ilya, didn't get what are you trying to say.
The problem I am facing is, my transaction is failing giving
TransactionOptimisticException. I do not have a reproducer for this project
and this does not happen frequently.
Transaction is failing during prepare phase. I had to open a debug port on
a
Sergey Chugunov created IGNITE-12721:
Summary: Validation of key length written to Distributed
Metastorage
Key: IGNITE-12721
URL: https://issues.apache.org/jira/browse/IGNITE-12721
Project: Ignite
Stanilovsky Evgeny created IGNITE-12722:
---
Summary: Get rid of
GridCacheDatabaseSharedManager#getPageMemoryForCacheGroup functionality.
Key: IGNITE-12722
URL: https://issues.apache.org/jira/browse/IGNITE-1272
Prasad,
Since optimistic transactions do not acquire key locks until prepare phase,
it is possible that the key value is concurrently changed before the
prepare commences. Optimistic exceptions is thrown exactly in this case and
suggest a user that they should retry the transaction.
Consider the
Hello!
I just noticed that the Java thin client throws the following internal
exceptions:
ClientProtocolError
ClientError
Since the classes are not public, there is no way to catch them properly in
user code.
Consider the recent changes, introduced by IGNITE-9410:
throw new ClientProtoc
Hi Alexey,
Key value is not getting changed concurrently, I am sure about it. The
cache for which I am getting the exception is kind of bootstrap data and it
changes very rarely. I have added retry logic in my code and it failed
every time giving the same error .
Every time if fails in GridDhtTx
Ivan, thank you, this is the answer:
> it always fails when configured to run with Java 9 and higher
Ignite can only be built with Java 8, and NuGet project includes Java build
step, which fails.
I've fixed TC settings to force Java 8 for `Platform .NET (NuGet)` project,
it seems to fix the issu
Nikolay Izhikov created IGNITE-12723:
Summary: Test refactoring. Explicit method to get MXBean instance
Key: IGNITE-12723
URL: https://issues.apache.org/jira/browse/IGNITE-12723
Project: Ignite
Amelchev Nikita created IGNITE-12724:
Summary: Command parser: do not skip commands with its own
specific arguments
Key: IGNITE-12724
URL: https://issues.apache.org/jira/browse/IGNITE-12724
Projec
Igniters,
I've prepared everything to start a vote.
Are we ready to go on?
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.8.0-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.0-rc1/
The following staging can be used for testing:
https://r
Folks,
It seems that we have a lack of knowledge at the platforms README file [1].
Should we also update it?
[1] https://github.com/apache/ignite/blob/master/modules/platforms/README.txt
On Wed, 26 Feb 2020 at 21:42, Denis Magda wrote:
>
> Igor Sapego, Igniters,
>
> I've been working on Ignite
Hello, Maxim!
All your links to ci.ignite.apache.org/ return 404 http code. It's okay?
чт, 27 февр. 2020 г. в 19:06, Maxim Muzafarov :
> Igniters,
>
>
> I've prepared everything to start a vote.
> Are we ready to go on?
>
>
> I have uploaded a release candidate to:
> https://dist.apache.org/repo
Stanilovsky Evgeny created IGNITE-12725:
---
Summary: Excessive backups performance suggestion.
Key: IGNITE-12725
URL: https://issues.apache.org/jira/browse/IGNITE-12725
Project: Ignite
Is
Thank you guys for your comments, Anton i understand your proposal but i
believe that highlighted case is rare and data safety is preferred. I fill the
ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-12725
>
>
>--- Forwarded message ---
>From: "Anton Vinogradov" < a...@
Hi Prasad.
nodeOrder is local counter used for updates ordering. The version is
incremented when lock is aquired for enlisted tx entry.
Are you sure where is no concurrent transaction on this replicated cache
which works significant time until committed ?
How long have you re-tried after getting
19 matches
Mail list logo
