ful than comparing with
specific enum's value.
I'm going to do that on the ticket [1].
Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-13144
--
BR, Sergey Antonov
gt;
> >
> >
> >
> > ср, 10 июн. 2020 г. в 19:02, Pavel Tupitsyn :
> >
> >> Sergey,
> >>
> >> I disagree - looks weird.
> >> We have lots of enums, is this one special in some way?
> >>
> >> Thanks,
> >> Pave
Igniters, the patch [1] is ready for the review.
Can someone look at it, please?
[1] https://github.com/apache/ignite/pull/7924
ср, 10 июн. 2020 г. в 23:42, Sergey Antonov :
> Pavel, Alexei thank you for your replays.
>
> > is this one special in some way?
> Yes. We have two &
Hello, Igniters!
I'd like to get a review of the ticket [1]. The patch is ready [2].
Can someone look at it, please?
[1] https://issues.apache.org/jira/browse/IGNITE-13138
[2] https://github.com/apache/ignite/pull/7918/files
--
BR, Sergey Antonov
Hello, Igniters!
I'd like to get a review of the ticket [1]. The patch is ready [2].
Can someone look at it, please?
[1] https://issues.apache.org/jira/browse/IGNITE-13144
[2] https://github.com/apache/ignite/pull/7924
--
BR, Sergey Antonov
Guys, could someone review my patch, please?
вт, 16 июн. 2020 г. в 10:50, Sergey Antonov :
> Hello, Igniters!
>
> I'd like to get a review of the ticket [1]. The patch is ready [2].
> Can someone look at it, please?
>
> [1] https://issues.apache.org/jira/browse/I
x27;t use TC Bot for getting a visa.
[1]
https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/7924/head&action=Latest
[2] https://ibb.co/m8rW74L
--
BR, Sergey Antonov
Hi!
Please uncheck java-9+ profile in the maven profiles in idea. It could help
you.
вс, 21 июн. 2020 г., 22:05 Guru Stron :
> Dear Igniters,
>
> I filled instructions from
> https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup - checked
> out project, opened it in Intellij IDEA and
Congratulations, Sergey!
сб, 18 июл. 2020 г., 0:24 Andrey Mashenkov :
> Congratulations, Sergey.
>
> пт, 17 июл. 2020 г., 15:06 Вячеслав Коптилин :
>
> > Hi,
> >
> > Well deserved! Keep it up, Sergey!
> >
> > Thanks,
> > S.
> >
> > пт, 17 июл. 2020 г. в 14:36, Ivan Pavlukhin :
> >
> > > Sergey, c
He joined the
> >>>>>>> community in 2016.
> >>>>>>> He participated in the development of Ignite 1.x, 2.x and he is
> >>>>>>> actively
> >>>>>>> working on a new Apache Ignite 3.0 release.
> >>>>>>>
> >>>>>>> Being a committer enables easier contribution to the project since
> >>>>>>> there
> >>>>>>> is no need to go via the patch submission process. This should
> >>> enable
> >>>>>>> better productivity.
> >>>>>>>
> >>>>>>> Please join me in welcoming Vlad, and congratulating him on the
> >> new
> >>>>>>> role
> >>>>>>> in the Apache Ignite Community.
> >>>>>>>
> >>>>>>> -Val
> >>>>>>>
> >>>>>
> >>>>> --
> >>>>> Sincerely yours, Ivan Daschinskiy
> >>>>>
> >>>>
> >>>> --
> >>>>
> >>>> Best regards,
> >>>> Ivan Pavlukhin
> >>>>
>
--
BR, Sergey Antonov
, Alexei Scherbakov <
alexey.scherbak...@gmail.com>:
> Sergey Antonov,
>
> The states ACTIVE, INACTIVE, READ-ONLY look confusing.
> Actually read-only cluster is active too.
>
> I would suggest adding new property to Ignite configuration like
> setActivationOptions(Activation
your opinion about my points. What do you think about it?
[1] https://issues.apache.org/jira/browse/IGNITE-12225
вт, 15 окт. 2019 г. в 14:56, Sergey Antonov :
> Hi, Alexei!
>
> Thank you for reply!
>
> > The states ACTIVE, INACTIVE, READ-ONLY look confusing. Actually
> rea
k...@gmail.com
> > > > > >:
> > > > >
> > > > > > +1 for Dmitry Pavlov
> > > > > >
> > > > > > ср, 30 окт. 2019 г. в 18:22, aealexsandrov <
> > aealexsand...@gmail.com
> > > >:
> > > > > >
> > > > > > > +1 Alexey Goncharuk
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sent from:
> > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Best regards,
> > > > > > Alexei Scherbakov
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
BR, Sergey Antonov
pdate value in cache.
User could get ClusterReadOnlyModeException in this case.
So we should return state with lower functionality from previous and
current states for avoiding unexpected behaviour.
чт, 31 окт. 2019 г. в 18:24, Alexei Scherbakov :
> Sergey Antonov,
>
> > Read-only
Igniters, ticket[1] in patch available state.
Anybody want to review changes?
[1] https://issues.apache.org/jira/browse/IGNITE-12225
пн, 25 нояб. 2019 г. в 14:56, Sergey Antonov :
> Alexei Scherbakov,
>
> > After activation (in read-only mode or not) rebalancing is possible to
>
/github.com/apache/ignite-extensions).
> > >
> > > PR https://github.com/apache/ignite/pull/7222
> > >
> > > jira : IGNITE-12356 Migrate Flink module to ignite-extensions
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-12356
> > >
> > > Please review and share feedback.
> > >
> > > Regards,
> > > Saikat
> > >
> >
>
--
BR, Sergey Antonov
> update the streamers testsuite to accommodate the change.
> >
> > Regards,
> > Saikat
> >
> > On Tue, Dec 31, 2019 at 10:39 AM Sergey Antonov <
> antonovserge...@gmail.com>
> > wrote:
> >
> >> Hello, Saikat, Ilya.
> >>
&
butors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 15:01:08 02-01-2020
>
--
BR, Sergey Antonov
Igniters, I prepared PR with fix [1].
Can someone merge it?
[1] https://github.com/apache/ignite/pull/7224/files
сб, 4 янв. 2020 г. в 12:08, Sergey Antonov :
> Hi!
>
> I'll fix failures under ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12520
>
>
+1
I'm preparing patch for 2.8 branch now. TC Bot visa for 2.8 branch will be
at 13 Jan
чт, 9 янв. 2020 г., 21:06 Ivan Pavlukhin :
> +1
>
> чт, 9 янв. 2020 г. в 16:38, Ivan Rakov :
> >
> > Maxim M. and anyone who is interested,
> >
> > I suggest to include this fix to 2.8 release:
> > https://is
che/ignite/pull/7194
> [3]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolvedissues(notrelatedtodocumentation)
>
> On Thu, 9 Jan 2020 at 19:01, Alexey Zinoviev
> wrote:
> >
> > +1
> >
> > чт, 9 янв. 2020 г. в 18:52, Serg
in client API and protocol and in the
> > same
> > > > > Ignite version deprecate these methods for servers and thick
> clients.
> > > > >
> > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-11709
> > > > > [2]: https://issues.apache
kolay, -1 from me, too.
> >> >
> >> > >Hello, Igniters.
> >> > >
> >> > >I’m -1 to include the read-only patch to 2.8.
> >> > >I think we shouldn’t accept any patches to 2.8 except bug fixes for
> >> > blockers a
/7238
> [2] https://issues.apache.org/jira/browse/IGNITE-11256
>
> On Sat, 11 Jan 2020 at 17:59, Sergey Antonov
> wrote:
> >
> > Guys, I created two pull requests [1] [2] for 2.8 release.
> >
> > First of them [1] is a patch with ticket [3] for ignite-2.8 branch.
gt; modules/zookeeper/pom.xml - transitive Jackson from Curator
> > >
> > > I'd suggest to uprgrade commons-beanutils:commons-beanutils to 1.9.4
> and
> > > override com.fasterxml.jackson.core:jackson-databind to our common
> jackson
> > > version from other modules.
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
>
--
BR, Sergey Antonov
Maxim,
Conflicts in pr [1] are resolved. TC Run all is started.
[1] https://github.com/apache/ignite/pull/7238
пт, 17 янв. 2020 г. в 16:04, Sergey Antonov :
> Maxim,
>
> I will do that on monday (20/01).
>
> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov :
>
>> Sergey,
gt; >
> > [1]
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/lang/IgniteExperimental.java
> > [2]
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Public-API-deprecation-rules-td45647.html
> >
> > Thanks,
> > --AG
>
>
>
> --
> Best Regards, Vyacheslav D.
>
--
BR, Sergey Antonov
t; On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <
> mmu...@apache.org>
> > >> wrote:
> > >> >> > > > >
> > >> >> > > > > Igniters,
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > I've prepared the issue [1] and PR [2] with removing
> @deprecate
> > >> >> > > > > annotation on DataRegionMetrics and adding
> @IgniteExperimental
> > >> to the
> > >> >> > > > > new metrics API.
> > >> >> > > > > Can anyone review my changes?
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > >> >> > > > > [2] https://github.com/apache/ignite/pull/7440
> > >> >> > > > >
> > >> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> > >> ilya.kasnach...@gmail.com>
> > >> >> > > > wrote:
> > >> >> > > > > >
> > >> >> > > > > > Hello!
> > >> >> > > > > >
> > >> >> > > > > > I have just merged a fix for embarrassing issue where you
> > >> could UPDATE
> > >> >> > > > > > entries with Spring Data, but not "Update" or "update"
> them.
> > >> >> > > > > >
> > >> >> > > > > > I suggest adding this fix to the scope of 2.8, since
> Spring
> > >> Data is
> > >> >> > > > popular
> > >> >> > > > > > and it does not in any way affect code outside of its
> > >> modules.
> > >> >> > > > > >
> > >> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > >> >> > > > > >
> > >> >> > > > > > WDYT?
> > >> >> > > > > >
> > >> >> > > > > > Regards,
> > >> >> > > > > > --
> > >> >> > > > > > Ilya Kasnacheev
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
> > >> mmu...@apache.org>:
> > >> >> > > > > >
> > >> >> > > > > > > Alexey,
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > Yes. I will remove @deprecation according to the vote
> > >> results and
> > >> >> > > > will
> > >> >> > > > > > > go further with the release steps [1] since there no
> > >> blockers left.
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > [1]
> > >> >> > > >
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >> >> > > > > > >
> > >> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > >> >> > > > > > > wrote:
> > >> >> > > > > > > >
> > >> >> > > > > > > > Folks,
> > >> >> > > > > > > >
> > >> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as
> experimental)
> > >> to master
> > >> >> > > > and
> > >> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
> > >> from the old
> > >> >> > > > > > > metrics
> > >> >> > > > > > > > and start the vote?
> > >> >> > > > > > >
> > >> >> > > >
> > >>
> > >
>
--
BR, Sergey Antonov
Guys, can somebody check those links from TC account different from @
apache.org domain?
пт, 28 февр. 2020 г. в 11:58, Pavel Tupitsyn :
> Sergey, can't confirm, those links work for me
>
> On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov >
> wrote:
>
> > Hello, Max
1]
> https://ci.ignite.apache.org/viewLog.html?buildId=5085462&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildResultsDiv
>
> On Thu, 27 Feb 2020 at 23:17, Sergey Antonov
> wrote:
> >
> > Hello, Maxim!
> >
> > All your li
0.
Still can't get access to teamcity links.
пн, 2 мар. 2020 г., 17:24 Alexey Zinoviev :
> +1 (binding)
> I've downloaded the binary archive, run it, checked the ML examples and
> JavaDocs.
>
>
>
> вс, 1 мар. 2020 г. в 13:49, Ivan Pavlukhin :
>
> > +1 (binding)
> >
> > Downloaded binary distribut
gt; > MOVING due to counter difference on node join.
> > IGNITE-12551 Partition desync if a partition is evicted then owned again
> > and historically rebalanced
> > IGNITE-12536 Inconsistency between cache data and indexes when cache
> > operation is interrupted
> > IGNITE-12403 Throttle page difference output in PageMemoryTracker
> > IGNITE-12523 Continuously generated thread dumps in failure processor
> slow
> > down the whole system
> > IGNITE-12489 Error during purges by expiration: Unknown page type
>
--
BR, Sergey Antonov
ionKeyV2 [grpId=1544803905, grpName=default,
> >> > partId=7]
> >> > Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> >> > consistentId=gridCommandHandlerTest2, updateCntr=3,
> >> partitionState=MOVING,
> >> > state=MOVING]] .. and so on
> >> >
> >> > I found this erroneous and can lead to further cluster index
> corruption,
> >> > for example in case when only command OK result checked.
> >> >
> >> > If no objections would be here, i plan to inform about moving states
> as
> >> > not OK exit code too.
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Vladislav Pyatkov
> >> Architect-Consultant "GridGain Rus" Llc.
> >> +7-929-537-79-60
> >>
>
>
>
>
--
BR, Sergey Antonov
tNull too and to add such check to checkstyle
> > plugin too?
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-@Annotations
> >
>
--
BR, Sergey Antonov
with this change?
> WDYT?
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Naming
> [2]
> https://web.archive.org/web/20120911192801/developers.sun.com/sunstudio/products/archive/whitepapers/java-style.pdf
> [3] https://gith
rties.html#IGNITE_MAX_INDEX_PAYLOAD_SIZE
--
BR, Sergey Antonov
-27T15:30:20.950
> > Command [CACHE] started
> > Arguments: --cache check_index_inline_sizes --yes
> >
> >
> ----------------
> > Found 2 secondary indexes.
> > All secondary indexes have the same effective inline size on all cluster
> > nodes.
> > Command [CACHE] finished with code: 0
> > Control utility has completed execution at: 2020-04-27T15:30:23.428
> > Execution time: 2478 ms
> >
> > Any objections?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12942
> > [2] https://apacheignite-sql.readme.io/docs/create-index
> > [3]
> >
> >
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteSystemProperties.html#IGNITE_MAX_INDEX_PAYLOAD_SIZE
> >
> > --
> > BR, Sergey Antonov
> >
>
--
BR, Sergey Antonov
IGNITE_MAX_INDEX_PAYLOAD_SIZE parameter when it's advised to pass
> > INLINE_SIZE to CREATE TABLE to change the index size cluster-wide.
> >
> > -
> > Denis
> >
> >
> > On Mon, Apr 27, 2020 at 5:38 AM Sergey Antonov <
> antonovserge...@gmail.co
from the application developer perspective.
> > > However, I'm curious why would the one change some low-level
> > > IGNITE_MAX_INDEX_PAYLOAD_SIZE parameter when it's advised to pass
> > > INLINE_SIZE to CREATE TABLE to change the index size cluster-wide.
> &
so why we should care about it?
>
> On Tue, 28 Apr 2020 at 14:32, Sergey Antonov
> wrote:
> >
> > Maxim,
> >
> > > should we _reject_ joining nodes which have different
> > From my point of view, it's a breaking change on cluster update.
> >
Hi, the ticket is ready for review.
[1] https://github.com/apache/ignite/pull/7728
вт, 28 апр. 2020 г. в 14:39, Sergey Antonov :
> Maxim, I'm talking about cluster upgrade through cluster stop -> binary
> update -> cluster start.
>
> вт, 28 апр. 2020 г. в 14:37, Maxim
he following:
> >
> >
> > * store binary meta and marshaller data inside db/ folder
> > * if binary meta of marshaller are found in "legacy" locations --
> > safely move them to new locations during the node startup
> >
> >
> > Kind regards,
> >
> > Semyon Danilov.
> >
>
--
BR, Sergey Antonov
debugging.
> > 2. Almost every system with transactions has timeout enabled by default.
> >
> > WDYT?
> >
> > --
> > Best Regards,
> > Ivan Rakov
> >
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
--
BR, Sergey Antonov
ilure/StopNodeOrHaltFailureHandler.html
[2]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/failure/StopNodeFailureHandler.html
[3]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/Ignition.html#KILL_EXIT_CODE
--
BR, Sergey Antonov
I've created the Ignite ticket for this improvement [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13047
чт, 21 мая 2020 г. в 00:46, Sergey Antonov :
> Hello, Igniters!
>
> I'd like to discuss behaviour of Ignite process exit code if the node was
> stopped by fail
://issues.apache.org/jira/browse/IGNITE-13071
--
BR, Sergey Antonov
Maxim, I'd prefer to do this with a separate ticket.
вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov :
> Sergey,
>
> Sounds good!
> Should we consider removing the deprecated methods `active()`,
> `active(boolean active)` from tests also?
>
> On Tue, 26 May 2020 at 12:1
Maxim, I've created a ticket [1] for this change.
[1] https://issues.apache.org/jira/browse/IGNITE-13079
вт, 26 мая 2020 г. в 20:09, Sergey Antonov :
> Maxim, I'd prefer to do this with a separate ticket.
>
> вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov :
>
>&g
t;
> > Dev ops/admins/anyone who admins Ignite may want to know it's value
> without
> > going to Java code.
> >
> > чт, 21 мая 2020 г. в 09:39, Zhenya Stanilovsky
> :
> >
> >> Thank you Sergey, as for me — very useful proposal huge +1 here.
> >>
&
gt;
> For me, the exit code makes sense only for StopNodeOrHaltFH with
> tryStop=false (otherwise, the JVM exit is not guaranteed as well), but we
> already use the KILL_EXIT_CODE there.
>
> пн, 1 июн. 2020 г. в 23:19, Sergey Antonov :
>
> > Hello, Kirill!
> >
> &g
I suggest using framework [1] and to do this, take out
> control.sh together with its associated classes in a separate module such
> as "modules/control-utility".
> >
> >Comments, suggestions?
> >
> >[1] - https://picocli.info/
>
>
>
>
--
BR, Sergey Antonov
ords,
> > > StopNodeFH with enabled JVM termination === StopNodeOrHaltFH with
> > > tryStop=false
> > > StopNodeFG with disabled JVM termination ~ StopNodeOrHaltFH with
> > > tryStop=true
> > >
> > > Why have two different failure handlers with identical behavior?
> Perhaps,
> > > there is confusion and we should consider merging these classes into
> one?
>
--
BR, Sergey Antonov
code in shutdown
> hook. We don't know what shut down will try to do and we can't sure
> that node will actually terminated. halt() gives such guarantee.
>
> On Tue, Jun 2, 2020 at 5:35 PM Sergey Antonov
> wrote:
> >
> > Andrey, Alexey, I can't agree wit
> Code Freeze: July 10, 2020
> > Voting Date: July 31, 2020
> > Release Date: August 7, 2019
> >
> > WDYT?
> >
> > [1] :
> >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> >
>
--
BR, Sergey Antonov
[4] https://github.com/apache/ignite/pull/7853/files
вт, 26 мая 2020 г. в 20:28, Sergey Antonov :
> Maxim, I've created a ticket [1] for this change.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13079
>
> вт, 26 мая 2020 г. в 20:09, Sergey Antonov :
>
>> Maxim, I
--exclude-caches and
define format for future options. How about linux like format i.e.
--word1-word2?
--
BR, Sergey Antonov
mean following (?):
> - boolean argument: *--word1-word2*
> - single value argument *--word1-word2=value*
> - multiple values argument *--word1-word2=value1 --word1-word2=value2*
>
>
> On Fri, Jan 11, 2019 at 2:05 PM Sergey Antonov
> wrote:
>
> > Hi, Igniters!
>
Igniters, what do you think about this topic?
пт, 11 янв. 2019 г. в 14:17, Sergey Antonov :
> Sergey,
>
> Not quite, I meant:
> - boolean argument: *--word1-word2*
> - single value argument *--word1-word2 value*
> - multiple values argument *--word1-word2 value1,value2*
>
-11046
[3] http://commons.apache.org/proper/commons-cli/
[4] https://issues.apache.org/jira/browse/IGNITE-10826
[5] https://issues.apache.org/jira/browse/IGNITE-11047
--
BR, Sergey Antonov
in patch
> avaliable status. Could someone review my changes?
>
> BR, Ramil Timerbaev
>
--
BR, Sergey Antonov
the classes are
> internal and unlikely to be used in the wild.
> On paper it’s an incompatible change, of course, but I think in this case
> it’s fine.
>
> My 2 cents,
> Stan
>
> From: Sergey Antonov
> Sent: 23 января 2019 г. 17:10
> To: dev@ignite.apache.org
> Subj
; Considering this, moving CommandHandler from ignite-core to
> > > > ignite-control-utility
> > > > doesn't look that bad. It doesn’t differ to much from any other
> change
> > > > that removes or renames a class.
> > > > There could be required
made JIRA ticket with reproducer [1].
[1] https://issues.apache.org/jira/browse/IGNITE-10789
--
BR, Sergey Antonov
I did a little investigation. In o.a.i.i.p.p.c.c.ClientCacheRequest#cache()
enforced cache with keep binary. Why we should always work binary objects?
чт, 24 янв. 2019 г. в 12:29, Sergey Antonov :
> Hello, Igniters!
>
> I have ignite node with configured cache. The cache have cache
>
over, in most cases you don't have classes on the server, so binary
> mode is the only way.
>
> Interceptor should support both modes, binary or not. Any code can call
> withKeepBinary(), this should be expected.
> Just add if (x instanceof BinaryObject) and go from there.
&g
. 2019 г. в 13:16, Sergey Antonov :
> Hi, Pavel,
>
> "Interceptor should support both modes, binary or not. Any code can call
> withKeepBinary(), this should be expected.
> Just add if (x instanceof BinaryObject) and go from there. "
> I don't agree. The ca
ted here.
> withKeepBinary() call is valid and should not depend on Interceptor
> presence or implementation.
>
> On Thu, Jan 24, 2019 at 1:17 PM Sergey Antonov
> wrote:
>
> > Hi, Pavel,
> >
> > "Interceptor should support both modes, binary or not. Any co
fact is - you can get anything, BinaryObject or any user class, so be
> prepared.
> Good example of older API is CacheEvent, which actually has oldValue() and
> newValue() as Object.
>
> Igniters, any other thoughts?
>
>
> On Thu, Jan 24, 2019 at 2:16 PM Sergey Antonov
>
I think it's bad idea. This contract nowhere defined and it's not clear for
users.
чт, 24 янв. 2019 г. в 17:18, Pavel Tupitsyn :
> Yes
>
> On Thu, Jan 24, 2019 at 5:15 PM Sergey Antonov
> wrote:
>
> > Pavel,
> >
> > "Leave it as is, use instanceof
”.
> > >
> > > If there is an inconsistency between thick and thin clients it should
> be
> > > eliminated. I do not see a reason why behavior should be different.
> > >
> > > If something is a good thing but it is not intuitive it could be
> > >
available with enabled read-only
mode.
More informartion about implementation you could find in PR [2].
What do you think about this feature?
[1] https://issues.apache.org/jira/browse/IGNITE-11256
[2] https://github.com/apache/ignite/pull/6423
--
BR, Sergey Antonov
hat do you think about this feature?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-11256
> > [2] https://github.com/apache/ignite/pull/6423
>
--
BR, Sergey Antonov
nge state back to normal;
> >
> > When the state has been changed to `read-only` I've flooded with a lot
> > of `Failed to perform cache operation (cluster is in read-only mode)`
> > errors, but when I've reverted the state back the DataStreamer
> > contin
e has been changed to `read-only` I've flooded with a lot
> of `Failed to perform cache operation (cluster is in read-only mode)`
> errors, but when I've reverted the state back the DataStreamer
> continue its load without any error. I think we should not allow such
> behaviour
_streamer/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/ClusterReadOnlyModeTest.java#L72
>
> On Tue, 4 Jun 2019 at 14:42, Sergey Antonov
> wrote:
> >
> > Hello, Maxim!
> >
> > >> Do we have an IEP for this feature?
> > No, we don
own. Am I missing something?
>
> [1]
> https://github.com/Mmuzaf/ignite/blob/readonly_streamer/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/ClusterReadOnlyModeTest.java#L72
>
> On Tue, 4 Jun 2019 at 14:42, Sergey Antonov
> wrote:
> >
> > He
HOST_OR_IP] [--port PORT] [--user USER]
> [--password
> >> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> >> --deactivate [--yes]
> >>
> >> ...
> >>
> >> Why do we repeat tons of parameters each time? Is it better for users to
> >> enlist options and commands separately?
> >>
> >> control.sh [options] command
> >>
> >> and then enlist options
> >>
> >> [--host HOST_OR_IP]
> >>
> >> [--port PORT]
> >>
> >> [--user USER]
> >>
> >> [--password PASSWORD]
> >>
> >> [--ping-interval PING_INTERVAL]
> >>
> >> [--ping-timeout PING_TIMEOUT]
> >>
> >> and describe several commands we have?
> >>
> >> In coding WET is not the best solution. So maybe we could DRY in our
> help,
> >> should we?
> >>
> >> Artem Boudnikov, could you evaluate this idea?
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
>
--
BR, Sergey Antonov
think about my proposal?
[1] https://issues.apache.org/jira/browse/IGNITE-12225
--
BR, Sergey Antonov
Also, I would add IGNITE-12225
<https://issues.apache.org/jira/browse/IGNITE-12225> ticket to 2.8 release
scope.
вт, 24 сент. 2019 г. в 16:18, Sergey Antonov :
> Hi, Igniters!
>
> We have 3 cluster states at the moment: inactive, active, read-only.
>
> For getting curr
; >
> > > dpav...@apache.org>
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > +1 For Maxim as release manager.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Maxim,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > It is a good thing that you have committer
> rights,
> > >
> > > and most of
> > > > > > > > > >
> > > > > > > > > > the steps
> > > > > > > > > > > > > > you will be able to complete yourself.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > But please engage one from PMC member to complete
> > >
> > > steps from the
> > > > > > > > > >
> > > > > > > > > > release
> > > > > > > > > > > > > > process where PMC rights are required
> > > > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process At
> > > > > > > > > > > > > > least, access to docker and nuget creds requires
> PMC
> > >
> > > membership.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Feel free to ping me, I will assist, as well.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:59, Alexey Zinoviev <
> > > > > > > > > >
> > > > > > > > > > zaleslaw@gmail.com>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > For Spark and ML components the best dates
> should
> > >
> > > be moved to
> > > > > > > > > >
> > > > > > > > > > one month
> > > > > > > > > > > > > > > later, what's about?
> > > > > > > > > > > > > > > There are a lot of features there, but a lot of
> > >
> > > bugs and minor
> > > > > > > > > > > > > > > improvements in JIRA too
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Also I support you as a release manager
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Scope Freeze: December 4, 2019
> > > > > > > > > > > > > > > Code Freeze: December 18, 2019
> > > > > > > > > > > > > > > Voting Date: January 10, 2019
> > > > > > > > > > > > > > > Release Date: January 17, 2019
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:44, Maxim Muzafarov <
> > > > > > > > > >
> > > > > > > > > > mmu...@apache.org>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > It's almost a year has passed since the last
> > >
> > > major Apache
> > > > > > > > > >
> > > > > > > > > > Ignite 2.7
> > > > > > > > > > > > > > > > has been released. We've accumulated a lot of
> > >
> > > performance
> > > > > > > > > > > > >
> > > > > > > > > > > > > improvements
> > > > > > > > > > > > > > > > and a lot of new features which are waiting
> for
> > >
> > > their release
> > > > > > > > > >
> > > > > > > > > > date.
> > > > > > > > > > > > > > > > Here is my list of the most interesting
> things
> > >
> > > from my point
> > > > > > > > > >
> > > > > > > > > > since
> > > > > > > > > > > > >
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > last major release:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Service Grid,
> > > > > > > > > > > > > > > > Monitoring,
> > > > > > > > > > > > > > > > Recovery Read
> > > > > > > > > > > > > > > > BLT auto-adjust,
> > > > > > > > > > > > > > > > PDS compression,
> > > > > > > > > > > > > > > > WAL page compression,
> > > > > > > > > > > > > > > > Thin client: best effort affinity,
> > > > > > > > > > > > > > > > Thin client: transactions support (not yet)
> > > > > > > > > > > > > > > > SQL query history
> > > > > > > > > > > > > > > > SQL statistics
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I think we should no longer wait and freeze
> the
> > >
> > > master branch
> > > > > > > > > >
> > > > > > > > > > anymore
> > > > > > > > > > > > > > > > and prepare the next major release by the
> end of
> > >
> > > the year.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I propose to discuss Time, Scope of Apache
> > >
> > > Ignite 2.8 release
> > > > > > > > > >
> > > > > > > > > > and
> > > > > > > > > > > > >
> > > > > > > > > > > > > also
> > > > > > > > > > > > > > > > I want to propose myself to be the release
> > >
> > > manager of the
> > > > > > > > > >
> > > > > > > > > > planning
> > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Scope Freeze: November 4, 2019
> > > > > > > > > > > > > > > > Code Freeze: November 18, 2019
> > > > > > > > > > > > > > > > Voting Date: December 10, 2019
> > > > > > > > > > > > > > > > Release Date: December 17, 2019
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > > > > >
>
--
BR, Sergey Antonov
ad-only-off commands have if
> current state is INACTIVE ?
>
>
> On Tue, Sep 24, 2019 at 4:23 PM Sergey Antonov
> wrote:
>
> > Also, I would add IGNITE-12225
> > <https://issues.apache.org/jira/browse/IGNITE-12225> ticket to 2.8
> release
> > scope.
&
e cluster:
> control.(sh|bat) --deactivate [--yes]
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-11866
> [2] https://issues.apache.org/jira/browse/IGNITE-12225
>
>
>
> On Tue, 24 Sep 2019 at 16:50, Sergey Antonov
> wrote:
> >
> > Andrey,
>
ur or bug?
--
BR, Sergey Antonov
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
--
BR, Sergey Antonov
members with new
> > > >
> > > > inspection
> > > > > > > > > > failures
> > > > > > > > > > added by them.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Also, I've taken Alexey's inspection file as an example,
> > I’ve
> > > > > >
> > > > > > checked
> > > > > > > what
> > > > > > > > > > we already discussed
> > > > > > > > > > previously (e.g. `Anonymous class can be converted to
> > lambda`
> > > > >
> > > > > should
> > > > > > > be
> > > > > > > > > > disabled by default)
> > > > > > > > > > and added these additional rules to it:
> > > > > > > > > > - General | Line is longer than allowed by code style
> > > > > > > > > > - Java | Code maturity | Call to 'printStackTrace()'
> > > > > > > > > > - Java | Code style issues | Unnecessary 'null' check
> > before
> > > > > > >
> > > > > > > 'equals()'
> > > > > > > > > > call
> > > > > > > > > >
> > > > > > > > > > If we decide to proceed I will attach this file to JIRA.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [1]
> > https://www.jetbrains.com/help/idea/code-inspection.html
> > > > > > > > > > [2]
> > > > > > > > > >
> > > > > > > > > >
> > > >
> > > >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F3710%2Fhead
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, 14 Aug 2018 at 16:19 Dmitriy Pavlov <
> > > > >
> > > > > dpavlov@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Dmitriy Govoruknin,
> > > > > > > > > > >
> > > > > > > > > > > It seems there is a lack of volunteers to apply code
> > > >
> > > > inspections
> > > > > > to
> > > > > > > our
> > > > > > > > > > CI
> > > > > > > > > > > & patch submission process. Probably we could come back
> > to
> > > >
> > > > your
> > > > > > > > > > > initial idea about setting up inspection locally.
> > > > > > > > > > >
> > > > > > > > > > > Could you commit or share your IDEA inspection
> settings?
> > I
> > > >
> > > > could
> > > > > > > apply
> > > > > > > > > > it
> > > > > > > > > > > at least on my machine and remove odd warning types one
> > by
> > > >
> > > > one.
> > > > > > > What do
> > > > > > > > > > you
> > > > > > > > > > > think?
> > > > > > > > > > >
> > > > > > > > > > > Sincerely,
> > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > >
> > > > > > > > > > > сб, 4 авг. 2018 г. в 1:22, Dmitriy Pavlov <
> > > > >
> > > > > dpavlov@gmail.com
> > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Ideally, I should not asking for people to solve
> > something
> > > >
> > > > for
> > > > > > me.
> > > > > > > > > > > >
> > > > > > > > > > > > I just want this idea did not disappear from our
> radar.
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 3 авг. 2018 г. в 23:47, Dmitriy Setrakyan <
> > > > > > >
> > > > > > > dsetrak...@apache.org
> > > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, Aug 3, 2018 at 7:49 AM, Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov@gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I understand it is not so Apache-way from my side
> > to ask
> > > > > > > > > >
> > > > > > > > > > volunteers to
> > > > > > > > > > > > > do
> > > > > > > > > > > > > > some things (instead of contributing it by
> myself).
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Dmitriy, I am not sure why you feel this is not the
> > Apache
> > > > >
> > > > > way.
> > > > > > > No
> > > > > > > > > > one
> > > > > > > > > > > can
> > > > > > > > > > > > > do everything themselves. You should absolutely
> keep
> > > > > >
> > > > > > recruiting
> > > > > > > more
> > > > > > > > > > > > > volunteers from the community.
> > > > > > > > > > > > >
> > > > > > > > > > > > > D.
> > > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > --
> > > > > > > > > > Maxim Muzafarov
> > > > > > > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > Maxim Muzafarov
> > > > >
> >
> --
> --
> Maxim Muzafarov
>
--
BR, Sergey Antonov
Sergey Antonov created IGNITE-13144:
---
Summary: Add attribute methods to ClusterState enum
Key: IGNITE-13144
URL: https://issues.apache.org/jira/browse/IGNITE-13144
Project: Ignite
Issue
Sergey Antonov created IGNITE-12520:
---
Summary: Wrong year in copyright in correct output of control
utility.
Key: IGNITE-12520
URL: https://issues.apache.org/jira/browse/IGNITE-12520
Project
Sergey Antonov created IGNITE-12710:
---
Summary: Extension log in rebuild indexes to search problems
Key: IGNITE-12710
URL: https://issues.apache.org/jira/browse/IGNITE-12710
Project: Ignite
Sergey Antonov created IGNITE-12774:
---
Summary: Transaction hungs after too many open files NIO exception
Key: IGNITE-12774
URL: https://issues.apache.org/jira/browse/IGNITE-12774
Project: Ignite
Sergey Antonov created IGNITE-12803:
---
Summary: Investigate exception message on too many open files in
different OS.
Key: IGNITE-12803
URL: https://issues.apache.org/jira/browse/IGNITE-12803
Sergey Antonov created IGNITE-12942:
---
Summary: control.sh add command for checking that inline size is
same on all cluster nodes
Key: IGNITE-12942
URL: https://issues.apache.org/jira/browse/IGNITE-12942
Sergey Antonov created IGNITE-12955:
---
Summary: Document a new command control.sh --cache
check_index_inline_sizes
Key: IGNITE-12955
URL: https://issues.apache.org/jira/browse/IGNITE-12955
Project
Sergey Antonov created IGNITE-12985:
---
Summary: Fix unguarded log.info/log.debug/log.trace usages
Key: IGNITE-12985
URL: https://issues.apache.org/jira/browse/IGNITE-12985
Project: Ignite
Sergey Antonov created IGNITE-13004:
---
Summary: Fix wrong comparison in
TcpCommunicationSpi#closeConnections(UUID)
Key: IGNITE-13004
URL: https://issues.apache.org/jira/browse/IGNITE-13004
Project
Sergey Antonov created IGNITE-13047:
---
Summary: Ignite node must return Ignition#KILL_EXIT_CODE exit
code, if node had stopped by StopNodeFailureHandler or
StopNodeOrHaltFailureHandler
Key: IGNITE-13047
URL
Sergey Antonov created IGNITE-13071:
---
Summary: Improve test coverage for read-only cluster state
Key: IGNITE-13071
URL: https://issues.apache.org/jira/browse/IGNITE-13071
Project: Ignite
Sergey Antonov created IGNITE-13076:
---
Summary: Cluster read-only mode doesn't affect LOCAL caches
Key: IGNITE-13076
URL: https://issues.apache.org/jira/browse/IGNITE-13076
Project: I
Sergey Antonov created IGNITE-13079:
---
Summary: Replace deprecated cluster activation methods in tests.
Key: IGNITE-13079
URL: https://issues.apache.org/jira/browse/IGNITE-13079
Project: Ignite
Sergey Antonov created IGNITE-13091:
---
Summary: Cluster read-only mode allows to create caches
Key: IGNITE-13091
URL: https://issues.apache.org/jira/browse/IGNITE-13091
Project: Ignite
Sergey Antonov created IGNITE-13102:
---
Summary: IgniteCache#isClosed() returns false on server node even
if the cache had closed before.
Key: IGNITE-13102
URL: https://issues.apache.org/jira/browse/IGNITE-13102
1 - 100 of 171 matches
Mail list logo