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
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
<
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 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 Chugunov created IGNITE-13674:
Summary: Document Persistent store defragmentation
Key: IGNITE-13674
URL: https://issues.apache.org/jira/browse/IGNITE-13674
Project: Ignite
Issue
> Pavel
>
> On Fri, Oct 9, 2020 at 9:59 AM Sergey Chugunov
> wrote:
>
> > 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).
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 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
/main/java/org/apache/ignite/internal/managers/encryption/GridEncryptionManager.java#L710
>
> > 21 сент. 2020 г., в 14:37, Sergey Chugunov
> написал(а):
> >
> > Ivan,
> >
> > Sorry for some confusion, MM indeed is not a normal mode. What I was
> trying
> >
er were easy. Unfortunately I cannot suggest
> 100% better approaches so far. So, I should trust your vision.
>
> 2020-09-22 10:29 GMT+03:00, Sergey Chugunov :
> > Ivan,
> >
> > Checkpointer in Maintenance Mode is started and allows normal operations
> as
> > it may be nee
ffers from the cluster.
> > To recover node Ignite should locally change master key before join.
> >
> > Please, take a look into source code [1]
> >
> > [1]
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ig
special mode" approach we will get
> an additional flag in the code making the code more complex and
> fragile. Should not I worry about it?
>
> 2020-09-02 10:45 GMT+03:00, Sergey Chugunov :
> > Vladislav, Ivan,
> >
> > Thank you for your questions and suggestions.
rovide a possibility for client where he can make a
> > decision without a manual intervention?
> >
> > For example: Start node and manually agree with an option and after
> > automatically resolve conflict and back to topology as a stable node.
> >
> > On Mon, Aug 3
tly we already have 3 modes (inactive, read-only, read-write)
> and the subject is about one more. From the first glance it could be
> hard for a user to understand and use all modes properly. Do we really
> need all spectrum? Could we simplify things somehow?
>
> 2020-08-27 15:59 GM
>
> > 27 авг. 2020 г., в 10:25, Sergey Chugunov
> написал(а):
> >
> > 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:
> > Maintenanc
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 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 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 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
roperty.
> > > Potentially, we can put more effort throughout an Ignite 3.0 timeframe
> > and
> > > remove the property altogether. @Valentin Kulichenko
> > > , could you please suggest any alternate
> > naming?
> > >
> > > Btw, what are the
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
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 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
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
Hi Ivan,
I have an idea about suggested maintenance mode.
First of all, I agree with your ideas about discovery restrictions: node
should not join topology when performing defragmentation.
At the same time I haven't heard about requests for this mode from users,
so we don't know much about
Sergey Chugunov created IGNITE-12878:
Summary: Improve logging for async writing of Binary Metadata
Key: IGNITE-12878
URL: https://issues.apache.org/jira/browse/IGNITE-12878
Project: Ignite
Sergey Chugunov created IGNITE-12876:
Summary: Test to cover deadlock fix between checkpoint, entry
update and ttl-cleanup threads
Key: IGNITE-12876
URL: https://issues.apache.org/jira/browse/IGNITE-12876
Hello Sergey,
Your analysis looks valid to me, we definitely need to investigate this
deadlock and find out how to fix it.
Could you create a ticket and write a test that reproduces the issue with
sufficient probability?
Thanks!
On Mon, Mar 16, 2020 at 8:22 PM Sergey-A Kosarev
wrote:
>
Ivan,
I also don't think this issue is a blocker for 2.8 as it affects only
experimental functionality and only in special cases.
Removing key length limitations in MetaStorage seems more strategic
approach to me but depending on how we decide to approach it (as a local
fix or as part of 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
-1 Prohibit.
To me as a developer the situation when old but stable API is deprecated
with only experimental (thus unstable/unfinished) alternative is very far
from comfortable.
And from outside folks it may look like as a sign of immature processes
inside Ignite community (which is definitely
Sergey Chugunov created IGNITE-12646:
Summary: When DEBUG mode is enabled GridToStringBuilder may throw
java.util.ConcurrentModificationException
Key: IGNITE-12646
URL: https://issues.apache.org/jira/browse
> >
> > Kind regards
> > *Emmanouil Gkatziouras*
> > https://egkatzioura.com/ |
> > https://www.linkedin.com/in/gkatziourasemmanouil/
> > https://github.com/gkatzioura
> >
> >
> > On Fri, 24 Jan 2020 at 15:15, Sergey Chugunov >
> > wrote:
> >
?
--
Thank you,
Sergey Chugunov.
On Thu, Jan 23, 2020 at 5:32 PM Emmanouil Gkatziouras
wrote:
> Hi all!
>
> Yes It seems possible to get some free quota for integration tests on AWS
> [1] however most probably they are not gonna last forever.
>
> [1]
>
> https://aws.amazon.
Hello community,
Recently I published a new blog post on getting started with Apache Ignite
in AWS [1]. I tried to make my example as simple as possible while keeping
it usable.
Let me know if this post is useful for you.
I plan to write several follow-up posts about AWS-specific things but
Sergey Chugunov created IGNITE-12439:
Summary: More descriptive message in situation of
IgniteOutOfMemoryException, warning message if risk of IOOME is found
Key: IGNITE-12439
URL: https://issues.apache.org
Hi Mitchell,
I believe that research done by Anton is correct, and the root cause of the
OOME is proportion of memory occupied by metapages in data region. Each
cache started in data region allocates one or more metapages per
initialized partition so when you run your test with only one cache
, there are plenty of
them and we could figure out what to pick up next.
Anyway, thank you for your interest to our project and community!
[1] https://issues.apache.org/jira/browse/IGNITE-11312
--
Best regards,
Sergey Chugunov.
re to a reader. And yes,
> intuition about metadata registration is definitely an important,
> related but slightly different subject.
>
> ср, 16 окт. 2019 г. в 14:23, Sergey Chugunov :
> >
> > Ivan, thank you for documenting this functionality, agree with Pavel
> here.
> &g
Ivan, thank you for documenting this functionality, agree with Pavel here.
I think this document is a good starting point and contains a lot of
low-level details and great examples but from my perspective it doesn't
show how binary objects fit into a broader picture.
It worth adding higher-level
/IGNITE-12111
--
Best Regards,
Sergey Chugunov.
Sergey Chugunov created IGNITE-12111:
Summary: Cluster ID and tag: properties to identify the cluster
Key: IGNITE-12111
URL: https://issues.apache.org/jira/browse/IGNITE-12111
Project: Ignite
etween registration and metadata
> > usages
> > > > > > with
> > > > > > > such fast-fix?
> > > > > > >
> > > > > > > I believe, that we need to move it to distributed metastorage,
> > and
> > &
Denis,
Thanks for bringing this issue up, decision to write binary metadata from
discovery thread was really a tough decision to make.
I don't think that moving metadata to metastorage is a silver bullet here
as this approach also has its drawbacks and is not an easy change.
In addition to
Sergey Chugunov created IGNITE-11952:
Summary: Bug fixes and improvements in console utilities & test
fixes
Key: IGNITE-11952
URL: https://issues.apache.org/jira/browse/IGNITE-11952
Pro
Sergey Chugunov created IGNITE-11865:
Summary: FailureProcessor treats tcp-comm-worker as blocked when
it works on reestablishing connect to failed client node
Key: IGNITE-11865
URL: https://issues.apache.org
Sergey Chugunov created IGNITE-11743:
Summary: Stopping caches concurrently with node join may lead to
crash of the node
Key: IGNITE-11743
URL: https://issues.apache.org/jira/browse/IGNITE-11743
Sergey Chugunov created IGNITE-11739:
Summary: Refactoring of cache lifecycle and cache configuration
management code
Key: IGNITE-11739
URL: https://issues.apache.org/jira/browse/IGNITE-11739
Sergey Chugunov created IGNITE-11621:
Summary: Node is stuck in "No next node in topology" infinite loop
in special case.
Key: IGNITE-11621
URL: https://issues.apache.org/jira/browse/IG
Sergey Chugunov created IGNITE-11493:
Summary: Test CheckpointFreeListTest#testFreeListRestoredCorrectly
always fails in DiskCompression suite
Key: IGNITE-11493
URL: https://issues.apache.org/jira/browse
Sergey Chugunov created IGNITE-11459:
Summary: Possible dead code in TcpDiscoveryStatusCheckMessage flow
Key: IGNITE-11459
URL: https://issues.apache.org/jira/browse/IGNITE-11459
Project: Ignite
Sergey Chugunov created IGNITE-11348:
Summary: Ping node procedure may fail when another node leaves the
cluster
Key: IGNITE-11348
URL: https://issues.apache.org/jira/browse/IGNITE-11348
Project
Sergey Chugunov created IGNITE-11290:
Summary: History of server node IDs should be passed to new nodes
with NodeAddedMessage
Key: IGNITE-11290
URL: https://issues.apache.org/jira/browse/IGNITE-11290
Sergey Chugunov created IGNITE-11159:
Summary: Collections of 'start-on-join' caches and 'init-caches'
should be filtered
Key: IGNITE-11159
URL: https://issues.apache.org/jira/browse/IGNITE-11159
Anton,
As I understand from the IEP document policy was supposed to support two
timeouts: soft and hard, so here you're proposing a bit simpler
functionality.
Just to clarify, do I understand correctly that this feature when enabled
will auto-adjust blt on each node join/node left event, and
Sergey Chugunov created IGNITE-11011:
Summary: Initialize components with grid disco data when
NodeAddFinished message is received
Key: IGNITE-11011
URL: https://issues.apache.org/jira/browse/IGNITE-11011
Sergey Chugunov created IGNITE-10819:
Summary: Test
IgniteClientRejoinTest.testClientsReconnectAfterStart became flaky in master
recently
Key: IGNITE-10819
URL: https://issues.apache.org/jira/browse/IGNITE
Sergey Chugunov created IGNITE-10809:
Summary:
IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3 fails
in master
Key: IGNITE-10809
URL: https://issues.apache.org/jira/browse/IGNITE
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5600
Ignite 10374
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10374-1
Alternatively you can review
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5578
IGNITE_DISABLE_WAL_DURING_REBALANCING turned on by default, test for race
between checkpointer and affinity change added
You can merge this pull request into a Git repository
Eduard,
This algorithm looks much easier but could you clarify some edge cased
please?
If I understand correctly when there is a continuous flow of updates to the
page already transferred to receiver checkpointer will write this page to
the log file over and over again. Do you see here any risks
+1
Plus this dedicated list should be properly documented in wiki, mentioning
it in How to Contribute [1] or in Make Teamcity Green Again [2] would be a
good idea.
[1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
[2]
Sergey Chugunov created IGNITE-10409:
Summary: ExchangeFuture should be in charge on cancelling
rebalancing process
Key: IGNITE-10409
URL: https://issues.apache.org/jira/browse/IGNITE-10409
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5468
IGNITE-10374 if rebalance isn't restarted no need to disable already â¦
â¦disabled WAL
You can merge this pull request into a Git repository by running:
$ git pull https
Sergey Chugunov created IGNITE-10374:
Summary: Node doesn't own rebalanced partitions on rebalancing
finished
Key: IGNITE-10374
URL: https://issues.apache.org/jira/browse/IGNITE-10374
Project
? In my mind it is
possible that we have a good bunch of tests that cover the same code and
could be replaced with just a single test.
In the ideal world we would even determine the minimal set of tests to
cover our codebase and remove excessive.
--
Best regards,
Sergey Chugunov.
On Thu, Nov 15
Sergey Chugunov created IGNITE-10153:
Summary: [TC Bot] Implement tests running time report
Key: IGNITE-10153
URL: https://issues.apache.org/jira/browse/IGNITE-10153
Project: Ignite
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5047
IGNITE-9957 Updates count was reduced to speed up the test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Sergey Chugunov created IGNITE-9958:
---
Summary: Optimize execution time of
CacheContinuousQueryVariationsTest
Key: IGNITE-9958
URL: https://issues.apache.org/jira/browse/IGNITE-9958
Project: Ignite
Sergey Chugunov created IGNITE-9957:
---
Summary: Optimize execution time of BinaryMetadataUpdatesFlowTest
Key: IGNITE-9957
URL: https://issues.apache.org/jira/browse/IGNITE-9957
Project: Ignite
1 - 100 of 417 matches
Mail list logo
