Definitely a +1 from me for moving the CLI tooling to a separate module.
As for the autocompletion - can you elaborate how it works? Will it require
to run an additional tool when a user hits TAB? Or will it generate an
autocompletion file during the build? Will we require an install step for
Hello Maxim, folks,
ср, 6 мая 2020 г. в 21:01, Maxim Muzafarov :
> We won't do performance analysis on the production environment. Each
> time we need performance analysis it will be done on a test
> environment with verbose logging enabled. Thus I suggest moving these
> changes to a separate
> affecting cluster availability and consistency. That ticket reminds 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
> co
Nikita, Igniters,
I left a few comments on the tool itself in the PR.
However, I would like to reiterate and discuss why a user would prefer to
use the profiling tool over tracing? Profiling tool only captures very
high-level details of the operations (a single cache operation, for
example), and
nd serve client requests. Entries for not
> owning anymore partitions expire according to configuration.
>
> Actually, I have an idea. My guess is that "rebalancing" is a smarter
> and better approach than waiting for expiration. Am I right?
>
> 2020-07-21 15:31 GMT+03:00, Alex
Hello Nikolay,
> > 10. Question - CRC is read in two places encryptionFileIO and
> filePageStore - what should we do with this?
>
> filePageStore checks CRC of the encrypted page. This required to confirm
> the page not corrupted on the disk.
> encryptionFileIO checks CRC of the decrypted
evidence:
> > >
> >
> https://stackoverflow.com/questions/62902640/apache-ignite-cacherebalancemode-is-not-respected-by-nodes
> > >
> > > On Mon, Jul 20, 2020 at 8:26 PM Alexey Goncharuk
> > >
> > > wrote:
> > >
> > >> Igniters,
> &
Stan,
Currently we never build indexes one-by-one - we always use a cache data
row visitor which either updates all indexes (see IndexRebuildFullClosure)
or updates a set of all indexes that need to catch up (see
IndexRebuildPartialClosure). GIven that, I do not see any need for
per-index rebuild
Igniters,
I would like to run the idea of deprecating and probably ignoring the NONE
rebalance mode by the community. It's in the removal list for Ignite 3.0
[1], but it looks like it still confuses and creates issues for users [2].
What about deprecating it in one of the next releases and even
t; чт, 26 нояб. 2020 г. в 13:18, Ivan Daschinsky :
>
> > Alexey, is it possible to manage call at 16:00 MSK?
> >
> > чт, 26 нояб. 2020 г. в 12:30, Alexey Goncharuk <
> alexey.goncha...@gmail.com
> > >:
> >
> > > Hi Ivan,
> > >
> > &
пн, 23 нояб. 2020 г. в 13:28, Alexey Goncharuk :
> Thanks, Ivan,
>
> Another protocol for group membership worth checking out is RAPID [1] (a
> recent one). Not sure though if there are any available implementations for
> it already.
>
> [1] https://www.usenix.org/system/f
Folks, let's have the call on Friday, Nov 27th at 18:00 MSK? We can use the
following waiting room link:
https://zoom.us/j/99450012496?pwd=RWZmOGhCNWlRK0ZpamdOOTZsYTJ0dz09
Let me know if this time works for everybody.
ср, 25 нояб. 2020 г. в 16:42, Alexey Goncharuk :
> Folks,
>
> I've
ariant -- in the morning.
>
> ср, 25 нояб. 2020 г. в 20:10, Alexey Goncharuk >:
>
> > Folks, let's have the call on Friday, Nov 27th at 18:00 MSK? We can use
> the
> > following waiting room link:
> > https://zoom.us/j/99450012496?pwd=RWZmOGhCNWlRK0ZpamdOOTZsYTJ0dz09
gt; > > > > should be validated against the latest version
> and
> > > > local
> > > > > > > > mapping
> > > > > > > > > > > should
> > > >
gt; end of story.
>
> On Tue, Nov 24, 2020 at 6:25 PM Alexey Goncharuk <
> alexey.goncha...@gmail.com>
> wrote:
>
> > Folks, I think this is a reasonable request. I thought about this when I
> > was drafting the IEP, but hesitated to add these types right away.
> &g
Dear Ignite Community,
I have uploaded a release candidate of the following extension modules:
ignite-camel-ext
ignite-flink-ext
ignite-flume-ext
ignite-jms11-ext
ignite-kafka-ext
ignite-mqtt-ext
ignite-pub-sub-ext
ignite-rocketmq-ext
ignite-storm-ext
ignite-twitter-ext
ignite-zeromq-ext
The
The vote is closed now.
Vote result: Vote passed with 5 "+1" votes (3 binding and 2 non-binding
votes), no "0" and no "-1" votes.
+1 Votes:
Denis Magda (binding)
Saikat Maitra (binding)
Andrey Gura (binding)
Kirill Tkalenko
Konstantin Orlov
Vote thread
:
> >
> >> Alex,
> >>
> >> Should we create a dedicated ticket for the documentation changes or
> can we
> >> reuse IGNITE-13634? As a bare minimum, we need to update maven
> artifacts'
> >> names and versions:
> >>
> >>
&
s sense to me.
> > > > >>>
> > > > >>> вт, 10 нояб. 2020 г. в 18:47, Sergey Chugunov <
> > > > sergey.chugu...@gmail.com>:
> > > > >>>
> > > > >>>> Igniters,
> > > >
Good,
I think we have an intermediate agreement on the scope and significance of
the changes we want to make. I suggest creating separate discussion streams
and calls for each of the suggested topics so that:
- It is clear for the community what is the motivation of the stream
(this
Igniters,
I think we a bit overdue for releasing already migrated extension modules
which were removed in Ignite 2.9. As Saikat mentioned, I suggest releasing
the following modules:
ignite-flink-ext
ignite-flume-ext
ignite-pub-sub-ext
ignite-zeromq-ext
ignite-twitter-ext
ignite-rocketmq-ext
I support having a single vote for all the extensions. Mikhail, do you mind
releasing the rest of the modules together with spring-boot? If you do, I
can take care of them but looks like this will be a separate vote, though.
чт, 19 нояб. 2020 г. в 10:55, Petr Ivanov :
> No 11 separate votes, but
Following up the Ignite 3.0 scope/development approach threads, this is a
separate thread to discuss technical aspects of the IEP.
Let's reiterate one more time on the questions raised by Ivan and also see
if there are any other thoughts on the IEP:
- *Whether to deploy metastorage on a
an Daschinsky :
> >
> >>
> >>
> >> -- Forwarded message -
> >> От: Ivan Daschinsky
> >> Date: чт, 19 нояб. 2020 г. в 13:02
> >> Subject: Re: IEP-61 Technical discussion
> >> To: Alexey Goncharuk
> >>
&g
> etcd (see raft/node.go) contains some heartbeats mechanism etc.
> > I agree with you, this seems not to be a huge deal to port.
> >
> > чт, 19 нояб. 2020 г. в 16:13, Alexey Goncharuk <
> alexey.goncha...@gmail.com
> > >:
> >
> >> Ivan,
> >>
> >&
e extensions as independent as possible.
> >
> > Doubt if we can do it for each module.
> > We have, ignite-hibernate_4.2, ignite-hibernate_5.1 modules that
> attached to specific hibernate version by their name.
> >
> >
> >> 11 нояб. 2020 г., в 11:19, Alex
t;> component wiring mechanics, general methods to approach core components
> >> such as exchange/communication
> >> to avoid code mess like we have in ExchangeFuture with all these custom
> >> callbacks for each component, interfaces like
> >> Partiti
Folks,
I want to bump up this discussion and slightly change the format suggested
by Nikita. I dot think it is correct to gather any information related to
the user environment. However, can we collect just the fact of some of the
Ignite APIs/subsystems being used with no user information
Hello folks,
I think we should start both 2.9.1 and 2.10. In practice, maintenance
release contains only critical and usability bugfixes (for example, I would
include this ticket [1] to include in 2.9.1 as it prevents users from using
tracing) and is released much faster than a minor release.
Igniters,
I wanted to pitch a rather radical idea regarding the Ignite 3.0
development which has occurred to me some time ago.
We already have several IEPs targeted to Ignite 3.0 which imply major
changes to the codebase (the change in replication protocol and thus
transactions, change in binary
APIs
> and internal structure is overwhelming
> >
> > Maybe we should relax a bit requirements for Ignite3?
> > Maybe we should move step by step and make Ignite3 with new
> configuration than Ignite4 with new transactions, etc?
> >
> >> 2 нояб. 2020 г., в 13:1
bugs and issues that can be fixed in 2.x without breaking
> backward
> > compatibility.
> > We have many users who are happy with the 2.x with all it’s issues.
> >
> > > 2 нояб. 2020 г., в 14:09, Anton Vinogradov написал(а):
> > >
> > > Alexey,
> > >
> >
iev <
> zaleslaw@gmail.com>
> > > > wrote:
> > > >
> > > >> Let's discuss the possible planning dates for feature freeze for
> 2.10,
> > > for
> > > >> example? Do you have any plans or ideas?
> > > >>
> >
y thoughts or objections?
> > > > Are interfaces good enough to be merged within the current ticket?
> > > >
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13748
> > > >
> > > > On Thu, Nov 26, 2020 at 2:33 PM Юрий
> &
Folks,
I updated the IEP to contain the missing pieces; actually, most of the
questions here were covered by the text. Please let me know if there is
something still missing or unclear.
чт, 31 дек. 2020 г. в 12:48, Alexey Goncharuk :
> Mikhail and Igniters,
>
> Thanks for your
Ivan,
My concern with the concept of a user completing the future returned from
Ignite public API is that it is unclear how to interpret this action (this
backs Val's message).
Let's say a user started a compute with fut = compute.runAsync(task); and
now calls fut.complete(someVal); Does this
Hello Alexander, Igniters,
I support the suggestion, we need to work out some ground rules to have a
consistent naming convention. Agree with having at most one component per
project module - this requirement may turn out to be too strict in the
future, but now it seems reasonable and may help us
ient as affinity or schema make no sense without the table.
> > Processor is just helper-component of the Service that routes messages,
> > executes async tasks, manages subscriptions and implements some secondary
> > functions.
> >
> > On Tue, Mar 30, 2021 at 11:24 AM
e. What are the benefits of this ?
>
> ср, 31 мар. 2021 г. в 12:16, Alexey Goncharuk >:
>
> > Alexei,
> >
> > I had the same opinion regarding the internal package, but we still need
> to
> > somehow distinguish between public and internal classes in the
> ignite-uti
Hello Denis, Andrey, Igniters,
Why don't we take a step further in improving the security model in Ignite
3? I think it would be great to have a default implementation of
user-role-permission model in Ignite to be on par with security models of
widely-used databases. This will complement
be free to change them without any compatibility contract" -
> let's mark such classes with a special annotation like @Internal, will it
> work for you ?
>
>
>
> ср, 31 мар. 2021 г. в 15:10, Alexey Goncharuk >:
>
> > This won't work with the Java Jigsaw module sys
I support the idea. All issues notifications are also sent to
iss...@ignite.apache.org so one can subscribe to this list in order to
track the created tickets. The notifications trash the devlist archive UI
and make it extremely difficult to navigate.
вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev
Aleksei,
> The method should always report root cause, in your example it will be
> B-, no matter which module API is called
I may be wrong, but I doubt this will be usable for an end-user. Let's
imagine that the same root exception was raised in different contexts
resulting in two outcomes.
Alexey Goncharuk created IGNITE-1945:
Summary: Get rid of keepDeserialized flag in configuration
Key: IGNITE-1945
URL: https://issues.apache.org/jira/browse/IGNITE-1945
Project: Ignite
Alexey Goncharuk created IGNITE-1450:
Summary: Excessive exceptions are printed out during cache/node
stop
Key: IGNITE-1450
URL: https://issues.apache.org/jira/browse/IGNITE-1450
Project: Ignite
Alexey Goncharuk created IGNITE-1553:
Summary: Optimize transaction prepare step when store is enabled
Key: IGNITE-1553
URL: https://issues.apache.org/jira/browse/IGNITE-1553
Project: Ignite
Alexey Goncharuk created IGNITE-1537:
Summary: Near TX prepare future is completed early for LOCAL cache
Key: IGNITE-1537
URL: https://issues.apache.org/jira/browse/IGNITE-1537
Project: Ignite
Alexey Goncharuk created IGNITE-2104:
Summary: Marshalling fails with Binary marshaller if class
hierarchy contains duplicate field names
Key: IGNITE-2104
URL: https://issues.apache.org/jira/browse/IGNITE
Alexey Goncharuk created IGNITE-2065:
Summary: Need to get rid of 'Portable' word in internals
Key: IGNITE-2065
URL: https://issues.apache.org/jira/browse/IGNITE-2065
Project: Ignite
Alexey Goncharuk created IGNITE-2325:
Summary: Assertion in optimistic prepare future on client node
during server node restart when near cache is enabled.
Key: IGNITE-2325
URL: https://issues.apache.org/jira
Alexey Goncharuk created IGNITE-2329:
Summary: Get rid of Iterator for selected keys in NIO server
Key: IGNITE-2329
URL: https://issues.apache.org/jira/browse/IGNITE-2329
Project: Ignite
Alexey Goncharuk created IGNITE-2012:
Summary: Add support for ConcurrentLinkedQueue type in .NET/C++
Key: IGNITE-2012
URL: https://issues.apache.org/jira/browse/IGNITE-2012
Project: Ignite
Alexey Goncharuk created IGNITE-1987:
Summary: Make binary marshaller default
Key: IGNITE-1987
URL: https://issues.apache.org/jira/browse/IGNITE-1987
Project: Ignite
Issue Type: Bug
Alexey Goncharuk created IGNITE-3305:
Summary: Ignite does not wait for dynamically created caches in
SYNC rebalance mode
Key: IGNITE-3305
URL: https://issues.apache.org/jira/browse/IGNITE-3305
Alexey Goncharuk created IGNITE-3307:
Summary: IllegalMonitorStateException in IgniteLockExample
Key: IGNITE-3307
URL: https://issues.apache.org/jira/browse/IGNITE-3307
Project: Ignite
Alexey Goncharuk created IGNITE-2396:
Summary: Dynamic cache changes are not tracked by service processor
Key: IGNITE-2396
URL: https://issues.apache.org/jira/browse/IGNITE-2396
Project: Ignite
Alexey Goncharuk created IGNITE-2589:
Summary: Value is not loaded from store in pessimistic transaction
when near cache is enabled
Key: IGNITE-2589
URL: https://issues.apache.org/jira/browse/IGNITE-2589
Alexey Goncharuk created IGNITE-2645:
Summary: Assertion error in ATOMIC cachce for invokeAll and cache
store
Key: IGNITE-2645
URL: https://issues.apache.org/jira/browse/IGNITE-2645
Project
Alexey Goncharuk created IGNITE-2707:
Summary: SkipStore flag is not overridden for a transaction entry
Key: IGNITE-2707
URL: https://issues.apache.org/jira/browse/IGNITE-2707
Project: Ignite
Alexey Goncharuk created IGNITE-2434:
Summary: Ignite updates cache store even if EntryProcessor did not
update cache entry
Key: IGNITE-2434
URL: https://issues.apache.org/jira/browse/IGNITE-2434
Alexey Goncharuk created IGNITE-2821:
Summary: Design and implement keepBinary flag for IgniteRDD
Key: IGNITE-2821
URL: https://issues.apache.org/jira/browse/IGNITE-2821
Project: Ignite
Alexey Goncharuk created IGNITE-2784:
Summary: Optimize continuous query remote listener invocation
Key: IGNITE-2784
URL: https://issues.apache.org/jira/browse/IGNITE-2784
Project: Ignite
Alexey Goncharuk created IGNITE-2941:
Summary: Add getOrStart method to ignition
Key: IGNITE-2941
URL: https://issues.apache.org/jira/browse/IGNITE-2941
Project: Ignite
Issue Type: Bug
Alexey Goncharuk created IGNITE-3077:
Summary: IgniteRDD data frame does not handle object fields
Key: IGNITE-3077
URL: https://issues.apache.org/jira/browse/IGNITE-3077
Project: Ignite
Alexey Goncharuk created IGNITE-3086:
Summary: Cache store validation should be done only when write
entry is enlisted
Key: IGNITE-3086
URL: https://issues.apache.org/jira/browse/IGNITE-3086
Alexey Goncharuk created IGNITE-3469:
Summary: Get rid of deprecated APIs and entities
Key: IGNITE-3469
URL: https://issues.apache.org/jira/browse/IGNITE-3469
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-3607:
Summary: Send non-filtered continuous query notifications in one
message per client
Key: IGNITE-3607
URL: https://issues.apache.org/jira/browse/IGNITE-3607
Alexey Goncharuk created IGNITE-3616:
Summary: Drop failed nodes from topology after a configured timeout
Key: IGNITE-3616
URL: https://issues.apache.org/jira/browse/IGNITE-3616
Project: Ignite
Alexey Goncharuk created IGNITE-3671:
Summary: Ignite profiling interface
Key: IGNITE-3671
URL: https://issues.apache.org/jira/browse/IGNITE-3671
Project: Ignite
Issue Type: Wish
Alexey Goncharuk created IGNITE-3471:
Summary: Do not send previous value to client node for invoke()
when possible
Key: IGNITE-3471
URL: https://issues.apache.org/jira/browse/IGNITE-3471
Project
Alexey Goncharuk created IGNITE-3479:
Summary: Global transaction ordering
Key: IGNITE-3479
URL: https://issues.apache.org/jira/browse/IGNITE-3479
Project: Ignite
Issue Type: Sub-task
Alexey Goncharuk created IGNITE-3477:
Summary: Rework offheap approach
Key: IGNITE-3477
URL: https://issues.apache.org/jira/browse/IGNITE-3477
Project: Ignite
Issue Type: Task
Alexey Goncharuk created IGNITE-3478:
Summary: Transactional SQL
Key: IGNITE-3478
URL: https://issues.apache.org/jira/browse/IGNITE-3478
Project: Ignite
Issue Type: Task
Alexey Goncharuk created IGNITE-3500:
Summary: Generate expiry event in GridCacheMapEntry#checkExpired()
Key: IGNITE-3500
URL: https://issues.apache.org/jira/browse/IGNITE-3500
Project: Ignite
Alexey Goncharuk created IGNITE-3499:
Summary: GridCacheReplicatedFullApiMultithreadedSelfTest1 is
commented
Key: IGNITE-3499
URL: https://issues.apache.org/jira/browse/IGNITE-3499
Project
Alexey Goncharuk created IGNITE-3484:
Summary: MVCC for cache data structures
Key: IGNITE-3484
URL: https://issues.apache.org/jira/browse/IGNITE-3484
Project: Ignite
Issue Type: Sub-task
Alexey Goncharuk created IGNITE-3464:
Summary: Possible race between partition exchange and
prepare/finish requests
Key: IGNITE-3464
URL: https://issues.apache.org/jira/browse/IGNITE-3464
Project
Alexey Goncharuk created IGNITE-3456:
Summary: Make sure EntryProcessor is always running on a OWNING
partition
Key: IGNITE-3456
URL: https://issues.apache.org/jira/browse/IGNITE-3456
Project
Alexey Goncharuk created IGNITE-3399:
Summary: Support primitive type names in QueryEntity
Key: IGNITE-3399
URL: https://issues.apache.org/jira/browse/IGNITE-3399
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-4551:
Summary: Reconsider cache key/value peer class loading
Key: IGNITE-4551
URL: https://issues.apache.org/jira/browse/IGNITE-4551
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-4335:
Summary: Implement cluster ACTIVE/INACTIVE state
Key: IGNITE-4335
URL: https://issues.apache.org/jira/browse/IGNITE-4335
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-4337:
Summary: Introduce persistence interface to allow build reliable
persistence plugins
Key: IGNITE-4337
URL: https://issues.apache.org/jira/browse/IGNITE-4337
Alexey Goncharuk created IGNITE-4534:
Summary: Implement offheap eviction policies based on page memory
Key: IGNITE-4534
URL: https://issues.apache.org/jira/browse/IGNITE-4534
Project: Ignite
Alexey Goncharuk created IGNITE-4535:
Summary: Add option to store deserialized values on-heap
Key: IGNITE-4535
URL: https://issues.apache.org/jira/browse/IGNITE-4535
Project: Ignite
Alexey Goncharuk created IGNITE-4536:
Summary: Update metrics for new offheap storage
Key: IGNITE-4536
URL: https://issues.apache.org/jira/browse/IGNITE-4536
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-4861:
Summary: Export rebalance metrics and state as MBeans
Key: IGNITE-4861
URL: https://issues.apache.org/jira/browse/IGNITE-4861
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-4876:
Summary: Tests: node stop should wait for cluster to see actual
topology version
Key: IGNITE-4876
URL: https://issues.apache.org/jira/browse/IGNITE-4876
Alexey Goncharuk created IGNITE-4985:
Summary: Atomic cache operations acquire backpressure semaphore on
retries
Key: IGNITE-4985
URL: https://issues.apache.org/jira/browse/IGNITE-4985
Project
Alexey Goncharuk created IGNITE-4986:
Summary: .NET possible affinity resource leak
Key: IGNITE-4986
URL: https://issues.apache.org/jira/browse/IGNITE-4986
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-4989:
Summary: Assertion error in BPlusTree#finishTail
Key: IGNITE-4989
URL: https://issues.apache.org/jira/browse/IGNITE-4989
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-5061:
Summary: Add ability to enable and disable rebalancing per-node
Key: IGNITE-5061
URL: https://issues.apache.org/jira/browse/IGNITE-5061
Project: Ignite
Alexey Goncharuk created IGNITE-4820:
Summary: Implement parallel indexes for BPlusTree
Key: IGNITE-4820
URL: https://issues.apache.org/jira/browse/IGNITE-4820
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-5872:
Summary: Replace standard java maps for partition counters to more
effective data structures
Key: IGNITE-5872
URL: https://issues.apache.org/jira/browse/IGNITE-5872
Alexey Goncharuk created IGNITE-5890:
Summary: Add estimated time to rebalance completion and time to
rebalance start to MXBean
Key: IGNITE-5890
URL: https://issues.apache.org/jira/browse/IGNITE-5890
Alexey Goncharuk created IGNITE-5915:
Summary: Add more clear WAL mode documentation and print a warning
when NONE mode is used
Key: IGNITE-5915
URL: https://issues.apache.org/jira/browse/IGNITE-5915
Alexey Goncharuk created IGNITE-6030:
Summary: Allow enabling persistence per-cache
Key: IGNITE-6030
URL: https://issues.apache.org/jira/browse/IGNITE-6030
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-5757:
Summary: RENT partition state is set before exchange is completed
Key: IGNITE-5757
URL: https://issues.apache.org/jira/browse/IGNITE-5757
Project: Ignite
Alexey Goncharuk created IGNITE-5774:
Summary: Print more information about long partition release future
Key: IGNITE-5774
URL: https://issues.apache.org/jira/browse/IGNITE-5774
Project: Ignite
Alexey Goncharuk created IGNITE-5772:
Summary: Race between WAL segment rollover and concurrent log
Key: IGNITE-5772
URL: https://issues.apache.org/jira/browse/IGNITE-5772
Project: Ignite
Alexey Goncharuk created IGNITE-5797:
Summary: Add latency tracing capability for cache operations
Key: IGNITE-5797
URL: https://issues.apache.org/jira/browse/IGNITE-5797
Project: Ignite
601 - 700 of 980 matches
Mail list logo
