Hi, Ivan
It looks fine now. Thanks much for quick fix!
--
Sergey
On 14.11.2022 20:21, Ivan Daschinsky wrote:
Dear Igniters!
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0.rc1
42% 2022-11-11 13:11 d3a45643 tests/__init__.py
Thanks,
--
Sergey Korotkov
On 11.11.2022 20:40, Ivan Daschinsky wrote:
Dear Igniters!
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0
Hello Igniters,
Looks like it's a flaky test and it's ok now:
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetCoreLinux/6564445?buildTab=tests=CancellationTest.TestTask=true
Thanks,
--
Sergey
On 18.08.2022 09:38, ignitetc...@sbt-ignite-dev.ru wrote:
Hi
Hello Petr,
On 03.08.2022 15:39, Petr Ivanov wrote:
Hi, Sergey.
What bot?
I mean this one: https://mtcga.ignite.apache.org/
But the problem was resolved for me already.
Thanks,
--
Sergey
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911)
d you please give me more?
My teamcity user name is: serge.korotkov
Thanks,
--
Sergey
Hello Igniters,
I would like to prepare the IEP for some improved loading testing
framework for Ignite.
Would you please give me a write access to
https://cwiki.apache.org/confluence
Thanks,
--
Sergey Korotkov
Hello, All
I’d like to join the community and contribute to the Ignite.
Would you please grant me the contributors permissions in Jira. My account
is serge.korotkov
Thanks,
--
Sergey
+1 for option2 (only @Nullable)
Best regards,
Sergey Kosarev.
чт, 13 янв. 2022 г. в 13:25, Alexander Polovtcev :
> Dear Igniters,
>
> In this thread
> <https://lists.apache.org/thread/2l50swqd1dymf2qjgrb4wqrbmwjtj02f> we've
> discussed possible approaches to using nul
He joined the
> >>>>>>> community in 2016.
> >>>>>>> He participated in the development of Ignite 1.x, 2.x and he is
> >>>>>>> actively
> >>>>>>> working on a new Apache Ignite 3.0 release.
> >>>>>>>
> >>>>>>> Being a committer enables easier contribution to the project since
> >>>>>>> there
> >>>>>>> is no need to go via the patch submission process. This should
> >>> enable
> >>>>>>> better productivity.
> >>>>>>>
> >>>>>>> Please join me in welcoming Vlad, and congratulating him on the
> >> new
> >>>>>>> role
> >>>>>>> in the Apache Ignite Community.
> >>>>>>>
> >>>>>>> -Val
> >>>>>>>
> >>>>>
> >>>>> --
> >>>>> Sincerely yours, Ivan Daschinskiy
> >>>>>
> >>>>
> >>>> --
> >>>>
> >>>> Best regards,
> >>>> Ivan Pavlukhin
> >>>>
>
--
BR, Sergey Antonov
I setup 2.11 instead of 2.10.
Now RunAllNightly for "ignite-2.11" branch will be run on TeamCity.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hello Igniters,
I would like to start a discussion on evolving IEP-73 [1]. Now it covers a
narrow topic about components dependencies but it makes sense to cover in
the IEP a broader question: how different components should be initialized
to support different modes of an individual node or a
Hi,
Patch is ready - no blockers, please review.
Best regards,
Sergey Kosarev.
чт, 6 мая 2021 г. в 13:57, Sergey :
> Hi, Igniters.
> I've came across JVM crush recently. And after investigations I've found
> Binary(Off)HeapOutputStream does not check correctly for overflow of the
&
regards,
Sergey Kosarev.
Kirill,
Indeed current behavior of force rebuild API seems broken, we need to fix
it, +1 from me too.
BTW would it be useful to allow rebuilding individual indices?
On Wed, Mar 24, 2021 at 6:20 PM ткаленко кирилл
wrote:
> Hello!
>
> What do you mean by the implementation plan?
> Implement
Sergey Chugunov created IGNITE-14382:
Summary: Network module API structuring
Key: IGNITE-14382
URL: https://issues.apache.org/jira/browse/IGNITE-14382
Project: Ignite
Issue Type: Sub
Sergey Chugunov created IGNITE-14323:
Summary: Messaging naming unification
Key: IGNITE-14323
URL: https://issues.apache.org/jira/browse/IGNITE-14323
Project: Ignite
Issue Type: Sub-task
Sergey Chugunov created IGNITE-14297:
Summary: API to unregister HandlerProvider from network module
Key: IGNITE-14297
URL: https://issues.apache.org/jira/browse/IGNITE-14297
Project: Ignite
Sergey Chugunov created IGNITE-14296:
Summary: Classe
Key: IGNITE-14296
URL: https://issues.apache.org/jira/browse/IGNITE-14296
Project: Ignite
Issue Type: Sub-task
Reporter
Sergey Chugunov created IGNITE-14295:
Summary: Message interface to be introduced
Key: IGNITE-14295
URL: https://issues.apache.org/jira/browse/IGNITE-14295
Project: Ignite
Issue Type
Sergey Chugunov created IGNITE-14231:
Summary: IGNITE_ENABLE_FORCIBLE_NODE_KILL flag is not supported in
inverse connection request scenario
Key: IGNITE-14231
URL: https://issues.apache.org/jira/browse/IGNITE
Sergey Chugunov created IGNITE-14184:
Summary: API for off-line update of configuration
Key: IGNITE-14184
URL: https://issues.apache.org/jira/browse/IGNITE-14184
Project: Ignite
Issue
Sergey Chugunov created IGNITE-14183:
Summary: Cross-root validation
Key: IGNITE-14183
URL: https://issues.apache.org/jira/browse/IGNITE-14183
Project: Ignite
Issue Type: Sub-task
Sergey Chugunov created IGNITE-14182:
Summary: NamedList remove improvements
Key: IGNITE-14182
URL: https://issues.apache.org/jira/browse/IGNITE-14182
Project: Ignite
Issue Type: Sub
Sergey Chugunov created IGNITE-14181:
Summary: Configuration to support arrays of primitive types
Key: IGNITE-14181
URL: https://issues.apache.org/jira/browse/IGNITE-14181
Project: Ignite
Sergey Chugunov created IGNITE-14180:
Summary: Storage notification API
Key: IGNITE-14180
URL: https://issues.apache.org/jira/browse/IGNITE-14180
Project: Ignite
Issue Type: Sub-task
Sergey Chugunov created IGNITE-14178:
Summary: Asynchronous Storage API
Key: IGNITE-14178
URL: https://issues.apache.org/jira/browse/IGNITE-14178
Project: Ignite
Issue Type: Sub-task
Sergey Chugunov created IGNITE-14155:
Summary: Test IgniteClusterIdTagTest.testInMemoryClusterTag is
flaky on TC
Key: IGNITE-14155
URL: https://issues.apache.org/jira/browse/IGNITE-14155
Project
Sergey Kadaner created IGNITE-14063:
---
Summary: Error: Failed to get java major version (unknown
'java.version' format) [ver=14-ea]
Key: IGNITE-14063
URL: https://issues.apache.org/jira/browse/IGNITE-14063
Hi, Petr.
Now I have access.
Thanks!
пн, 25 янв. 2021 г. в 11:28, Petr Ivanov :
> Hi, Sergey.
>
>
> Check you permissions, please.
>
> > On 24 Jan 2021, at 21:00, Sergey D wrote:
> >
> > Hi Igniters,
> >
> > I want to start work on a ticke
--
*Best regards, Sergey.*
Sergey Kadaner created IGNITE-14031:
---
Summary: Add Docker images based on Java 11
Key: IGNITE-14031
URL: https://issues.apache.org/jira/browse/IGNITE-14031
Project: Ignite
Issue Type
Sergey Kadaner created IGNITE-14014:
---
Summary: Insufficient documentation and examples for
ignite-spring-boot-autoconfigure-ext
Key: IGNITE-14014
URL: https://issues.apache.org/jira/browse/IGNITE-14014
Sergey Uttsel created IGNITE-13929:
--
Summary: Don't print sensitive information in logs by default
Key: IGNITE-13929
URL: https://issues.apache.org/jira/browse/IGNITE-13929
Project: Ignite
Sergey Uttsel created IGNITE-13917:
--
Summary: (err) Failed to dump debug information:
java.lang.NullPointerException at
dumpLongRunningOperations0(GridCachePartitionExchangeManager.java:2256)
Key: IGNITE-13917
<
valentin.kuliche...@gmail.com> wrote:
> Thanks, Sergey! Looks good to me.
>
> -Val
>
> On Tue, Dec 15, 2020 at 12:12 AM Sergey Chugunov <
> sergey.chugu...@gmail.com>
> wrote:
>
> > Val,
> >
> > Your comments make total sense to me, I've fixed them and update
,
Sergey Chugunov
On Sat, Dec 12, 2020 at 3:20 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Sergey,
>
> Thanks for doing this.
>
> It looks like PR #5 is already under review, so I guess it will be merged
> soon. I would really love to see that, b
Hello Igniters,
I would like to present two pull requests [1], [2] with basic
implementation of IEP-55 for Unified Configuration [3] and IEP-63 REST API
for Unified Configuration [4].
The main goal of these PRs is to present and discuss a new approach for
preparing and managing Ignite
Sergey Uttsel created IGNITE-13731:
--
Summary: High contention on
GridCachePartitionExchangeManager.ExchangeFutureSet#values.
Key: IGNITE-13731
URL: https://issues.apache.org/jira/browse/IGNITE-13731
Sergey Chugunov created IGNITE-13718:
Summary: REST API to manage configuration
Key: IGNITE-13718
URL: https://issues.apache.org/jira/browse/IGNITE-13718
Project: Ignite
Issue Type: Sub
Sergey Chugunov created IGNITE-13712:
Summary: Simple application integrating dynamic configuration
Key: IGNITE-13712
URL: https://issues.apache.org/jira/browse/IGNITE-13712
Project: Ignite
maller subset of changes will leave Ignite 3.0 in a transient state
> > with people being too afraid to move to it because there are more major
> > breaking changes scheduled.
> >
> > пт, 13 нояб. 2020 г. в 18:28, Alexey Zinoviev :
> >
> >> I'm -1 for creating a n
Igniters,
I thought over Friday meeting ideas and concerns and summarized them in
these three points:
1. *Components design unification approach.* New proposed components
will be developed by different contributors, but they need to be unified
and should integrate with each other
Sergey Uttsel created IGNITE-13678:
--
Summary: Extend test coverage for persistence files dir and WAL
page snapshot records compression
Key: IGNITE-13678
URL: https://issues.apache.org/jira/browse/IGNITE-13678
Sergey Chugunov created IGNITE-13674:
Summary: Document Persistent store defragmentation
Key: IGNITE-13674
URL: https://issues.apache.org/jira/browse/IGNITE-13674
Project: Ignite
Issue
Hi Pavel,
Thanks, I looked through your comments and fixed them. Could you please
check one more time?
On Fri, Oct 9, 2020 at 10:27 AM Pavel Tupitsyn wrote:
> Hello Sergey,
>
> I went over the public API changes briefly and left some minor comments on
> GitHub
>
> Thanks,
Max,
Thanks for spotting this, great catch!
Zhenya, could you please file a ticket of at least Critical priority?
On Fri, Oct 9, 2020 at 9:24 AM Zhenya Stanilovsky
wrote:
>
>
> Thanks Maxim, the test is correct no need for removal.
> I checked 2.9 too, but looks it all ok there. I will take a
Hello Igniters,
I'm getting closer to finishing main ticket for Maintenance Mode feature
[1] and now working on test fixes (most likely test modifications are
needed).
So I would like to ask for a review of my pull request [2] to discuss the
code earlier. Test status is pretty good so I expect
Sergey Chugunov created IGNITE-13558:
Summary: GridCacheProcessor should implement better
parallelization when restoring partition states on startup
Key: IGNITE-13558
URL: https://issues.apache.org/jira
Sergey Chugunov created IGNITE-13557:
Summary: Logging improvements for PDS memory restore process
Key: IGNITE-13557
URL: https://issues.apache.org/jira/browse/IGNITE-13557
Project: Ignite
Sergey Stronchinskiy created IGNITE-13556:
-
Summary: .NET: Thin client: Transactions support async
Key: IGNITE-13556
URL: https://issues.apache.org/jira/browse/IGNITE-13556
Project: Ignite
Sergey Chugunov created IGNITE-13550:
Summary: CLI command to execute maintenance action in corrupted
PDS scenario
Key: IGNITE-13550
URL: https://issues.apache.org/jira/browse/IGNITE-13550
Hello Ignite dev community,
As internal implementation of Maintenance Mode [1] is getting closer to
finish I want to discuss one more thing: user-facing API (I will use
control utility for examples) for managing it.
What should be managed?
When a node enters MM, it may start some automatic
via system property. Do you think of getting rid of this
property and passing new master key name to encryption manager with
maintenance parameters? In terms of original IEP it is parameters passed
with MaintenanceRecord.
--
Thanks!
On Mon, Sep 21, 2020 at 3:20 PM Nikolay Izhikov wrote:
> Hello,
Ivan,
If you come up with any ideas that may make this feature better, don't
hesitate to share them!
Thank you!
On Tue, Sep 22, 2020 at 11:27 AM Ivan Pavlukhin wrote:
> Sergey,
>
> Thank you for your answer. While I am not happy with the proposed
> approach but things nev
% guarantee that no communication with
other nodes will happen.
It is important to note that GridRestProcessor is started normally as we
need it to connect to the node via control utility.
On Mon, Sep 21, 2020 at 7:04 PM Ivan Pavlukhin wrote:
> Sergey,
>
> > From the code complexity per
ell with reasonable amount of
refactoring.
Does it make sense to you?
On Sun, Sep 6, 2020 at 8:08 AM Ivan Pavlukhin wrote:
> Sergey,
>
> Thank you for your answer!
>
> Might be I am looking at the subject from a different angle.
>
> > I think of a node in MM as an almost
.{sh|bat}) is a good fit for our current APIs and ways
to interact with the node.
Does it sound reasonable to you?
Thank you!
[1] https://issues.apache.org/jira/browse/IGNITE-13366
On Tue, Sep 1, 2020 at 2:07 PM Ivan Pavlukhin wrote:
> Sergey,
>
> Actually, I missed
ter/modules/core/src/main/java/org/apache/ignite/cluster/ClusterState.java
On Mon, Aug 31, 2020 at 12:32 PM Ivan Pavlukhin wrote:
> Hi Sergey,
>
> Thank you for bringing attention to that important subject!
>
> My note here is about one more cluster mode. As far as I know
> curren
/confluence/display/IGNITE/IEP-53%3A+Maintenance+Mode
[2]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-47:+Native+persistence+defragmentation
On Thu, Aug 27, 2020 at 11:01 AM Nikolay Izhikov
wrote:
> Hello, Sergey!
>
> Thanks for the proposal.
> Let’s have IEP for this feature.
Hello Igniters,
I want to start a discussion about new supporting feature that could be
very useful in many scenarios where persistent storage is involved:
Maintenance Mode.
*Summary*
Maintenance Mode (MM for short) is a special state of Ignite node when node
doesn't serve user requests nor
Sergey Chugunov created IGNITE-13367:
Summary: meta --remove command usage improvements
Key: IGNITE-13367
URL: https://issues.apache.org/jira/browse/IGNITE-13367
Project: Ignite
Issue
Sergey Chugunov created IGNITE-13366:
Summary: Prohibit unconditional automatic deletion of data files
if WAL was disabled prior to node's shutdown
Key: IGNITE-13366
URL: https://issues.apache.org/jira/browse
Sergey Uttsel created IGNITE-13365:
--
Summary: GridCacheDatabaseSharedManager.releaseHistoryForExchange
may throw AssertionError when WALMode.NONE is used.
Key: IGNITE-13365
URL: https://issues.apache.org/jira
Sergey Uttsel created IGNITE-13353:
--
Summary: DynamicCacheChangeBatch invokes partition validation for
all caches
Key: IGNITE-13353
URL: https://issues.apache.org/jira/browse/IGNITE-13353
Project
Hi, alamar and akuznetsov!
Could you please review my PR https://github.com/apache/ignite/pull/7912
Regards,
Sergey
пн, 8 июн. 2020 г. в 19:21, Moldachev Sergey (Jira) :
> Moldachev Sergey created IGNITE-13133:
> -
>
>
Congratulations, Sergey!
сб, 18 июл. 2020 г., 0:24 Andrey Mashenkov :
> Congratulations, Sergey.
>
> пт, 17 июл. 2020 г., 15:06 Вячеслав Коптилин :
>
> > Hi,
> >
> > Well deserved! Keep it up, Sergey!
> >
> > Thanks,
> > S.
> >
> > пт
Sergey Chugunov created IGNITE-13260:
Summary: Improve javadoc documentation for FilePageStore
abstraction.
Key: IGNITE-13260
URL: https://issues.apache.org/jira/browse/IGNITE-13260
Project
Sergey Uttsel created IGNITE-13256:
--
Summary: IgniteCacheNearRestartRollbackSelfTest.testRestarts
(Cache restarts) (Regression) became flaky
Key: IGNITE-13256
URL: https://issues.apache.org/jira/browse/IGNITE
Sergey Uttsel created IGNITE-13244:
--
Summary: Transaction commit completes successfully if partition is
lost on commit phase
Key: IGNITE-13244
URL: https://issues.apache.org/jira/browse/IGNITE-13244
Sergey Chugunov created IGNITE-13239:
Summary: Document APIs to view and change Cluster ID and Tag
Key: IGNITE-13239
URL: https://issues.apache.org/jira/browse/IGNITE-13239
Project: Ignite
Sergey Uttsel created IGNITE-13217:
--
Summary: Partition loss detection is not working if a dynamic
cache is not started on a client.
Key: IGNITE-13217
URL: https://issues.apache.org/jira/browse/IGNITE-13217
Sergey Stronchinskiy created IGNITE-13214:
-
Summary: .NET different behavior when using TransactionScope and
ITransactions.Start
Key: IGNITE-13214
URL: https://issues.apache.org/jira/browse/IGNITE-13214
Sergey Uttsel created IGNITE-13210:
--
Summary: Parameterized tests in ServiceDeploymentProcessIdSelfTest
class have different name each time
Key: IGNITE-13210
URL: https://issues.apache.org/jira/browse/IGNITE
Sergey Chugunov created IGNITE-13212:
Summary: Peer class loading does not work for Scan Query
Key: IGNITE-13212
URL: https://issues.apache.org/jira/browse/IGNITE-13212
Project: Ignite
Sergey Chugunov created IGNITE-13190:
Summary: Core defragmentation functions
Key: IGNITE-13190
URL: https://issues.apache.org/jira/browse/IGNITE-13190
Project: Ignite
Issue Type: Sub
Sergey Chugunov created IGNITE-13189:
Summary: Maintenance mode switch and defragmentation process
initialization
Key: IGNITE-13189
URL: https://issues.apache.org/jira/browse/IGNITE-13189
Project
Sergey Chugunov created IGNITE-13185:
Summary: API to change Cluster Tag and notify about change of
Cluster Tag
Key: IGNITE-13185
URL: https://issues.apache.org/jira/browse/IGNITE-13185
Project
Sergey Chugunov created IGNITE-13182:
Summary: Document Cluster ID and Tag feature
Key: IGNITE-13182
URL: https://issues.apache.org/jira/browse/IGNITE-13182
Project: Ignite
Issue Type
Hi!
Please uncheck java-9+ profile in the maven profiles in idea. It could help
you.
вс, 21 июн. 2020 г., 22:05 Guru Stron :
> Dear Igniters,
>
> I filled instructions from
> https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup - checked
> out project, opened it in Intellij IDEA
use TC Bot for getting a visa.
[1]
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/7924/head=Latest
[2] https://ibb.co/m8rW74L
--
BR, Sergey Antonov
Guys, could someone review my patch, please?
вт, 16 июн. 2020 г. в 10:50, Sergey Antonov :
> Hello, Igniters!
>
> I'd like to get a review of the ticket [1]. The patch is ready [2].
> Can someone look at it, please?
>
> [1] https://issues.apache.org/jira/browse/IGNITE
Hello, Igniters!
I'd like to discuss with you changes for *ignite-spring-data*. You can read
about motivation and the idea in [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13152
<https://issues.apache.org/jira/browse/IGNITE-13152#>
--
Regards,
Sergey
gt;
> > TcpCommunicationSpi#forceClientToServerConnections -- false by default,
> > true if the new mode needs to be enabled.
> >
> > Let me know your thoughts.
> >
> > -Val
> >
> > On Wed, Jun 10, 2020 at 4:10 PM Denis Magda wrote:
> >
> &
Hello, Igniters!
I'd like to get a review of the ticket [1]. The patch is ready [2].
Can someone look at it, please?
[1] https://issues.apache.org/jira/browse/IGNITE-13144
[2] https://github.com/apache/ignite/pull/7924
--
BR, Sergey Antonov
Moldachev Sergey created IGNITE-13152:
-
Summary: Introduce spring-data repository configuration properties
Key: IGNITE-13152
URL: https://issues.apache.org/jira/browse/IGNITE-13152
Project: Ignite
Sergey Chugunov created IGNITE-13151:
Summary: Checkpointer code refactoring
Key: IGNITE-13151
URL: https://issues.apache.org/jira/browse/IGNITE-13151
Project: Ignite
Issue Type: Sub
Hello, Igniters!
I'd like to get a review of the ticket [1]. The patch is ready [2].
Can someone look at it, please?
[1] https://issues.apache.org/jira/browse/IGNITE-13138
[2] https://github.com/apache/ignite/pull/7918/files
--
BR, Sergey Antonov
Igniters, the patch [1] is ready for the review.
Can someone look at it, please?
[1] https://github.com/apache/ignite/pull/7924
ср, 10 июн. 2020 г. в 23:42, Sergey Antonov :
> Pavel, Alexei thank you for your replays.
>
> > is this one special in some way?
> Yes. We have two &
ike we do not need methods *readOnly *and *inactive*.
I agree.
ср, 10 июн. 2020 г. в 21:17, Alexei Scherbakov :
> But it looks like we do not need methods *readOnly *and *inactive*.
> What is the point in adding them ?
>
>
> ср, 10 июн. 2020 г. в 21:05, Alexei Scherbakov <
>
han comparing with
specific enum's value.
I'm going to do that on the ticket [1].
Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-13144
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-13144:
---
Summary: Add attribute methods to ClusterState enum
Key: IGNITE-13144
URL: https://issues.apache.org/jira/browse/IGNITE-13144
Project: Ignite
Issue
Sergey Chugunov created IGNITE-13143:
Summary: Persistent store defragmentation
Key: IGNITE-13143
URL: https://issues.apache.org/jira/browse/IGNITE-13143
Project: Ignite
Issue Type: New
Sergey Kalashnikov created IGNITE-13142:
---
Summary: SQL constraint not null added on key prevents correct
inserts
Key: IGNITE-13142
URL: https://issues.apache.org/jira/browse/IGNITE-13142
Sergey Chugunov created IGNITE-13141:
Summary: Modify .NET counterpart of IgniteCluster to include
functionality of Cluster ID and tag
Key: IGNITE-13141
URL: https://issues.apache.org/jira/browse/IGNITE-13141
scenarios will stop working
without additional logic like sending data through router node. As far as I
know client-client connectivity is involved in p2p class deployment
scenarios, does anyone know about other cases?
--
Thanks,
Sergey Chugunov
On Wed, Jun 3, 2020 at 5:37 PM Denis Magda w
Hello Igniters,
I've created the PR for this ticket with related changes in
ignite-spring-data-2.0 and ignite-spring-data-2.2, also I added some
examples in ignite-examples.
I didn't find a maintainer of this component. Who can review my PR?
With best regards,
Sergey.
Sergey Antonov created IGNITE-13138:
---
Summary: Add REST tests for the new cluster state change API
Key: IGNITE-13138
URL: https://issues.apache.org/jira/browse/IGNITE-13138
Project: Ignite
Moldachev Sergey created IGNITE-13133:
-
Summary: Add integration with QuerydslPredicateExecutor for
spring-data integrations
Key: IGNITE-13133
URL: https://issues.apache.org/jira/browse/IGNITE-13133
Of course I meant ticket [1] increased cluster stability in situation of
blinking network.
[1] https://issues.apache.org/jira/browse/IGNITE-7163
On Mon, Jun 8, 2020 at 1:51 PM Sergey Chugunov
wrote:
> Vladimir,
>
> Adding to what Alexey has said I remember that cases of short-ter
s me of
> those notorious issues that would fire once a week or month under specific
> configuration settings. So, I would not touch the code that fixes the issue
> unless @Alexey Goncharuk or @Sergey Chugunov
> confirms that it's safe to do. Also, there should
> be a test fo
1 - 100 of 1083 matches
Mail list logo
