GridTaskProcessor,
> SchemaManager). Have I missed something?
>
> пт, 4 окт. 2019 г. в 14:12, Nikolay Izhikov :
> >
> > Hello, Ivan.
> >
> > > 1. How system views are going to be exposed? Is there any difference
> > > in comparison to other metrics?
&
+1
В Пн, 07/10/2019 в 13:18 +0300, Maxim Muzafarov пишет:
> Igniters,
>
>
> I'm planning October 11 (Friday) 22-00 MSK enable `checkstyle` profile
> on the [Build
> Apache Ignite] suite by the end of the next weekend (one week test
> period). Such an option discussed many times before (e.g. [1])
Hello, Mikhail.
I will take a look, shortly.
В Чт, 10/10/2019 в 16:08 +0300, Mikhail Petrov пишет:
> Hello, Igniters.
>
> My project demands extended logic of Apache Ignite REST processor. I'd
> like to implement a specific one and use it with Apache Ignite, but now
> it's impossible. I have c
Hello, Alexey.
I'm ready to take part in the meeting.
It will be in Russian, isn't it?
В Пн, 14/10/2019 в 14:00 +0300, Alexey Zinoviev пишет:
> Hi, Igniters, and especially Nikolay Izhikov
>
> I suggest to arrange the meeting via ASF-slack in #ignite-spark-integration
>
//github.com/apache/ignite/pull/6937
> > [4] https://reviews.ignite.apache.org/ignite/review/IGNT-CR-1067
> >
> > пн, 23 сент. 2019 г. в 17:13, Nikolay Izhikov :
> > >
> > > Hello, Nikita.
> > >
> > > > A node creates the ChangeMasterKeyMessag
Denis, AFAIK we doesn't have documentation for the SQL System Views existing in
Ignite.
I have plans to write a documentation about metrics and syste views that will
cover SQL System View.
It will be available till 2.8 release.
В Пт, 18/10/2019 в 07:16 -0700, Denis Magda пишет:
> Alex, Ignite
Hello, Sergey.
I will take a look, shortly.
Additional review of index experts will be very helpful.
В Пн, 21/10/2019 в 11:46 +0300, Sergey Kalashnikov пишет:
> Hello Igniters!
>
> I'm working on the improvement
> https://issues.apache.org/jira/browse/IGNITE-12295 in scope of a larger
> file-ba
Hello, Nikita.
Thanks for picking this up.
> I suggest adding a ... system view that shows if there are any index
> rebuilding
Are you talking about new system view?
Why do we need it?
We already have INDEXES system view that show info about each index existing on
the Ignite node.
Can we add
gt; > > > > >separately from current scala profile
> > > > > > >4. We are ready to move the Ignite-Spark integration to the
> > > >
> > > > separate
> > > > > > >module after release 2.8 with support o
Nikita, please, feel free:
1. To create a ticket to remove `stopProcess` method from the interface.
This improvement looks obvious to me.
Seems we can implement it easily.
2. To make all Discovery messages immutable.
This one more complex.
I think we should discuss every single mutable message se
hear back from someone by that time,
> then the silence will be treated as a rejection. Keep in mind that even
> though everyone is free to cast a vote, the votes of PMC members are
> counted for the Chair election:
>
>- Nikolay Izhikov
>- Alexey Goncharuk
>
Hello, Fernando.
First of all, thank you for your interest in Apache Ignite.
> how can I contribute to improve geospatial support and indexing?
Just create a ticket and discuss the changes on the dev-list.
Here are some links you can find usefull:
* https://ignite.apache.org/community/contribu
+1 for Nikolay Izhikov (binding)
В Вт, 29/10/2019 в 20:13 +0300, Pavel Tupitsyn пишет:
> +1 for Dmitry Pavlov
>
> On Tue, Oct 29, 2019 at 8:07 PM Ivan Rakov wrote:
>
> > +1 for Dmitry Pavlov
> >
> > Best Regards,
> > Ivan Rakov
> >
> > On 29.10
Hello, Alexey.
I'm +1.
Let's do it.
В Ср, 06/11/2019 в 16:37 +0700, Alexey Kuznetsov пишет:
> Hi, All!
>
> I'm working on a tool for metrics monitoring.
> And found that Metric interface [1] has a name and description, but has not
> measurement units.
>
> When you are working on a tool that col
+1 to include PME free switch to 2.8
ср, 18 дек. 2019 г., 8:31 Anton Vinogradov :
> Maxim,
> https://issues.apache.org/jira/browse/IGNITE-9913 (Pme-free switch) ready
> to be merged to master.
> How about to include it to the 2.8 too?
>
> On Tue, Dec 17, 2019 at 3:31 PM Ivan Pavlukhin
> wrote:
>
+1 to mark feature or whole release as EA.
пт, 17 янв. 2020 г., 23:00 Denis Magda :
> Folks, if you don't mind I'll share some thoughts/suggestions as an
> observer who was not involved in the feature development.
>
> It's absolutely 'ok' to deprecate an API that is replaced with a much
> better
Hello, Alexey Kuznetsov.
I have two approvals from Saikat Maitra and Maxim Stepachov.
I have plans to merge spring-boot autoconfigure modules to
ignite-extensions. [1]
Do you want to perform additional review?
[1] https://github.com/apache/ignite-extensions/pull/6
пт, 24 янв. 2020 г. в 07:41, Sa
;>>>>>>>>
>>>>>>>>>> Alexey approved my PR [1] regarding fixing public API for metric
>> exporters.
>>>>>>>>>> I’m waiting for a bot visa and merge this PR.
>>>>>>>>>>
>>>&g
, I suggest to include
>>>> this
>>>>>> fix to
>>>>>>>>> 2.8
>>>>>>>>>> release. What do you think?
>>>>>>>>>>
>>>>>>>>>> [1]: https://issues.apache.o
metrics updated on each communication message.
>
> Metrics are not free at all. User can disable metrics if it will
> affect performance.
>
> On Mon, Jan 27, 2020 at 8:23 PM Nikolay Izhikov wrote:
>>
>> Hello, Andrey.
>>
>> I’m OK to include these changes to
in any release nor in
>> current master so we should change this code carefully
>
> This is another bug. I think it could be fixed easily by adding
> metricsEnabled flag to TcpCommunicationSpi.
>
> On Mon, Jan 27, 2020 at 9:17 PM Nikolay Izhikov wrote:
>>
>> Andrey.
gt;
> I don't need help in benchmarking. Once again, еhe current behavior is
> incorrect and should be fixed regardless of performance.
>
> Or... this functionality should be removed if performance is more
> important. In case of incorrect behavior it is the best option.
>
>
Merged to master [1]
Igniters, I want to release both modules I added.
Do we have documentation, how it should be done for ignite-extensions?
[1]
https://github.com/apache/ignite-extensions/commit/575ec510e4d48b1e0c2ec7e4cf8d596e7de82f70
пн, 27 янв. 2020 г. в 13:06, Nikolay Izhikov :
> He
couldn't
>> be switched off).
>>
>> We are walking in a circle instead of moving forward. On comments
>> about API you provide new PRs that change API while denying problems
>> with the API. This is illogical and process doesn't converge because
>
apache.org/jira/browse/IGNITE-12576
> [2]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks
>
> On Mon, 27 Jan 2020 at 23:58, Nikolay Izhikov wrote:
>>
>> Andrey.
>>
>>> My choice: correctness over performance
>&g
Vladimir.
Please, provide a simple, self-contained reproducer to the issue you described.
> 29 янв. 2020 г., в 11:16, Vladimir Steshin написал(а):
>
> Hi ppl. Wanted to ask is issue a bug. Minor propably.
>
> Recently noticed that one simple query returns a value which can't be found
> 'as is'
Hello, Igniters.
Can you, please, give me a link to the «Ignite Extension» project on the TC?
Hello, Sergey.
Your proposal is not clear for me
Can you, please, describe the issue you are trying to solve?
And the way you want to do it.
> 29 янв. 2020 г., в 14:53, Sergey Chernolyas
> написал(а):
>
> Hi!
> It is proposed to use the structure for configuration.
>
> spring.data.ignite:
>
l
>
> Am I investing to a bicycle?
>
> On Wed, 29 Jan 2020 at 14:58, Nikolay Izhikov wrote:
>
>> Hello, Sergey.
>>
>> Your proposal is not clear for me
>> Can you, please, describe the issue you are trying to solve?
>> And the way you want
Hello, Igniters.
I found really confusing results of the simple test.
Data from the in-memory cache are vanished after change cluster state to
INACTIVE/ACTIVE.
Is this a bug or expected behavior?
```
public class ClusterDeactivateTest extends GridCommonAbstractTest {
String name = "my-cach
/ci.ignite.apache.org/project.html?projectId=IgniteExtensions&tab=projectOverview
>
> Regards,
> Saikat
>
> On Wed, Jan 29, 2020 at 5:26 AM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> Can you, please, give me a link to the «Ignite Extension» project on the TC?
e, the
> data is lost, this is an expected behavior.
>
> ср, 29 янв. 2020 г. в 19:18, Nikolay Izhikov :
>
>> Hello, Igniters.
>>
>> I found really confusing results of the simple test.
>> Data from the in-memory cache are vanished after change cluster stat
:51, Alexey Goncharuk
> написал(а):
>
> Nikolay,
>
> This change will affect only the command-line utility, correct? No changes
> for the public API are planned?
>
> чт, 30 янв. 2020 г. в 12:46, Nikolay Izhikov :
>
>> Hello, Alexey.
>>
>> Thank
Hello.
> 2. Add @IgniteExperimetnal to new API (because... see item. 1
+1
> 1. Remove @Deprecated from old API (because it strange to have one deprecated
> API and second experimental API)
-1
I propose to update deprecation message and provide metric name for each
deprecated method.
> @depr
Alexey.
I answered to your examples and issues you provide.
But, it seems the discussion of the API and the Java code itself is not the
goal of this thread anymore.
> Should we provide a way to know the number of metrics and registries in
> advance?
No.
If you think this is the real use-as l
Go for it, Vladimir!
> 31 янв. 2020 г., в 16:15, Vladimir Steshin написал(а):
>
> Hi folks. I created a ticket for this (IGNITE-12614):
>
>
>
>
>
> Currently, anyone is able to silently deactivate cluster with command line
> utility (control.sh). Probably with JMX too. Same for the API:
Hello, Igniters.
I propose to create management API to dance user provided tasks and queries.
Below my proposal in the IEP [1] form.
Please, share your feedback.
Motivation:
Ignite provides many API to deploy and execute user-provided code on the
server nodes
inside the sam JVM as Ign
Ivan.
It seems we don’t have a format definition for a «community decision»
We, for sure, should fill this gap.
Me and Andrey Gura, have certain proposals for our development process based on
metrics API discussion.
We will share those proposals after 2.8 release and some additional discussion.
Igniters, thanks for the feedback.
> Can we retain only single cancel(long queryId) method in QueryMXBean ?
> I think query type can be determined by queryId.
It seems the answer is no we can’t do it for now.
Different types of queries are handled by different managers and have different
sets of
Alexey.
I’m talking the following scenario:
1. Consider we have unified bean to kill tasks:
CancelMXBean {
public void cancel(long id);
}
2. And we have the following log:
```
Transaction with ID=42 started.
Compute task with ID=43 started.
```
3. We want to kill compute task and by
Vladimir.
This looks like a bug to me.
Can you, please, prepare the simple reproducer for this issue and it’s
consequences?
> 5 февр. 2020 г., в 17:08, Vladimir Steshin написал(а):
>
> Hi, folks.
>
>
>
> I recently found that one node might be started with flag
> reuse-memory-on-deactivat
Hello, Igniters.
We don't have a release process for newly created ignite-extensions modules.
I want to release two modules:
* ignite-spring-boot-autoconfigure
* ignite-client-spring-boot-autoconfigure
Let's discuss it.
Any objections to it?
What should be done before release?
gt; do it for IgniteConfiguration?
>>
>> [1]
>> https://issues.apache.org/jira/browse/IGNITE-12470?focusedCommentId=17004207&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17004207
>>
>> On Wed, 5 Feb 2020 at 17:20, Nikolay Izhikov
Hello,
I have two notes
> * Allow to deprecate the old APIs even when new APIs are marked with
> @IgniteExperimental to explicitly notify users that the new APIs are available
I think the main reason is not «notify users that new APIs are available», but
«Notify users that old APIs will be rem
Hello, Igniters.
Should we mark MVCC feature with the new @IgniteExperimental?
We explicitly note users that MVCC has beta status, for now [1]
> Beta version of Transactional SQL and MVCC
> In Ignite v2.7, Transactional SQL and MVCC are released as beta versions to
> allow users to experiment a
t; Best regards,
> Ivan Pavlukhin
>
> ср, 5 февр. 2020 г. в 17:44, Denis Magda :
>>
>> Alex, did you have a chance to review Saikat’s changes related to the
>> extensions repository organization and release approach?
>>
>> Denis
>>
>> On Wedne
that it’s
>>> not production ready.
>>>
>>> What happens with the annotation, incidentally? Is it just in the
>>> documentation or do you get a compile-time warning?
>>>
>>>> On 6 Feb 2020, at 11:32, Nikolay Izhikov wrote:
>>&g
Ticket [1] created.
[1] https://issues.apache.org/jira/browse/IGNITE-12632
> 5 февр. 2020 г., в 15:36, Nikolay Izhikov написал(а):
>
> Alexey.
>
> I’m talking the following scenario:
>
> 1. Consider we have unified bean to kill tasks:
>
> CancelMXBean {
>
gt; I thought we just release module with the 1.0.0 version and specify
>> supported Ignite version somewhere in the documentation.
> sounds fine to me.
>
> Best regards,
> Ivan Pavlukhin
>
> чт, 6 февр. 2020 г. в 15:00, Nikolay Izhikov :
>>
>> Hello, Ivan.
> To prevent unexpected data loss on
deactivation CLI and JMX should require 'force' flag
Vladimir, please, go for it.
пт, 7 февр. 2020 г., 11:19 Vladimir Steshin :
> Ok. Then we are at the beginning. To prevent unexpected data loss on
> deactivation CLI and JMX should require 'force' flag. If
Hello, Vyacheslav.
> It seems to me we missed API that should be introduced into control utility.
Do you think we should support control.sh for cancel tasks?
> 7 февр. 2020 г., в 11:04, Alexey Goncharuk
> написал(а):
>
> Alexei,
>
> I agree that there should be no principal difficulty with
Hell, Alexey.
> We should work on processes to prevent such merges in the future, but not
> waste time reverting something that can be used for profit.
Can you, please, clarify, what real-world use-cases for the current
implementation of MVCC exists?
> 7 февр. 2020 г., в 13:07, Alexey Gonchar
Hello, Ivan.
Please, clarify what columns are missed?
Do you file a ticket to introduce those fields?
> 7 февр. 2020 г., в 13:26, Ivan Pavlukhin написал(а):
>
> Nikolay,
>
> Recently I noticed some changes in SQL indexes view content introduced
> in [1]. Among changes I noticed:
> 1. Columns r
> 1. Columns related to a cache group information disappeared.
Information about cache group can be gathered from SYS.CACHES and
SYS.CACHE_GROUPS.
> 2. "proxy" indexes info is now displayed in the view.
Yes, this was made intentionally.
I think we shouldn’t hide internal details from the user i
ty is a more natural way of administration/control
> of the cluster instead of JMX, for example.
>
> Thanks,
> S.
>
> пт, 7 февр. 2020 г. в 11:38, Nikolay Izhikov :
>
>> Hello, Vyacheslav.
>>
>>> It seems to me we missed API that should be introdu
one from a user perspective. Could you
> please elaborate?
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 7 февр. 2020 г. в 13:33, Nikolay Izhikov :
>>
>>> 1. Columns related to a cache group information disappeared.
>>
>> Information about cache group can be
+1
> 10 февр. 2020 г., в 11:57, Andrey Mashenkov
> написал(а):
>
> -1 Prohibit.
>
> We must not deprecate old API without have a new stable well-documented
> alternative and a way to migrate to new one.
>
>
> On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk
> wrote:
>
>> Dear Apache Ignit
Hello, Vladimir.
I think we should do the following:
* Update Ignite documentation and write down the fact that in-memory cache
cleared on deactivation.
* Disallow, by default, deactivation of the cluster that has in-memory cache
with proper error message
«Your cluster has in-memory cac
Alexey.
The issue with the existing method.
Single implementation for both Ignite#active(boolean) and
IgniteMXBean#active(boolean)
Should it continue to silently clears in-memory caches?
> 14 февр. 2020 г., в 15:20, Alexey Goncharuk
> написал(а):
>
> Igniters,
>
> Do we really need the conf
Vyacheslav.
What is your suggestion for the API?
Single implementation for both Ignite#active(boolean) and
IgniteMXBean#active(boolean)
Should public java API continue to silently clears in-memory caches?
> 14 февр. 2020 г., в 15:56, Вячеслав Коптилин
> написал(а):
>
> Hello Vladimir,
>
>>
)/deactivateCluster() and
> deprecate IgniteMXBean#active(boolean)?
> Does this make sense? Am I missing something?
>
> Thanks,
> S.
>
> пт, 14 февр. 2020 г. в 16:17, Nikolay Izhikov :
>
>> Vyacheslav.
>>
>> What is your suggestion for the API?
>>
&
Soory.
I forgot two more methods
IgniteMXBean {
@Deprecated
public String clusterState();
public void clusterState(String state);
}
> 14 февр. 2020 г., в 17:50, Nikolay Izhikov
> написал(а):
>
> Vyacheslav.
>
>
> Let’s see what we got for n
Hello, Igniters.
Can someone bring some light on the state of the ML module in Ignite?
As far as I know, for now, we have only 1 active contributor to this area -
Alexey Zinoviev.
I see how whole modules come and go from the module - [1]
Please, also note this quote:
> Also as a result of good t
us to execute through JMX despite it is deprecated.
>>>>
>>>> пт, 14 февр. 2020 г. в 17:36, Вячеслав Коптилин <
>>> slava.kopti...@gmail.com
>>>>> :
>>>>
>>>>> Hello Nikolay,
>>>>>
>>>>>> Sho
e correct docs, the understanding what could be used by clients
>> and first of all, production-ready ML (it could be run on Ignite-cluster,
>> really, it works.)
>>
>> If you, Igniters, believe, that I could be a good maintainer for ML module,
>> please support me here in
Hello, Alexey.
> We need to agree whether IgniteMxBean#active(boolean) and
> Ignite#active(boolean) behaving differently is ok from the user side.
I think it’s not OK.
We should provide consistent behavior for all management APIs: jmx, control.sh,
REST, Java API.
The primary use-case I keep in
Hello, Dmitriy.
Do you have a reproducer? minimal application that can reproduce this specific
bug.
Can you, please, run a TC for your PR and get a TC bot visa?
> 25 февр. 2020 г., в 11:08, Dmitry Gorchakov
> написал(а):
>
> This issue once reproduced in my productive with similar stack trac
Igniters,
I think we can replace cache name with the cache id.
This should solve issue with the length limitation.
What do you think?
> 28 февр. 2020 г., в 15:32, Ivan Bessonov написал(а):
>
> Hello Igniters,
>
> we have an issue in master branch and in the upcoming 2.8 release that
> related
Hello, Ilya.
ignite-jta
ignite-zookeeper
Why you suggest to remove these modules?
As far as I know, they are used in the real production environment.
You can take this vide(in Russian) as an example -
https://www.youtube.com/watch?v=GSi_C9_gQMc
> 29 февр. 2020 г., в 08:22, Alexey Zinoviev
>
Hello, Igniters.
Ignite right now support `KILL QUERY` command.
I tried to use it and stuck with the simple test.
Error is «Query with provided ID doesn’t exist»
Can you, please, advise me - How KILL QUERY should be used?
```
@Test
public void testCancelSQLQuery() throws Exception {
27;t get into that list.
>
> Try to replace "ignite0" with a "client" node in this line. I think it
> may help:
>
>> List> sqlQries0 = SqlViewExporterSpiTest.execute(client, "SELECT
>> QUERY_ID FROM SYS.SQL_QUERIES");
>
>
>
&
our.
>
>
> And what about query hanging: it is a known issue. I'm working on it
> right now. I'll file a ticket and propose a patch soon.
>> I tried and it doesn’t work, also.
>> `KILL QUERY` command just freeze on
>> `CommandProcessor#processKillQueryComman
uery with provided ID doesn’t exist»
>
> The another problem you've encountered after running KILL QUERY command
> with correct qryId is freezing. Am I correct? If yes, this is a known
> issue and I am working on it.
>
>
> --
> Kind Regards
> Roman Kondakov
>
Hello, Vladimir.
> What if we just provide an option to disable service metrics at all?
I don't think we should create an explicit property for service metrics.
We will implement the way to disable any metrics in the scope of
IGNITE-11927 [1].
> Usage of a proxy instead of service instances can
+1 (binding)
* compiled from source.
* start node from bin distribution.
* check thin driver and made some SQL queries with it.
> 2 марта 2020 г., в 17:33, Sergey Antonov
> написал(а):
>
> 0.
> Still can't get access to teamcity links.
>
> пн, 2 мар. 2020 г., 17:24 Alexey Zinoviev :
>
>> +1
I thought documentation can be updated after the release.
Isn’t it?
> Is there anybody who can do that?
I can do it.
> 2 марта 2020 г., в 18:44, Maxim Muzafarov написал(а):
>
> Denis,
>
> Thank you, I think yes.
> But I don't expect that the release will be delayed since we still
> need som
Just made you an administrator of Ignite documentation site.
> 2 марта 2020 г., в 18:54, Maxim Muzafarov написал(а):
>
> login: maxmu...@gmail.com
>
> On Mon, 2 Mar 2020 at 18:54, Maxim Muzafarov wrote:
>>
>> Igniters,
>>
>>
>> Can anyone give permissions to edit\publish documentation Apach
Hello, Igniters.
Do we have a person who can fix this issue in the nearest time?
Right now IGNITE-12746 is Open and Unassigned.
> 3 марта 2020 г., в 23:54, Denis Magda написал(а):
>
> Ilya,
>
> Thanks for catching that and sharing. I wonder if there are any other
> blockers that were pushed to
can't delay the release forever because of them. Let's fix
> things in 2.8.1.
>
> [1] https://ignite.apache.org/download.cgi
> [2] https://mvnrepository.com/artifact/org.apache.ignite
>
>
> On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov wrote:
>
>> H
cancellation
>>>>
>>>>
>>>>- JDBC: Support for query timeout
>>>>
>>>>
>>>>- suspend/resume for pessimistic transactions
>>>>
>>>>
>>>>- WAL page compression
>>>>
>
>> Ivan Pavlukhin
>>>>>>>
>>>>>>> ср, 4 мар. 2020 г. в 17:08, Denis Magda :
>>>>>>>>
>>>>>>>> Dmitriy,
>>>>>>>>
>>>>>>>> Ignite 2.8 will be announced as soon
;> https://mvnrepository.com/artifact/org.apache.ignite/ignite-co
>>>>>>> re/2.8.0
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Ivan Pavlukhin
>>>>>>>
>>>>>>> ср, 4 мар. 2020 г. в 17:
gt;>>>>>> Are your sure? Was not the feature implemented for java thin client
>>>>>>>> in [1]?
>>>>>>>>
>>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-11898
>>>>>>>>
>>&g
Hello, Igniters.
I prepared a PR for the new system view - JOBS. [1]. Ticket [2]
For now, as you may know, internally we have two processors that implement
compute feature:
* `GridTaskProcessor` - manage locally started compute tasks.
* `GridJobProcessor` - manage compute jobs that should be e
or issues left with
>> documentation.
>> Are we ready to announce 2.8 release widely?
>>
>>
>> On Tue, 10 Mar 2020 at 12:10, Nikolay Izhikov
>>
>> wrote:
>>
>>> Hello, Igniters.
>>>
>>> I rewrote pages about new metrics
Hello, Igniters.
I want to organize the webinar for the Apache Ignite community.
The subject of the webinar - «New monitoring and system view in 2.8»
Is there any Apache guides on how to do it?
What software should be used? How I should announce it? etc...
Yes.
> 12 марта 2020 г., в 10:59, Maksim Stepachev
> написал(а):
>
> It's the perfect idea. Will it in English?
>
> чт, 12 мар. 2020 г. в 10:15, Nikolay Izhikov :
>
>> Hello, Igniters.
>>
>> I want to organize the webinar for the Apache Ignite com
Hello, Igniters.
I propose to add these tickets to the 2.8.1 scope
[1] Disallow silent deactivation in CLI and REST -
https://issues.apache.org/jira/browse/IGNITE-12701
[2] Compute job system view - https://issues.apache.org/jira/browse/IGNITE-12745
[3] Transaction operations metrics -
https://
Hello, Petr.
> I thought the release cycle should be community driven, not single donator.
We are the part of the global Ignite community, itn’t it?
If you know some reason to postpone bug fix releases, please, write it down.
> what's the haste with next minor version?
Users of the Ignite acti
ing. I will be happy to help with the announcement and
>> scheduling.
>> Dmitry, what do you think? ASF slack looks less comfortable for this
>> purpose.
>>
>> чт, 12 мар. 2020 г. в 11:22, Nikolay Izhikov :
>>
>>> Yes.
>>>
>>>> 12 марта
Hello, Mikhail.
Can you, please, double-check link to the ticket?
For now it’s a IGNITE-12049 Add user attributes to thin clients which is
resolved.
> 16 марта 2020 г., в 12:04, Mikhail Petrov написал(а):
>
> Hello, Igniters.
>
> I'd like to propose a small improvement in control.sh configur
Hello, guys.
I propose myself as a release manager for 2.8.1.
> 16 марта 2020 г., в 14:19, kpushenko написал(а):
>
> Hi, igniters!
>
> I would like to propose a discussion of version 2.9 and scope releases for
> 2020 to another discussion thread.
>
> I understand that there is no objection to
bd1712ad01c9'
KILL COMPUTE_TASK '58b48c3e071-b2d221ca-ab08-4544-b8dc-8475538ed42f'
KILL SERVICE 'my-svc'
```
[1] https://github.com/apache/ignite/pull/7520
[2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145724615
[3] https://issues.apache.org/ji
Hello, Vladimir.
If there is at lease one persistent data region then system data region also
becomes persistent.
Your example applies only to pure in-memory clusters.
And should be covered with the —force parameter we added.
What do you think?
> 17 марта 2020 г., в 13:45, Vladimir Steshin на
o emphasize overall ability to lose
> various objects, not only data. Probably might be reconsidered in future.
>
>
> 17.03.2020 13:49, Nikolay Izhikov пишет:
>> Hello, Vladimir.
>>
>> If there is at lease one persistent data region then system data region also
&g
I want to be a release manager.
> 19 марта 2020 г., в 17:52, Denis Magda написал(а):
>
> Igniters,
>
> As long as 2.8.1 is inevitable and we already keep adding critical issues
> to the working queue, let's settle on the release time frames and decide
> who will be a release manager. This is t
> Thoughts?
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-12614
> [2]: https://issues.apache.org/jira/browse/IGNITE-12701
>
> --
> Ivan
>
>
> On Tue, Mar 17, 2020 at 2:26 PM Vladimir Steshin wrote:
>
>> Nikolay, I think we should reconsider cleari
memory state
> after subsequent reactivation.
> 3. Describe current behavior for in-memory cache on deactivation in Ignite
> documentation.
>
>
> пн, 23 мар. 2020 г. в 21:22, Nikolay Izhikov :
>
>> Hello, Ivan.
>>
>>> Seems like we don't have a final a
gt; the
>>> javadoc.
>>> I'm also against some "temporary" API.
>>>
>>> We should:
>>>
>>> 1. Partially remove IGNITE-12701 except javadoc part. Note control.sh
>> for a
>>> long time has support for a confirmation on dea
Hello, Alexey.
I just repeat our agreement to be on the same page
> The confirmation should only present in the user-facing interfaces.
1. We should add —force flag to the command.sh deactivation command.
2. We should throw the exception if cluster has in-memory caches and
—force=false.
3. We s
101 - 200 of 1145 matches
Mail list logo
