Hello, Ivan.
I’m +1 for your proposal.
> 25 дек. 2020 г., в 13:14, Ivan Daschinsky написал(а):
>
> Hi folks!
>
> Since we already have a separate repo for thin-clients [1], [2]
> I'd like to propose some improvements in development process/
>
> 1. We should simplify and automate unit tests ru
Great news!
Congrats to all the community with one more release!
Yaroslav and Maxim thanks for driving it!
> 29 дек. 2020 г., в 15:17, Yaroslav Molochkov
> написал(а):
>
> The Apache Ignite Community is pleased to announce the release of
> Apache Ignite 2.9.1.
>
> Apache Ignite [1] is a memor
tps://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
>>>>>> [2]
>>>>>>
>>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases
Hello, Igniters.
Currently, in case of usage .Net platform client it’s required for the user to
explicitly register each custom type.
```
_marsh = new Marshaller(new BinaryConfiguration
{
TypeConfigurations = new List
{
new BinaryTypeConfiguration(typeof (Address)),
new B
ent type names to the same typeId
>> with a custom name or id mapper.
>>
>> This proposal says we should always put Foo.Bar.Person from .NET to the
>> Java mapping,
>> in the hope that there is a class with that name in Java, which is a very
>> rare use case.
&g
>
> As I understand, you insist on changing the default behavior, is this
> correct?
>
>
> On Tue, Jan 12, 2021 at 9:51 PM Nikolay Izhikov wrote:
>
>> Hello, Igor, Pavel.
>>
>> Thanks for the feedback
>>
>>> Agree with Pavel, this shou
both ways:
> all type names become shared across all platforms in MarshallerContextImpl.
>
>
> On Wed, Jan 13, 2021 at 11:21 AM Nikolay Izhikov
> wrote:
>
>> Hello, Pavel
>>
>> My proposal is the following:
>>
>> *When Ignite configured with FQN NameM
p breaks,
> because "foo.bar.Aa" and "foo.bar.BB" have the same hash code,
> and DuplicateTypeIdException is thrown by Ignite.
>
> On Wed, Jan 13, 2021 at 1:54 PM Nikolay Izhikov wrote:
>
>> Hello, Pavel.
>>
>>> Imagine that some Ignite
e inside ExecuteJavaTask or Java service call
> - FQN mapper is used (default or explicit)
> - There is no BinaryIdMapper on .NET or Java side
>
>
> On Wed, Jan 13, 2021 at 6:30 PM Nikolay Izhikov wrote:
>
>> Pavel.
>>
>>> Yes, but they are registered separa
therwise, multiple agents will be doing duplicate
>> work). In
>> the current design, the consumer will not be able to differentiate
>> primary/backup updates. Moreover, even if we wrote such flags to WAL,
>> the
>> consumer would need to process backup records a
+1
чт, 10 янв. 2019 г. в 19:09, Anton Vinogradov :
> +1
>
> On Thu, Jan 10, 2019 at 6:02 PM Alexey Kuznetsov
> wrote:
>
> > +1 to drop support of Scala 2.10 in Ignite 2.8.
> >
> >
> > On Thu, Jan 10, 2019 at 9:59 PM Yuriy Babak wrote:
> >
> > > Hi Igniters,
> > >
> > > What do you think about t
Hello, Igniters.
Please, note, Github merges without squashing by default.
Use "squash and merge" option in drop down list.
ср, 9 янв. 2019 г. в 14:25, Anton Vinogradov :
> Seems, the next step is to integrate tcbot with github.
> It will be nice to have an opportunity to ask the bot to check P
Hello, Maxim.
> IGNITE-11129
Do we have reproducer for this ticket?
WalRecord will be encrypted only if record class
implements WalRecordCacheGroupAwarei.e it contains some cache data that
should be protected with encryption.
Please, look into private boolean needEncryption(WALRecord rec).
Switch
th blocks by 16 bytes for
> encryption data + 2 bytes for padding in AES_WITH_PADDING mode.
> The current implementation works for dataSize = 20: ( (20 / 16) + 2 ) *
> 16. " 20 / 16 = 1." , Are we lost one block for 4 bytes? Or is it fine?
>
>
>
>
>
>
t;> It's my mistake. You're right.
>> Thanks for answering.
>>
>> чт, 31 янв. 2019 г. в 17:50, Nikolay Izhikov :
>>
>>> Maxim,
>>>
>>> > I suppose the AES algorithm work with blocks by 16 bytes for encryption
>>> data + 2 bytes
Hello, Denis.
Thank you for this discussion.
I have a few notes:
1. Is it possible to change the list of deployed resources in runtime via
built-in DeploymentSPI implementations?
Can I add or remove jar to(from) class-path without node(cluster) restart?
2. Can we update service dependencies via
Hello, Maxim.
+1 from me for migrating to checkstyle.
Oleg, there is plugin for IDEA with 2mln downloads -
https://plugins.jetbrains.com/plugin/1065-checkstyle-idea
I propose do the following:
1. Migrate current checks to checkstyle.
2. Apply checks to all Ignite modules. Currently, only core m
r.
пн, 11 февр. 2019 г., 11:16 Petr Ivanov mr.wei...@gmail.com:
> Is build configuration Inspections [Core] meant to transform into single
> all-modules check build configuration (without module subdivision)?
>
>
> > On 11 Feb 2019, at 11:02, Nikolay Izhikov wrote:
> >
> &
tions it was going to be build configuration per module.
>
>
>
>
> > On 11 Feb 2019, at 11:24, Nikolay Izhikov wrote:
> >
> > Hello, Petr.
> >
> > Are you saying that we have not single build task? And each module builds
> > when it required? If yes, th
ll formed javadocs).
> >
> > [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite
> >
> > пн, 11 февр. 2019 г. в 11:38, Nikolay Izhikov :
> >>
> >> Petr, we should have 1 configuration for project, may be 1 config
hase).
> >
> > Please, note currently enabled checks are:
> > - list.isEmpty() instead of list.size() == 0
> > - unused imports
> > - missing @Override
> > - sotred modifiers checks (e.g. pulic static final ..)
> > - redundunt suppersion checks
>
u please
> outline the benefits you see of failing compilation and skipping tests
> execution if inspections detect a problem?
>
> чт, 14 февр. 2019 г. в 14:14, Nikolay Izhikov :
> >
> > Hello, Ivan.
> >
> > > Requirements for a prototype code are not the
Ivan.
Please, use the quote right: "We should avoid any discussions *this time*."
This means - "We should *fix the issue* as quick as we can and discuss
correct improvement after"
Should we live this long with wrong deprecation?
I don't think so.
пн, 18 февр. 2019 г. в 11:58, Павлухин Иван :
>
hing.
>
> But it is quite interesting for me personally where our community
> declared actions which should be taken against troublesome
> contributions.
>
> пн, 18 февр. 2019 г. в 12:11, Nikolay Izhikov :
> >
> > Ivan.
> >
> > Please, use the quote right: &q
Hello, Denis.
> This XML may contain task descriptors, but I couldn't find any
documentation on this format.
> This information can be provided in simple JAR files with the same file
structure.
I support you proposal. Let's:
1. Support jar files instead of gar.
2. Write down documentation about
Hello, Pavel.
Please, clarify.
What exactly your new compatibility framework should check?
I know at lease 2 compatible subsystem in Ignite that should work with
previous versions:
1. Persistence.
2. Thin client.
> A new version of Ignite has released and a developer should update
compatibility
patibility tests against all detected old
> versions.
> > > The number of versions to test is controlled by a property.
> > > Some versions can be excluded for particular test suite or the user can
> > > bound it using versions range.
> > > In all of these cases, t
Hello, Ivan.
May be I miss some mail - if yes, can you repeat it.
What is advantages of migration from junit 4 to 5?
Why we should do it?
пн, 25 февр. 2019 г. в 16:33, Ivan Fedotov :
> Ivan,
> That is my thoughts according to your questions.
>
> 1. I tried to implement test suits with JUnit4 co
+1
чт, 7 марта 2019 г., 20:00 Denis Magda :
> Igniters,
>
> How about releasing Ignite 2.8 from the master - creating the release
> branch on Monday-Tuesday, as fast as we can? Don't want us to delay with
> Java 11 improvements, they are really helpful from the usability
> standpoint.
>
> After t
ue for inspections RedundantSuppression and
> > >> > SizeReplaceableByIsEmpty (all code style checks [5]). Propose to
> merge
> > >> > without them.
> > >> > 2) Checkstyle plugin has it's own maven profile and enabled by
> > >> &g
; >> > > absence of `emergency 2.8` is a problem for the user.
> > > >> > >
> > > >> > > Is it still our rush and 'highway or no way'? I was in the hope
> it
> > > is
> > > >> > gone.
> > > >> > >
>
Hello, Vladimir.
Thanks for the detailed answer.
I think your statement doesn't differs with Dmitry statement much.
Do we have committer who merge without confidence in patch content?
If yes, they should stop to do it.
пн, 18 мар. 2019 г. в 12:00, Anton Vinogradov :
> Huge +1 to "We should stre
- does not matter. And a
> > > committer will be responsible to take a final decision.
> > >
> > > There will no any kind of automatic merge.
> > >
> > > If a maintainer is on vacation, some other contributor may come to the
> > > thread an
Guys.
We should fix the SYSTEM_WORKER_TERMINATION once and for all.
Seems, we have ten or more "cluster shutdown" bugs with this subsystem
since it was introduced.
Should we disable it by default in 2.7.5?
пн, 25 мар. 2019 г. в 13:04, Pavel Kovalenko :
> Hi Roman,
>
> I think this InvalidParti
is unable to work anymore.
> >
> > Unexpected cluster shutdown with reasons in logs that failure handlers
> > provide is better than hanging. So answer is NO. We mustn't disable
> > failure handlers.
> >
> > On Mon, Mar 25, 2019 at 2:47 PM Roman Shtykh
>
or example, isn't it?
> 100% agree with you: overcome, but not hide.
>
> > How user can know it's a bug? Where this bug should be reported?
> As far as I see from user-list messages, our users are qualified enough to
> provide necessary information from their cluster-
Hello, Alex.
We also have suspend and resume operations.
I think we should support them
вт, 26 марта 2019 г., 22:07 Sergey Kozlov :
> Hi
>
> Looks like I missed something but why we need OP_TX_CLOSE operation?
>
> Also I suggest to reserve a code for SAVEPOINT operation which very useful
> to un
Hello, Maxim.
Thanks for the update.
Please, let me know when PR will be ready.
I will do the review.
В Вт, 02/04/2019 в 14:52 +0300, Maxim Muzafarov пишет:
> Ivan,
>
> I tend to agree with you. Let's keep changes as an internal Apache Ignite API.
>
> Igniters,
>
> I need your support by revi
Hello, Anton.
Thanks for the PoC.
> finds correct values according to LWW strategy
Can you, please, clarify what is LWW strategy?
В Ср, 03/04/2019 в 17:19 +0300, Anton Vinogradov пишет:
> Ilya,
>
> This is impossible due to a conflict between some isolation levels and
> get-with-consistency ex
Hello, Dmitriy.
Any news about release?
Do you need assistance with it?
вт, 2 апр. 2019 г. в 20:04, Dmitriy Pavlov :
> Ivan P., it seems the netty approach you've proposed works well. Thank you.
>
> Igniters, please take a look at following fix:
> https://github.com/apache/ignite/pull/6384
> It
Hello, Igniters.
Current master is broken with this commit:
https://github.com/apache/ignite/commit/c23f6b0c11df9c0a9cd55e87e0f9b4c6771ce43f
Andrew, please, fix it.
```
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on
project ignit
Hello, Ignite.
Finally, I've implemented this ticket! :)
Jira - https://issues.apache.org/jira/browse/IGNITE-9113
PR - https://github.com/apache/ignite/pull/6388
Tests seems to be OK.
Anyone wants to take a look?
В Чт, 09/08/2018 в 16:41 +0300, Alexey Goncharuk пишет:
> Once the OS gave us the
Hooray!
Congrats, Vyacheslav!
чт, 11 апр. 2019 г., 17:00 Dmitriy Pavlov :
> Dear Ignite Developers,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Daradur to become a committer and we are pleased to announce
> that he has accepted. Apache Ignite PMC apprecia
Hello, Igniters.
Why test on TC can allocate Data Region bigger than the amount of available RAM?
How can I disable this feature in a specific test?
"memoryAllocated=1024.0 GiB ... required=1093413MB, available=96675MB"
I have a test [1] that try to create Data Region of 1024 Gib size.
I want to
Hello, Ilya.
> Ignite does not touch every page of data region, and until you touch a page
> OS will not allocate any specific physical RAM to the virtual RAM address of
> that page.
This is not true.
Take a look into this discussion [1]
> Moreover, AFAIK Ignite will not even allocate all the
e there any guarantees that withConsistency proxy will not
> >
> > contain
> > > > > > > bugs that will lead to inconsistent write after inconsistency was
> > > > > > > found? I think there are no such guarantees. Bugs still are
&g
Hello, Igniters.
> Why test on TC can allocate Data Region bigger than the amount of available
> RAM?
Seems, we are using `echo 1 > /proc/sys/vm/overcommit_memory` on TC.
So I should fix my test :).
В Пн, 15/04/2019 в 13:41 +0300, Nikolay Izhikov пишет:
> Hello, Ilya.
>
>
Hello, Igniters.
For now, Ignite lack of good monitoring subsystem and profiling tools.
I think it's time to fix it!
I've created IEP-35 [1] for it.
Problems description:
1. Existing metrics are not documented(This is huge issue for our users, I know
it, for sure).
2. Currently, there are diffe
often face with a case when Ignite is a black-box for
> > administrators and devops engineers.
> >
> > I'd like to have a feature to monitor PME's queue, to view its size
> > and events type. The same is actual for Service Grid deployments
> > queue.
> >
leased: Version: 2018.2.3.
> > > > >
> > > > > Probably it could solve recently introduced problem related to:
> > > > > Unexpected error during build messages processing in TeamCity;
> > > > >
> > > > > Peter
Hello, Igniters.
I've prepared Proof of Concept for IEP-35 [1]
PR can be found here - https://github.com/apache/ignite/pull/6510
I've done following changes:
1. `GridMonitoringManager` [2] - simple implementation of manager to
store all monitoring info
2. `HttpPullExposerSpi` [
be great to have an ability to store a list of a fixed size
> of last N sensors, not to miss them without pushing to an external
> monitoring system.
>
> It'd be great if you provide a more extended test to show the work of
> the system. Everybody who looks to PR needs to run th
> Let's imagine that we have an infinite number of agents
Why we should imagine it?
We don't have infinite number of agents.
And we have several concurrent Run All.
В Пн, 29/04/2019 в 11:50 +0300, Павлухин Иван пишет:
> Vyacheslav,
>
> I finally figured out that "faster" means "total agent tim
d what do we mean by "faster". My question was:
>
> 1st approach will take less agent time in sum. 2nd approach will
> complete faster in wall clock time. And your main concern is "total
> agent time". Am I right?
>
> пн, 29 апр. 2019 г. в 12:01, Nikolay Izh
Hello, alex.
Thanks for reporting this.
1. You can file a bug in Ignite Jira.
2. It would be even better if you write a simple self contained reproducer
for your problem.
3. If you turnoff Ignite query optimization issue still reproducible?
пн, 29 апр. 2019 г., 19:29 alexcwyu :
> I am using Ign
e can add an additional parameter of
> `sensitivityLevel` to provide for the user a flexible sensor control
> (e.g., INFO, WARN, NOTICE, DEBUG).
>
> It also seems that for the sensors getValue() the completely
> functional java approach can be used. Am I right?
>
> O
each user API.
5. Collect feedback for a #4.
6. Design a log exposer. Consider the usage of JFR format or some other widely
used, tool compatible format.
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392
В Чт, 02/05/2019 в 14:02 +0300, Nikolay Izhikov пишет:
> He
Ticket for IEP.Phase1 created -
https://issues.apache.org/jira/browse/IGNITE-11848
В Пн, 13/05/2019 в 18:06 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
>
> We have discussed this IEP [1] with Alexey Goncharyuk, Anton Vinogradov,
> Andrey Gura, Alexey Scherbakov and Pav
+1 (binding)
чт, 23 мая 2019 г., 12:28 Dmitriy Pavlov :
> Hi Denis,
>
> I don't feel that we have found any blocker. It is impossible to do an
> absolutely perfect release. (if we do absolutely perfect release, what is
> the reason to contribute anything else? :) )
>
> The problem now is the only
> Dmitriy,
> >
> > This RC can not be released without explanation of huge diff to 2.7.0.
> > See my message above.
> > So, my -1 (binding).
> >
> > On Thu, May 23, 2019 at 12:34 PM Nikolay Izhikov
> > wrote:
> >
> > > +1 (binding)
> &g
/IndexingMultithreadedLoadContinuousRestartTest.java
```
В Чт, 23/05/2019 в 14:05 +0300, Nikolay Izhikov пишет:
> Seems, compare script doesn't unzip apache-ignite-2.7.0-bin.zip file before
> comparsion [1]
>
> Seems, our friend 'fabric' term sneaks in download script [2]. Step
> > > > > > > > пт, 15 мар. 2019 г. в 12:04, Павлухин Иван <
> vololo...@gmail.com>:
> > > > > > > > >
> > > > > > > > > Maxim,
> > > > > > > > >
> > > > &g
Hello, Denis.
Ignite doesn't encrypt memory page as long as it retains in memory.
Page encrypted when it is written to the disk.
пт, 31 мая 2019 г. в 19:39, Denis Magda :
> Nikolay,
>
> Do we really support encryption for pages in RAM? That's what I found in
> the docs:
>
> Ignite uses JDK-prov
Hello, Igniters.
We have several issues with Examples suite on TC
1. IgniteExamplesSparkSelfTestSuite seems configure, bu not runs on suite
execution. [1]
2. Spark Data Frame examples doesn't work in master. Seems some classpath
issues [2]
I will resolve issue #2.
Can anyone help me with #1?
aster/modules/core/src/main/java/org/apache/ignite/internal/util/io/GridReversedLinesFileReader.java#L154
> [3]
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/io/GridReversedLinesFileReader.java#L35
>
> вс, 2 июн. 2019 г. в 22:00,
Hello, Dmitriy.
I don't agree with you.
IEP should be written for any big changes in product.
We should have it for:
1. Following contributors.
2. History of decision making.
3. Easier documenting.
Without IEPs our product will become a total mess.
In the Apache Kafka one can't change any publ
Anton,
> > >
> > > Are any of you able to help Nickolay with [1]?
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Mon, Jun 3, 2019 at 6:17 AM Nikolay Izhikov
> > > wrote:
> > >
> > > > Hello, I
t;
>
>
> com.fasterxml.jackson.core
> jackson-annotations
> 2.6.7
>
>
> вт, 4 июн. 2019 г. в 14:57, Nikolay Izhikov :
> >
> > Igniters
> >
> > I've found the root issue.
> >
> > jackson dependency was added in IGNI
39945&tab=queuedBuildOverviewTab
https://ci.ignite.apache.org/viewLog.html?buildId=4039943&;;
В Вт, 04/06/2019 в 15:45 +0300, Павлухин Иван пишет:
> Would be great if it is possible.
>
> вт, 4 июн. 2019 г. в 15:43, Nikolay Izhikov :
> >
> > I used to think it&#x
e any objections?
[1] https://github.com/apache/ignite/pull/6587
[2]
https://ci.ignite.apache.org/viewLog.html?buildId=4041670&buildTypeId=IgniteTests24Java8_Examples&tab=testsInfo&branch_IgniteTests24Java8=pull%2F6587%2Fhead
В Вт, 04/06/2019 в 16:56 +0300, Nikolay Izhikov пишет:
> I
+1 (binding)
В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> +1 (binding)
>
> Nice to have clusters nodes started with ignite.sh in my JVM 11 environment
> without any settings.
>
> -
> Denis
>
>
> On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov wrote:
>
> > Dear Community,
> >
> >
> >
describe the problem once more, please? Is it about
> :ignite-examples module not being build in ~Build Apache Ignite~ ?
>
>
>
> > On 4 Jun 2019, at 20:34, Nikolay Izhikov wrote:
> >
> > Hello, Igniters.
> >
> > Root of the issue is in our maven profil
r Ivanov пишет:
> > On 5 Jun 2019, at 11:49, Nikolay Izhikov wrote:
> >
> > > 1. Why does your PR show only single file changed?
> >
> > Because this change fix the issue described in the ticket [1]
>
> So changes in intermediate commits were reverted in br
teTests24Java8_CheckCodeStyle
> >
> >
> > On Wed, 5 Jun 2019 at 12:35, Petr Ivanov wrote:
> > >
> > > I've added 'scala' profile to ~Build Apache Ignite~.
> > > Can you check please that everything is OK now?
> > >
> > > &g
xamplesSparkSelfTestSuite running
> on TC today?
>
> чт, 6 июн. 2019 г. в 15:00, Nikolay Izhikov :
> >
> > Petr.
> >
> > Scala profile already exists in ignite-examples.
> > But is wan't used in "Build Ignite"
> >
> > https:/
?buildId=4053973&buildTypeId=IgniteTests24Java8_Examples&tab=buildLog&_focus=1628
В Чт, 06/06/2019 в 15:23 +0300, Nikolay Izhikov пишет:
> Petr, Ivan.
>
> > Is IgniteExamplesSparkSelfTestSuite running on TC today?
>
> Yes.
>
> https://ci.ignite.apache.org/
Hello, Igniters.
Please, pay attention to commits quality.
1. Please, writer Javadocs.
2. Please, make the new lines according to code style.
Issues like [1] has to be fixed *BEFORE* commit.
[1]
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/interna
Hello, Petr.
> at least Scala does not compile
How cat I reproduce it?
Do we have ticket?
В Пт, 07/06/2019 в 15:28 +0300, Petr Ivanov пишет:
> Suite fails because Apache Ignite compilation is not supported under JDK 9+
> (at least Scala does not compile).
> Your build from [3] was triggered wit
905
В Вт, 14/05/2019 в 16:42 +0300, Nikolay Izhikov пишет:
> Ticket for IEP.Phase1 created -
> https://issues.apache.org/jira/browse/IGNITE-11848
>
>
> В Пн, 13/05/2019 в 18:06 +0300, Nikolay Izhikov пишет:
> > Hello, Igniters.
> >
> > We have discussed
iy Pavlov
>
> пн, 10 июн. 2019 г. в 14:30, Dmitriy Pavlov :
>
> > The vote for a new release candidate is closed, now
> >
> >
> >
> > Vote result: Vote passes with 9 votes +1 (4 binding +1 votes), no 0 and no
> > -1.
> >
> >
> &
r,-:ignite-visor-console,-:ignite-visor-console_2.10
> > > >
> > > > 3. Configure [Check Code Style] the same way as ~Build Apache Ignite~
> > > > to support builds for JDK9+.
> > > >
> > > > WDYT?
> > > > What
ts (sanity checks) into ~Build Apache
> Ignite~?
> Or may be we can go even further and use cascade system of tests — run them
> group by group, stopping the whole run if more fundamental tests are failing?
>
>
> > On 12 Jun 2019, at 21:54, Nikolay Izhikov wrote:
> >
>
+1 from me to reduce supported feature list.
Guys, are we talking about Ignite 3.0?
В Пн, 17/06/2019 в 11:57 +0300, Alexey Goncharuk пишет:
> Denis,
>
> I fully support this idea.
>
> First, looking back, I do not think it was a good design in the first place
> to build IGFS on top of Ignite c
* Scalar.
* LOCAL caches.
* Deprecated metrics.
В Пн, 17/06/2019 в 15:18 +0300, Alexey Goncharuk пишет:
> Igniters,
>
> Even though we are still planning the Ignite 2.8 release, I would like to
> kick-off a discussion related to Ignite 3.0, because the efforts for AI 3.0
> will be significantly l
ready in the list :) Added the outdated
> metrics point.
>
> пн, 17 июн. 2019 г. в 15:32, Nikolay Izhikov :
>
> > * Scalar.
> > * LOCAL caches.
> > * Deprecated metrics.
> >
> > В Пн, 17/06/2019 в 15:18 +0300, Alexey Goncharuk пишет:
> > > Ignite
do not think it makes sense to expose all feature
> >
> > set
> > > of Igntie to thin clients.
> > >
> > > Instead, we can significantly simplify client node configuration - it
> > > currently requires the same config as a regular Ignite node, howeve
not name it removal of client nodes at all. Any Apache Ignite
> guide I saw is starting from 2 steps: 1) start server node, 2) start client
> node.
>
> There are no reasons to write software if users are unaware of how to use
> it. So I do not agree that supplementary materials are u
Hello, Dmitriy.
Thanks, for starting this discussion.
I think almost all of community members don't know the difference between two
options.
I vote for the simplest solution with the human readable format.
В Пн, 17/06/2019 в 21:07 +0300, Dmitriy Pavlov пишет:
> Hi Igniters,
>
> During prepari
+1
чт, 20 июня 2019 г., 8:28 Павлухин Иван :
> +1
>
> чт, 20 июн. 2019 г. в 04:18, Valentin Kulichenko
> :
> >
> > +1
> >
> > On Wed, Jun 19, 2019 at 5:58 PM Roman Shtykh
> > wrote:
> >
> > > +1
> > >
> > >
> > > On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura <
> > > ag...@apach
Hello, Igniters.
Especially, Ignite veterans.
I've prepared PR [1] for the ticket IGNITE-11926 [2].
I found that we don't have any tests for the current GridJobMetrics
implementation.
So I added basic tests for the current implementation in the PR.
Guys, do we have real-world usages of numbers
Anton.
I worried about this limitation:
> Entries streamed using data streamer (using not a "cache.put" based updater)
> and loaded by cache.load.
As we discussed privately in this modes
*ALL ENTRIES ON ALL OWNERS WILL HAVE DIFFERENT VERSIONS*
Why we need this modes, in the first place?
Shou
Hello, Alex.
Thanks for the answer.
1. I, actually, don't understand your proposal :)
Can you write it down?
What numbers should be additionally migrated in this PR?
Or it's OK for now?
> I think "idle time" is a useful metric
I think "usefulness" or "uselessness" of specific metrics depends
Hello, Ivan.
> Ignite is a cluster which almost every
> time assumes an external monitoring for a production use.
+1.
> 1. Are we going to preserve a compatibility with metrics present
> before? Or are we going to keep only those making sense today?
1. Backward compatibility preserved.
2. Depr
Hello, Alex.
Based on our private discussion I've additionally migrated `totalExecutionTime`
and `totalWaitingTime` counters.
Can you review the PR [1]?
[1] https://github.com/apache/ignite/pull/6622
В Пн, 24/06/2019 в 15:14 +0300, Nikolay Izhikov пишет:
> Hello, Alex.
>
>
+1.
В Вт, 25/06/2019 в 11:08 +0300, Dmitriy Pavlov пишет:
> Hi Developers, and, especially, PMCs,
>
> As 2.7.5 release manager, I've faced with a number of unclear steps in our
> process.
>
> I would like to share this talk given by Mark Thomas, the Board member:
>
> https://youtu.be/MO_AVjSPuB
Hello, Igniters.
As you may know, I've contributed Phase1 [1] for IEP-35 [2].
Now we have metrics subsystem and can create and export any metrics from Ignite.
I think user(administrator of Ignite) should be able to configure some metrics
params in a common way [3]
I propose to use the same way
52, 52-infinity - recorded), it should be possible to skip some
> values.
> Another case is to specify 2+ windows for same metric, eg. puts for last
> hour, minute, 5 seconds.
>
> On Thu, Jun 27, 2019 at 12:30 PM Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
hat the
> configuration is generalized into the metrics framework.
>
> What do you think?
>
> чт, 27 июн. 2019 г. в 12:30, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > As you may know, I've contributed Phase1 [1] for IEP-35 [2].
> > Now
Hello, Maksim.
I will take a look shortly.
В Пт, 28/06/2019 в 19:02 +0300, Maksim Stepachev пишет:
> Hello, Igniters.
>
> I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" breaks cache
> stop performance. It affects next tests: testParallelStartAndStop,
> testStartManyCaches
>
the metrics registry to utilize a SkipListMap,
> which allow us to iterate only on a subset of the metrics by prefix, or
> internally have a trie so that we can remove all metrics with a given prefix
> in O(1) time.
>
> What do you think?
>
> пн, 10 июн. 2019 г. в 13:49, Nik
401 - 500 of 1145 matches
Mail list logo
