Hello!
I have indeed committed a fix of TLSv1.3 into master, but I don't think we
should rush it in 2.7.5. It is a large change and its implications are not
obvious.
It would be much better to merge just the temporary fix int 2.7.5, what is
https://issues.apache.org/jira/browse/IGNITE-11860 -
hi, Sergey.
What's the purpose for ignite-sys-cache updates still be available ?
thanks !
Hello Igniters!
I'm working on cluster read-only mode [1] feature. In this mode cluster
will be available only for read operations, all data modification
operations in user caches will be rejected
with
Sergey,
I think it will be a very useful feature for Ignite's users, my +1 here.
Can you clarify what kind of updates are written to the ignite-sys-cache?
Should we also allow writes to the DistributedMetaStorage and if not why?
On Thu, 30 May 2019 at 19:55, Dmitriy Pavlov wrote:
>
> ++1 from
Folks,
The PR [2] has been updated and comments [1] have been addressed.
If you're interested in this feature, please join the review [3] and discussion.
[1] https://issues.apache.org/jira/browse/IGNITE-10619
[2] https://github.com/apache/ignite/pull/5619
[3]
Ilya K.,
could you please confirm that issue with SSL is fixed now? I saw a
notification from some JIRA.
Can we proceed with new RC?
чт, 23 мая 2019 г. в 15:54, Pavel Tupitsyn :
> -1 (binding)
>
> NuGet packages for Ingite.NET were not built as described in [1].
>
> This is automated on
++1 from my side. This mode seems to be very useful for Ignite users.
чт, 30 мая 2019 г. в 19:47, Sergey Antonov :
> Hello Igniters!
>
> I'm working on cluster read-only mode [1] feature. In this mode cluster
> will be available only for read operations, all data modification
> operations in
Igniters,
I've looked through Nikita's changes and I think for the current issue
[1] we should not allow the existence of MOVING partitions in the
cluster (it must be stable) to run the lightweight PME on BLT node
leave event occurred to achieve truly unlocked operations and here are
my thoughts
Hello Igniters!
I'm working on cluster read-only mode [1] feature. In this mode cluster
will be available only for read operations, all data modification
operations in user caches will be rejected
with ClusterReadOnlyModeCheckedException. This feature could be helpfull
for maintenance works
Nikolay Izhikov created IGNITE-11881:
Summary: Spark Data Fram example not working
Key: IGNITE-11881
URL: https://issues.apache.org/jira/browse/IGNITE-11881
Project: Ignite
Issue Type:
Dmitriy Pavlov created IGNITE-11880:
---
Summary: [TC Bot] Configurable notifications by build
parameters/suite IDS & names
Key: IGNITE-11880
URL: https://issues.apache.org/jira/browse/IGNITE-11880
Dmitriy Pavlov created IGNITE-11879:
---
Summary: [TC Bot] Don't reject contribution because of
ExitCodes/Timeouts if the same failure is present in master
Key: IGNITE-11879
URL:
Stepachev Maksim created IGNITE-11878:
-
Summary: Rebuild index skips MOVING partitions when historical re
balance
Key: IGNITE-11878
URL: https://issues.apache.org/jira/browse/IGNITE-11878
Hi Igniters!
I found the solution for how to run IgniteConfigVariationsAbstractTest. I
removed garbage injection [1] and static variable [2].
Now assigning of VariationsTestsConfig proceeds in constructor class which
is created dynamically [3].
But I faced with the problem that a certain amount
13 matches
Mail list logo
