[GitHub] ignite pull request #4363: IGNITE-7752: Update Ignite KafkaStreamer to use n...

[shroman]

GitHub user shroman opened a pull request:

https://github.com/apache/ignite/pull/4363

IGNITE-7752: Update Ignite KafkaStreamer to use new consumer.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shroman/ignite IGNITE-7752

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4363.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4363


commit b099602287ac1282b3b3fcb094e601c1f9e33e52
Author: shroman 
Date:   2018-07-14T05:56:00Z

IGNITE-7752: Update Ignite KafkaStreamer to use new consumer.

commit 8eafc4c305b6c069b7b63b7d4d567a7160b17043
Author: shroman 
Date:   2018-07-14T05:56:33Z

IGNITE-7752: Update Ignite KafkaStreamer to use new consumer.




---

Re: [MTCGA]: new failures in builds [1490510, 1490413] needs to be handled

[Dmitry Pavlov]

Please ignore this also.

These failures came from mass weekend tests master run and flaky tests
which unluckily failed simultaneously 3 times a row, so bot considered it
as new failures.

сб, 14 июл. 2018 г., 0:22 :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgnitePdsCorruptedStoreTest.testCacheMetaCorruption
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6523479222827749257&branch=%3Cdefault%3E&tab=testDetails
>  No changes in build
>
>  *New test failure in master
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7534554859858291194&branch=%3Cdefault%3E&tab=testDetails
>
>  *New test failure in master
> IgnitePdsTxCacheRebalancingTest.testTopologyChangesWithConstantLoad
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3769512162483462816&branch=%3Cdefault%3E&tab=testDetails
>  Changes may led to failure were done by - ilya.kasnacheev
> http://ci.ignite.apache.org/viewModification.html?modId=825627&personal=false
>  - vinokurov.pasha
> http://ci.ignite.apache.org/viewModification.html?modId=825609&personal=false
>  - agura
> http://ci.ignite.apache.org/viewModification.html?modId=825604&personal=false
>  - ezagumennov
> http://ci.ignite.apache.org/viewModification.html?modId=825579&personal=false
>  - amedvedev
> http://ci.ignite.apache.org/viewModification.html?modId=825566&personal=false
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Sat Jul 14 00:21:58 MSK 2018
>

[MTCGA]: new failures in builds [1490510, 1490413] needs to be handled

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New test failure in master 
IgnitePdsCorruptedStoreTest.testCacheMetaCorruption 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6523479222827749257&branch=%3Cdefault%3E&tab=testDetails
 No changes in build

 *New test failure in master 
IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7534554859858291194&branch=%3Cdefault%3E&tab=testDetails

 *New test failure in master 
IgnitePdsTxCacheRebalancingTest.testTopologyChangesWithConstantLoad 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3769512162483462816&branch=%3Cdefault%3E&tab=testDetails
 Changes may led to failure were done by - ilya.kasnacheev 
http://ci.ignite.apache.org/viewModification.html?modId=825627&personal=false
 - vinokurov.pasha 
http://ci.ignite.apache.org/viewModification.html?modId=825609&personal=false
 - agura 
http://ci.ignite.apache.org/viewModification.html?modId=825604&personal=false
 - ezagumennov 
http://ci.ignite.apache.org/viewModification.html?modId=825579&personal=false
 - amedvedev 
http://ci.ignite.apache.org/viewModification.html?modId=825566&personal=false

- If your changes can led to this failure(s), please create issue with 
label MakeTeamCityGreenAgain and assign it to you.
-- If you have fix, please set ticket to PA state and write to dev list 
fix is ready 
-- For case fix will require some time please mute test and set label 
Muted_Test to issue 
- If you know which change caused failure please contact change author 
directly
- If you don't know which change caused failure please send message to 
dev list to find out
Should you have any questions please contact dpav...@apache.org or write to 
dev.list 
Best Regards,
MTCGA.Bot 
Notification generated at Sat Jul 14 00:21:58 MSK 2018 

Re: MVCC and IgniteDataStreamer

[Denis Magda]

Agree that initial loading and real-time streaming should be seen as
different use cases.

For the loading part, I would borrow ideas from direct data load IEP [1].
Ignite should assume that no app works with the cluster until it's
preloaded. So, no global locks or things like that. Just fasten a seat belt
and feed data to your nodes.

For the streaming part, I would consider 2 or 3 proposed by Igor.

--
Denis

[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-22%3A+Direct+Data+Load

On Fri, Jul 13, 2018 at 10:03 AM Seliverstov Igor 
wrote:

> Ivan,
>
> Anyway DataStreamer is the fastest way to deliver data to a data node, the
> question is how to apply it correctly.
>
> I don’t thing we need one more tool, which 90% is the same as DataStreamer.
>
> All we need is just to implement a couple of new stream receivers.
>
> Regards,
> Igor
>
> > 13 июля 2018 г., в 9:56, Павлухин Иван  написал(а):
> >
> > Hi Igniters,
> >
> > I had a look into IgniteDataStreamer. As far as I understand, currently
> it
> > just works incorrectly for MVCC tables. It appears as a blocker for
> > releasing MVCC. The simplest thing is to refuse creating streamer for
> MVCC
> > tables.
> >
> > Next step could be hair splitting of related use cases. For me, initial
> > load and continuous streaming look quite different cases and it is better
> > to keep them separate at least at API level. Perhaps, it is better to
> > separate API basing on user experience. For example, DataStreamer could
> be
> > considered tool without surprises (which means leaving data always
> > consistent, transactions). And let's say BulkLoader is a beast for
> fastest
> > data loading but full of surprises. Such surprises could be locking
> tables,
> > rolling back user transactions and so on. So, it is of very limited use
> > (like initial load). Keeping API entities separate looks better for me
> than
> > introducing multiple modes, because separated entities are easier for
> > understanding and so less prone to user mistakes.
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
>
>

Re: Application of various Complex object types

[Denis Magda]

Dmitriy,

Even though it makes sense to support SQL queries that can return a
deserialized object, the primary use case for SQL is pretty straightforward
[1]:
- configure your schema with DDL (CREATE TABLE, CREATE INDEX, etc.)
- run queries and get a result set of raw fields (what you get with any
RDBMS).

This primary use case assumes you're not dealing with complex objects.

[1]
https://apacheignite.readme.io/v2.5/docs/nodejs-thin-client#section-sql-fields-query

--
Denis

On Fri, Jul 13, 2018 at 11:17 AM Igor Sapego  wrote:

> Hi, Dmitry,
>
> To get objects with full schema in footer you should just start your node
> with config, which is going to have compactFooter set to "false" in it:
>
> 
>   
> 
>   
> 
>
> For example, C++ server nodes use full footer in schema.
>
> Two other cases - no schema and raw data are just the ways objects are
> written. When you write some fields as named fields, and then write other
> fields in raw mode, objects are going to have raw data in them. When all
> fields in object are written in a raw mode, it contains no schema. So,
> basically, you can get such objects from any cache, if this is how a user
> have chosen to serialize them.
>
> Best Regards,
> Igor
>
>
> On Fri, Jul 13, 2018 at 6:44 PM Dmitry Melnichuk <
> dmitry.melnic...@nobitlost.com> wrote:
>
> > Hello fellow Ignite developers!
> >
> > As you may already know, I am building Ignite thin client API library in
> > Python. I have reached the point where all applicable operations are
> > implemented. All data types are also fully covered, except for some
> > variants of Complex object.
> >
> > I have been already told that Ignite stores its SQL tables using a
> > Complex object data type. It lets me write parser and builder for that
> > exact variant of Complex object used for an SQL row:
> >
> > - compact footer approach, all fields are named.
> >
> > Now I wonder if I can find any other real-life usage example of Complex
> > objects
> >
> > - with no schema,
> > - with full schema in footer,
> > - with raw data.
> >
> > Your advice is greatly appreciated.
> >
> > Ideally I should be able to automate the creation of various kinds of
> > Complex objects to build my unit tests upon it.
> >
> > Dmitry
> >
>

Re: [MTCGA]: new failures in builds [1398134] needs to be handled

[Dmitry Pavlov]

Hi, it seems it is duplicate, so please ignore.

I will find out how duplicate notification ocurred.

пт, 13 июл. 2018 г. в 22:51, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgniteNativeIoPdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-7843429397229340143&branch=%3Cdefault%3E&tab=testDetails
>  No changes in build
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Fri Jul 13 22:51:51 MSK 2018
>

[MTCGA]: new failures in builds [1398134] needs to be handled

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New test failure in master 
IgniteNativeIoPdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-7843429397229340143&branch=%3Cdefault%3E&tab=testDetails
 No changes in build

- If your changes can led to this failure(s), please create issue with 
label MakeTeamCityGreenAgain and assign it to you.
-- If you have fix, please set ticket to PA state and write to dev list 
fix is ready 
-- For case fix will require some time please mute test and set label 
Muted_Test to issue 
- If you know which change caused failure please contact change author 
directly
- If you don't know which change caused failure please send message to 
dev list to find out
Should you have any questions please contact dpav...@apache.org or write to 
dev.list 
Best Regards,
MTCGA.Bot 
Notification generated at Fri Jul 13 22:51:51 MSK 2018 

Re: Neighbors exclusion

[Valentin Kulichenko]

Dmitry,

Good point. I think it makes sense to even remove (deprecate) the
excludeNeighbors property and always distribute primary and backups to
different physical hosts in this scenario. Because why would anyone ever
set this to false if we switch default to true? This also automatically
fixes the confusing behavior of backupFilter - it should never be ignored
if it's set.

-Val

On Fri, Jul 13, 2018 at 8:05 AM Dmitry Karachentsev <
dkarachent...@gridgain.com> wrote:

> Hi folks,
>
> Why RendezvousAffinityFunction.excludeNeighbors [1] is false by default?
> It's not obvious that if user wants to run more than one node per
> machine it has also set this flag to true explicitly. Maybe it would be
> better to set it to true by default?
>
> At the same time if excludeNeighbors is true, it ignores backupFilter.
> Why it's not vice-versa? For example:
>
> 1) if backupFilter is set - it will be used,
>
> 2) if there are not enough backup nodes (or no backupFilter) - try to
> distribute according to excludeNeighbors = true,
>
> 3) if this is not possible too (or excludeNeighbors) = false - assign
> partitions as possible.
>
> [1]
>
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html#setExcludeNeighbors-boolean-
>
> Are there any drawbacks in such approach?
>
> Thanks!
>
>

[RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Andrey Gura]

Igniters,

Apache Ignite 2.6.0 release (RC1) has been accepted.

5 "+1" binding votes received:

- Alexey Goncharuk
- Alexey Kuznetsov
- Andrey Gura
- Anton Vinogradov
- Denis Magda

Vote thread:

*http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
*

Ignite 2.6.0 will be released soon.

[GitHub] ignite pull request #4296: IGNITE-8564 Clear affinity mapping cache when cli...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4296


---

[GitHub] ignite pull request #4331: IGNITE-8912 PartitionLossPolicy.READ_ONLY_SAFE do...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4331


---

Re: MTCGA: new failures in builds [1485687] needs to be handled

[Dmitry Pavlov]

I've created https://issues.apache.org/jira/browse/IGNITE-9005 to fix

Stanislav L. kindly agreed to fix this failure.

пт, 13 июл. 2018 г. в 12:09, Dmitry Pavlov :

> I suspect this change may case this failure:
> kcheng.mvp (kcheng.mvp) IGNITE-8776  Eviction policy MBeans are never
> registered if
> so I'm going to take a look.
>
> пт, 13 июл. 2018 г. в 10:59, :
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *New test failure in master
>> GridCacheLifecycleAwareSelfTest.testLifecycleAware
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7246907407546697403&branch=%3Cdefault%3E&tab=testDetails
>>  Changes may led to failure were done by dpavlov
>> http://ci.ignite.apache.org/viewModification.html?modId=825539&personal=false,
>> eduard.shangareev
>> http://ci.ignite.apache.org/viewModification.html?modId=825536&personal=false,
>> kcheng.mvp
>> http://ci.ignite.apache.org/viewModification.html?modId=825531&personal=false,
>> dmitriyff
>> http://ci.ignite.apache.org/viewModification.html?modId=825495&personal=false,
>> alexey.scherbakoff
>> http://ci.ignite.apache.org/viewModification.html?modId=825466&personal=false,
>> anovikov
>> http://ci.ignite.apache.org/viewModification.html?modId=825458&personal=false,
>> akuznetsov
>> http://ci.ignite.apache.org/viewModification.html?modId=825455&personal=falseIf
>> your changes can led to this failure(s), please create issue with label
>> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
>> set ticket to PA state and write to dev list fix is readyFor case
>> fix will require some time please mute test and set label Muted_Test to
>> issueIf you know which change caused failure please
>> contact change author directlyIf you don't know which change
>> caused failure please send message to dev list to find
>> outShould you have any questions please contact
>> dpav...@apache.org or write to dev.listBest
>> Regards,MTCGA.BotNotification generated at Fri Jul 13 10:58:57 MSK
>> 2018
>
>

[jira] [Created] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-9005:
--

 Summary: Eviction policy MBeans change failed LifecycleAwareTest 
on cache name injectoin
 Key: IGNITE-9005
 URL: https://issues.apache.org/jira/browse/IGNITE-9005
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov
Assignee: Stanislav Lukyanov
 Fix For: 2.7


http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
New test failure detected 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7246907407546697403&branch=%3Cdefault%3E&tab=testDetails

after merging 
IGNITE-8776 Eviction policy MBeans are never registered if 
evictionPolicyFactory is used 

Revert of commit makes test passing.

Locally test also failed. Failed with message
{noformat}
Unexpected cache name for 
org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
 expected: but was:
{noformat}

Message of failure seems to be related to TestEvictionPolicy instance from test 
class. 

Seems that returing call to cctx.kernalContext (). resource (). injectCacheName 
(rsrc, cfg.getName ()); should fix issue.







--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Application of various Complex object types

[Igor Sapego]

Hi, Dmitry,

To get objects with full schema in footer you should just start your node
with config, which is going to have compactFooter set to "false" in it:


  

  


For example, C++ server nodes use full footer in schema.

Two other cases - no schema and raw data are just the ways objects are
written. When you write some fields as named fields, and then write other
fields in raw mode, objects are going to have raw data in them. When all
fields in object are written in a raw mode, it contains no schema. So,
basically, you can get such objects from any cache, if this is how a user
have chosen to serialize them.

Best Regards,
Igor


On Fri, Jul 13, 2018 at 6:44 PM Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Hello fellow Ignite developers!
>
> As you may already know, I am building Ignite thin client API library in
> Python. I have reached the point where all applicable operations are
> implemented. All data types are also fully covered, except for some
> variants of Complex object.
>
> I have been already told that Ignite stores its SQL tables using a
> Complex object data type. It lets me write parser and builder for that
> exact variant of Complex object used for an SQL row:
>
> - compact footer approach, all fields are named.
>
> Now I wonder if I can find any other real-life usage example of Complex
> objects
>
> - with no schema,
> - with full schema in footer,
> - with raw data.
>
> Your advice is greatly appreciated.
>
> Ideally I should be able to automate the creation of various kinds of
> Complex objects to build my unit tests upon it.
>
> Dmitry
>

[GitHub] ignite pull request #4362: IGNITE-9004 rollback formatFile changes

[akalash]

GitHub user akalash opened a pull request:

https://github.com/apache/ignite/pull/4362

IGNITE-9004 rollback formatFile changes



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9004

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4362.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4362


commit e431f2311fc756b0945ac20ee24b1a768a4d8c62
Author: Anton Kalashnikov 
Date:   2018-07-13T15:53:30Z

IGNITE-9004 rollback formatFile changes




---

[jira] [Created] (IGNITE-9004) Failed to move temp file during segment creation

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-9004:
-

 Summary: Failed to move temp file during segment creation
 Key: IGNITE-9004
 URL: https://issues.apache.org/jira/browse/IGNITE-9004
 Project: Ignite
  Issue Type: Test
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov


Reproduced by Activate/Deactivate suit, for example  
IgniteChangeGlobalStateTest#testStopPrimaryAndActivateFromClientNode

{noformat}

class org.apache.ignite.internal.pagemem.wal.StorageException: Failed to move 
temp file to a regular WAL segment file: /data/teamcity/work/c182b70f2dfa650
7/work/IgniteChangeGlobalStateTest/db/wal/node1/0002.wal
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.createFile(FileWriteAheadLogManager.java:1446)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkFiles(FileWriteAheadLogManager.java:2269)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$4500(FileWriteAheadLogManager.java:143)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.allocateRemainingFiles(FileWriteAheadLogManage
r.java:1862)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.body(FileWriteAheadLogManager.java:1606)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
java.lang.Thread.run(Thread.java:748)
[13:56:05]W: [org.apache.ignite:ignite-core] Caused by: 
java.nio.file.NoSuchFileException: 
/data/teamcity/work/c182b70f2dfa6507/work/IgniteChangeGlobalStateTest/db/wal/node1/0002.wal.tmp
[13:56:05]W: [org.apache.ignite:ignite-core] at 
sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
java.nio.file.Files.move(Files.java:1395)
[13:56:05]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.createFile(FileWriteAheadLogManager.java:1442)
[13:56:05]W: [org.apache.ignite:ignite-core] ... 6 more

{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Application of various Complex object types

[Dmitry Melnichuk]

Hello fellow Ignite developers!

As you may already know, I am building Ignite thin client API library in 
Python. I have reached the point where all applicable operations are 
implemented. All data types are also fully covered, except for some 
variants of Complex object.


I have been already told that Ignite stores its SQL tables using a 
Complex object data type. It lets me write parser and builder for that 
exact variant of Complex object used for an SQL row:


- compact footer approach, all fields are named.

Now I wonder if I can find any other real-life usage example of Complex 
objects


- with no schema,
- with full schema in footer,
- with raw data.

Your advice is greatly appreciated.

Ideally I should be able to automate the creation of various kinds of 
Complex objects to build my unit tests upon it.


Dmitry

TeamCity: Mass run-all during weekend

[Dmitry Pavlov]

Hi Igniters,

I am going to start mass run-all during weekend and will shedule 30 builds
at 20.30 MSK today, if nobody minds.

Sincerely,
Dmitriy Pavlov

[GitHub] ignite pull request #4361: IGNITE-9002: Fixed C++ thin client crash when use...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/4361

IGNITE-9002: Fixed C++ thin client crash when used with dynamic cache 
without config



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9002

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4361.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4361


commit 88bdec61ba3a4855de354744b9f4d9a4e8dd9045
Author: Igor Sapego 
Date:   2018-07-13T15:19:55Z

IGNITE-9002: Added test.

commit 8d4acbdf230af01d082a6101f54002844c90dedf
Author: Igor Sapego 
Date:   2018-07-13T15:21:00Z

IGNITE-9002: Fixed issue

commit d86ab299341fec69a4892820d34b8d6b83ecc59e
Author: Igor Sapego 
Date:   2018-07-13T15:22:00Z

IGNITE-9002: Bumped protocol version

commit 39bebb18e6b828d3760fcf67cd7b6a6f4a4dde57
Author: Igor Sapego 
Date:   2018-07-13T15:22:37Z

IGNITE-9002: Added default constructors for CacheClient and IgniteClient




---

Neighbors exclusion

[Dmitry Karachentsev]

Hi folks,

Why RendezvousAffinityFunction.excludeNeighbors [1] is false by default? 
It's not obvious that if user wants to run more than one node per 
machine it has also set this flag to true explicitly. Maybe it would be 
better to set it to true by default?


At the same time if excludeNeighbors is true, it ignores backupFilter. 
Why it's not vice-versa? For example:


1) if backupFilter is set - it will be used,

2) if there are not enough backup nodes (or no backupFilter) - try to 
distribute according to excludeNeighbors = true,


3) if this is not possible too (or excludeNeighbors) = false - assign 
partitions as possible.


[1] 
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html#setExcludeNeighbors-boolean-


Are there any drawbacks in such approach?

Thanks!

[jira] [Created] (IGNITE-9003) walSegmentsCleared piece of checkpoint logging improvement

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-9003:
---

 Summary: walSegmentsCleared piece of checkpoint logging improvement
 Key: IGNITE-9003
 URL: https://issues.apache.org/jira/browse/IGNITE-9003
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Sergey Chugunov
 Fix For: 2.7


In the IGNITE-8737 ticket *walSegmentsCovered* piece was added: now on 
checkpoint finish absolute indexes of all wal segments that are not needed 
anymore for restoring from this checkpoint are logged at info level.

The same thing should be done for *walSegmentsCleared* piece: instead of number 
of cleared segments index range should be printed out.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: MVCC and IgniteDataStreamer

[Seliverstov Igor]

Ivan,

Anyway DataStreamer is the fastest way to deliver data to a data node, the 
question is how to apply it correctly.

I don’t thing we need one more tool, which 90% is the same as DataStreamer.

All we need is just to implement a couple of new stream receivers.

Regards,
Igor

> 13 июля 2018 г., в 9:56, Павлухин Иван  написал(а):
> 
> Hi Igniters,
> 
> I had a look into IgniteDataStreamer. As far as I understand, currently it
> just works incorrectly for MVCC tables. It appears as a blocker for
> releasing MVCC. The simplest thing is to refuse creating streamer for MVCC
> tables.
> 
> Next step could be hair splitting of related use cases. For me, initial
> load and continuous streaming look quite different cases and it is better
> to keep them separate at least at API level. Perhaps, it is better to
> separate API basing on user experience. For example, DataStreamer could be
> considered tool without surprises (which means leaving data always
> consistent, transactions). And let's say BulkLoader is a beast for fastest
> data loading but full of surprises. Such surprises could be locking tables,
> rolling back user transactions and so on. So, it is of very limited use
> (like initial load). Keeping API entities separate looks better for me than
> introducing multiple modes, because separated entities are easier for
> understanding and so less prone to user mistakes.
> 
> -- 
> Best regards,
> Ivan Pavlukhin

Re: Async cache groups rebalance not started with rebalanceOrder ZERO

[Yakov Zhdanov]

Maxim, I do not understand the problem. Imagine I do not have any ordering
but rebalancing of some cache fails to start - so in my understanding
overall rebalancing progress becomes blocked. Is that true?

Can you pleaes provide reproducer for your problem?

--Yakov

2018-07-09 16:42 GMT+03:00 Maxim Muzafarov :

> Hello Igniters,
>
> Each cache group has “rebalance order” property. As javadoc for
> getRebalanceOrder() says: “Note that cache with order {@code 0} does not
> participate in ordering. This means that cache with rebalance order {@code
> 0} will never wait for any other caches. All caches with order {@code 0}
> will be rebalanced right away concurrently with each other and ordered
> rebalance processes. If not set, cache order is 0, i.e. rebalancing is not
> ordered.”
>
> In fact GridCachePartitionExchangeManager always build the chain of
> rebalancing cache groups to start (even for cache order ZERO):
>
> ignite-sys-cache -> cacheR -> cacheR3 -> cacheR2 -> cacheR5 -> cacheR1.
>
> If one of these groups will fail to start further groups will never be run.
>
> * Question 1*: Should we fix javadoc description or create a bug for fixing
> such rebalance behavior?
>
> [1]
> https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/internal/processors/cache/
> GridCachePartitionExchangeManager.java#L2630
>

[GitHub] ignite pull request #4360: IGNITE-8995: Catch and proper propagate uncatched...

[ivandasch]

GitHub user ivandasch opened a pull request:

https://github.com/apache/ignite/pull/4360

IGNITE-8995: Catch and proper propagate uncatched exceptions from filter

and transformer to client.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ivandasch/ignite ignite-8995

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4360.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4360


commit a4ad28a4ee05c490ff468eaa33b687ad5446e405
Author: Ivan Daschinskiy 
Date:   2018-07-13T13:47:12Z

IGNITE-8995: Catch and proper propagate uncatched exceptions from filter
and transformer to client.




---

[jira] [Created] (IGNITE-9002) CPP Thin: Crash when used with not replicated cache

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9002:
---

 Summary: CPP Thin: Crash when used with not replicated cache
 Key: IGNITE-9002
 URL: https://issues.apache.org/jira/browse/IGNITE-9002
 Project: Ignite
  Issue Type: Bug
  Components: platforms, thin client
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.7


Crash happens because of the unhandled case when cache has zero partitions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4359: IGNITE-8060 IGNITE-8055

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/4359

IGNITE-8060 IGNITE-8055



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8060

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4359.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4359


commit 2b9a0f46b7ca37cfd00cac6eb5e0ecda74884ca0
Author: Ilya Kasnacheev 
Date:   2018-07-13T11:41:39Z

IGNITE-8060 Start missing caches before executing operations on all caches.

commit e732561681cd6e62978b07f7ab4116797ecda2a3
Author: Ilya Kasnacheev 
Date:   2018-07-13T11:42:55Z

IGNITE-8055 Start missing caches even if "IF EXISTS" not in query.




---

[GitHub] ignite pull request #4198: IGNITE-8738 log "coordinator changed" message in ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4198


---

[jira] [Created] (IGNITE-9001) Crush when using SSL on Ignite.NET 2.5.0

[Pavel Poltoratskiy (JIRA)]

Pavel Poltoratskiy created IGNITE-9001:
--

 Summary: Crush when using SSL on Ignite.NET 2.5.0
 Key: IGNITE-9001
 URL: https://issues.apache.org/jira/browse/IGNITE-9001
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Pavel Poltoratskiy


I update form 2.4.0 to 2.5.0 and found this bug.

Here you can download minimal project that reproduces the bug: 
[https://yadi.sk/d/j0GqBfDN3Z8xNX]

When executing the last line "var ignite = Ignition.Start(igniteConfig)", this 
exception occurs:

[16:06:36,744][SEVERE][main][IgniteKernal] Exception during start processors, 
node will be stopped and close connections
class org.apache.ignite.IgniteException: Java exception occurred 
[class=java.lang.NullPointerException, message=]
    at 
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongLongLongObjectOutLong(Native
 Method)
    at 
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.onStart(PlatformCallbackGateway.java:805)
    at 
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.start(PlatformProcessorImpl.java:249)
    at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1738)
    at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:999)
    at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
    at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
    at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:649)
    at 
org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
    at 
org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75)
[16:06:36,747][SEVERE][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
class org.apache.ignite.IgniteException: Java exception occurred 
[class=java.lang.NullPointerException, message=]
    at 
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongLongLongObjectOutLong(Native
 Method)
    at 
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.onStart(PlatformCallbackGateway.java:805)
    at 
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.start(PlatformProcessorImpl.java:249)
    at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1738)
    at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:999)
    at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
    at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
    at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:649)
    at 
org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
    at 
org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75)
[16:06:36] Ignite node stopped OK [uptime=00:00:10.602]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9000) [Test Failed] IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails sometimes.

[Pavel Pereslegin (JIRA)]

Pavel Pereslegin created IGNITE-9000:


 Summary: [Test Failed] 
IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails sometimes.
 Key: IGNITE-9000
 URL: https://issues.apache.org/jira/browse/IGNITE-9000
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Pavel Pereslegin


IgniteServiceReassignmentTest.testZombieAssignmentsCleanup has flaky failures.

Typical output:
{noformat}
junit.framework.AssertionFailedError
at 
org.apache.ignite.internal.processors.service.IgniteServiceReassignmentTest.testZombieAssignmentsCleanup(IgniteServiceReassignmentTest.java:237)
{noformat}

Exception that triggers an assertion error:
{noformat}
java.lang.IllegalStateException: Getting affinity for topology version earlier 
than affinity is calculated [locNode=TcpDiscoveryNode 
[id=dc037d7a-2882-478c-a944-56c66131, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
lastExchangeTime=1531485137994, loc=true, ver=2.7.0#19700101-sha1:, 
isClient=false], grp=ignite-sys-cache, topVer=AffinityTopologyVersion 
[topVer=3, minorTopVer=0], head=AffinityTopologyVersion [topVer=4, 
minorTopVer=0], history=[AffinityTopologyVersion [topVer=2, minorTopVer=0], 
AffinityTopologyVersion [topVer=2, minorTopVer=1], AffinityTopologyVersion 
[topVer=4, minorTopVer=0]]]
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:694)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:594)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:225)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:261)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:252)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:276)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1879)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2066)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4358: IGNITE-8998 Send reconnect exception without part...

[akalash]

GitHub user akalash opened a pull request:

https://github.com/apache/ignite/pull/4358

IGNITE-8998 Send reconnect exception without partitions



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8998

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4358.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4358


commit 147e8c52e1aab3e54b14c9dbd168d228a1282fb8
Author: Anton Kalashnikov 
Date:   2018-07-13T12:36:14Z

IGNITE-8998 Send reconnect exception without partitions




---

[GitHub] ignite pull request #4334: IGNITE-8957: fix assert when histMap is empty

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4334


---

[jira] [Created] (IGNITE-8999) WebConsole should correct parsing trace error messages introduced by #8971

[Andrew Medvedev (JIRA)]

Andrew Medvedev created IGNITE-8999:
---

 Summary: WebConsole should correct parsing trace error messages 
introduced by #8971
 Key: IGNITE-8999
 URL: https://issues.apache.org/jira/browse/IGNITE-8999
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Medvedev






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: MTCGA: new failures in builds [1479951] needs to be handled

[Dmitry Pavlov]

Hi Maxim,

Q1, always dev list. I've asked Igniters to add match before VCS username &
TC user, but it was not always done. So it is only one option currently to
notify developers.

Q2. there is such plans
https://github.com/dspavlov/ignite-teamcity-helper/issues/9 - It will be
done in very nearest future. I will do my absolute best to find a time slot
to finish this feature.

Sincerely,
Dmitriy Pavlov

пт, 13 июл. 2018 г. в 10:14, Maxim Muzafarov :

> Dmity,
>
> Nice idea for such notification. Can you, please, clarify few questions:
>
> * Q1 *:  For such failures (5 times ok than 3 times fail) this notification
> would be sent to whole developer list or just for authous of problem
> commits?
>
> * Q2 *:  Can we also add notification about new "execution timeouts" for
> important Ignite test suites? (e.g. Caches, Activate\Deactivate, PDS)
>
> чт, 12 июл. 2018 г. в 19:29, Dmitry Pavlov :
>
> > I've pushed fix of failure to master.
> >
> > чт, 12 июл. 2018 г. в 16:25, Dmitry Pavlov :
> >
> > > Hi Igniters,
> > >
> > > this notification was generated because this test was stable passing
> (at
> > > least 5 ok) in master and became stable failed (at least 3 failures).
> > >
> > > Such notifications would not be generated for each case of flaky
> > failures,
> > > so I hope this feature will help us to identify and fix new failures.
> > >
> > > I'll fix message format to be more readable soon.
> > >
> > > It would be pleasure to me to run short talk (webinar) about tests,
> > MTCGA,
> > > and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.
> > >
> > > I would also highly appreciate any kind of feedback.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 12 июл. 2018 г. в 16:14, :
> > >
> > >> Hi Ignite Developer,
> > >>
> > >> I am MTCGA.Bot, and I've detected some issue on TeamCity to be
> > addressed.
> > >> I hope you can help.
> > >>
> > >>  *New test failure in master
> > >>
> >
> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
> > >>
> > >>
> >
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-1615751728537497724&branch=%3Cdefault%3E&tab=testDetails
> > >>  Changes may led to failure were done by alexey.goncharuk
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825445&personal=false
> > ,
> > >> eshangareev
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825442&personal=false
> > ,
> > >> sergey.chugunov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825439&personal=false
> > ,
> > >> irakov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825436&personal=false
> > ,
> > >> irakov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825428&personal=false
> > ,
> > >> ivandasch
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825411&personal=false
> > ,
> > >> sbt-pereslegin-pa1
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825407&personal=false
> > ,
> > >> alexey.scherbakoff
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825404&personal=false
> > ,
> > >> akuznetsov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825396&personal=false
> > ,
> > >> vsisko
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825371&personal=false
> > ,
> > >> pivanov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825366&personal=false
> > ,
> > >> dmitriyff
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825351&personal=false
> > ,
> > >> dmitriyff
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825348&personal=false
> > If
> > >> your changes can led to this failure(s), please create issue with
> label
> > >> MakeTeamCityGreenAgain and assign it to you.If you have fix,
> > please
> > >> set ticket to PA state and write to dev list fix is readyFor
> > case
> > >> fix will require some time please mute test and set label Muted_Test
> to
> > >> issueIf you know which change caused failure please
> > >> contact change author directlyIf you don't know which change
> > >> caused failure please send message to dev list to find
> > >> outShould you have any questions please contact
> > >> dpav...@apache.org or write to dev.listBest
> > >> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23
> > MSK
> > >> 2018
> > >
> > >
> >
>

[GitHub] ignite pull request #1596: IGNITE-1393

[SomeFire]

Github user SomeFire closed the pull request at:

https://github.com/apache/ignite/pull/1596


---

Re: RDD spark 2.10 version upgrade & TC suites

[Dmitry Pavlov]

Hi Petr, Nikolay, thank you!

пт, 13 июл. 2018 г. в 10:33, Petr Ivanov :

> Marked build type obsolete and removed from build chain.
>
>
>
> > On 13 Jul 2018, at 10:13, Nikolay Izhikov  wrote:
> >
> > Hello, Igniters.
> >
> > 1. There is no spark_2.10 module in master and ignite-2.6.
> >
> > 2. We don't need "RDD (Spark 2.10)" build. Please, delete it from Team
> City.
> >
> > В Чт, 12/07/2018 в 23:19 +0300, Dmitry Pavlov пишет:
> >> I guess related topic is
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Review-request-for-IGNITE-8534-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-td30979.html
> >> Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark
> version to 2.3.
> >> and ticket https://issues.apache.org/jira/browse/IGNITE-8534
> >>
> >>
> >> чт, 12 июл. 2018 г. в 19:35, Denis Magda :
> >>> Nikolay,
> >>>
> >>> Please step in. I still see spark-2.10 module which means we fully
> support
> >>> this version.
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov 
> wrote:
> >>>
>  Hi Igniters,
> 
>  Do we need
> 
> 
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
>  suite is always fails with exit code 1 and I think I saw discussion
> about
>  version change.
> 
>  Could I remove this suite from RunAll?
> 
>  Sincerely,
>  Dmitriy Pavlov
>
>

Re: MTCGA: new failures in builds [1485687] needs to be handled

[Dmitry Pavlov]

I suspect this change may case this failure:
kcheng.mvp (kcheng.mvp) IGNITE-8776  Eviction policy MBeans are never
registered if
so I'm going to take a look.

пт, 13 июл. 2018 г. в 10:59, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> GridCacheLifecycleAwareSelfTest.testLifecycleAware
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7246907407546697403&branch=%3Cdefault%3E&tab=testDetails
>  Changes may led to failure were done by dpavlov
> http://ci.ignite.apache.org/viewModification.html?modId=825539&personal=false,
> eduard.shangareev
> http://ci.ignite.apache.org/viewModification.html?modId=825536&personal=false,
> kcheng.mvp
> http://ci.ignite.apache.org/viewModification.html?modId=825531&personal=false,
> dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825495&personal=false,
> alexey.scherbakoff
> http://ci.ignite.apache.org/viewModification.html?modId=825466&personal=false,
> anovikov
> http://ci.ignite.apache.org/viewModification.html?modId=825458&personal=false,
> akuznetsov
> http://ci.ignite.apache.org/viewModification.html?modId=825455&personal=falseIf
> your changes can led to this failure(s), please create issue with label
> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
> set ticket to PA state and write to dev list fix is readyFor case
> fix will require some time please mute test and set label Muted_Test to
> issueIf you know which change caused failure please
> contact change author directlyIf you don't know which change
> caused failure please send message to dev list to find
> outShould you have any questions please contact
> dpav...@apache.org or write to dev.listBest
> Regards,MTCGA.BotNotification generated at Fri Jul 13 10:58:57 MSK
> 2018

[jira] [Created] (IGNITE-8998) Client hangs after merge exchange

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-8998:
-

 Summary: Client hangs after merge exchange
 Key: IGNITE-8998
 URL: https://issues.apache.org/jira/browse/IGNITE-8998
 Project: Ignite
  Issue Type: Test
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov


Reproduce by CacheExchangeMergeTest#testConcurrentStartServersAndClients



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4357: ignite-8897

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

https://github.com/apache/ignite/pull/4357

ignite-8897



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8897

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4357.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4357


commit a590c88abf3afb06aab3f45a94f7ee3b07c56620
Author: Sergey Chugunov 
Date:   2018-06-29T09:40:13Z

IGNITE-8897 fix for ArrayIndexOutOfBoundsException

commit af0364c3242c479c8613e59db0cc07535b7c3177
Author: Sergey Chugunov 
Date:   2018-07-06T15:17:09Z

IGNITE-8905 when cluster in transition state joining node BLT is compared 
against prev BLT




---

MTCGA: new failures in builds [1485687] needs to be handled

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New test failure in master 
GridCacheLifecycleAwareSelfTest.testLifecycleAware 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7246907407546697403&branch=%3Cdefault%3E&tab=testDetails
 Changes may led to failure were done by dpavlov 
http://ci.ignite.apache.org/viewModification.html?modId=825539&personal=false, 
eduard.shangareev 
http://ci.ignite.apache.org/viewModification.html?modId=825536&personal=false, 
kcheng.mvp 
http://ci.ignite.apache.org/viewModification.html?modId=825531&personal=false, 
dmitriyff 
http://ci.ignite.apache.org/viewModification.html?modId=825495&personal=false, 
alexey.scherbakoff 
http://ci.ignite.apache.org/viewModification.html?modId=825466&personal=false, 
anovikov 
http://ci.ignite.apache.org/viewModification.html?modId=825458&personal=false, 
akuznetsov 
http://ci.ignite.apache.org/viewModification.html?modId=825455&personal=falseIf
 your changes can led to this failure(s), please create issue with label 
MakeTeamCityGreenAgain and assign it to you.If you have fix, please set 
ticket to PA state and write to dev list fix is readyFor case fix will 
require some time please mute test and set label Muted_Test to 
issueIf you know which change caused failure please contact 
change author directlyIf you don't know which change caused failure 
please send message to dev list to find outShould you have any 
questions please contact dpav...@apache.org or write to dev.listBest 
Regards,MTCGA.BotNotification generated at Fri Jul 13 10:58:57 MSK 
2018

[jira] [Created] (IGNITE-8997) Web Console: Need to destroy all the icons from all modal windows

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-8997:
-

 Summary: Web Console: Need to destroy all the icons from all modal 
windows
 Key: IGNITE-8997
 URL: https://issues.apache.org/jira/browse/IGNITE-8997
 Project: Ignite
  Issue Type: Improvement
  Components: UI, wizards
Reporter: Vica Abramova
Assignee: Alexey Kuznetsov
 Attachments: icon.png





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: RDD spark 2.10 version upgrade & TC suites

[Petr Ivanov]

Marked build type obsolete and removed from build chain.



> On 13 Jul 2018, at 10:13, Nikolay Izhikov  wrote:
> 
> Hello, Igniters.
> 
> 1. There is no spark_2.10 module in master and ignite-2.6.
> 
> 2. We don't need "RDD (Spark 2.10)" build. Please, delete it from Team City.
> 
> В Чт, 12/07/2018 в 23:19 +0300, Dmitry Pavlov пишет:
>> I guess related topic is 
>> http://apache-ignite-developers.2346864.n4.nabble.com/Review-request-for-IGNITE-8534-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-td30979.html
>> Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version 
>> to 2.3.
>> and ticket https://issues.apache.org/jira/browse/IGNITE-8534
>> 
>> 
>> чт, 12 июл. 2018 г. в 19:35, Denis Magda :
>>> Nikolay,
>>> 
>>> Please step in. I still see spark-2.10 module which means we fully support
>>> this version.
>>> 
>>> --
>>> Denis
>>> 
>>> On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov  wrote:
>>> 
 Hi Igniters,
 
 Do we need
 
 https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
 suite is always fails with exit code 1 and I think I saw discussion about
 version change.
 
 Could I remove this suite from RunAll?
 
 Sincerely,
 Dmitriy Pavlov

[GitHub] ignite pull request #4356: IGNITE-8761 WAL fsync at rollover should be async...

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

https://github.com/apache/ignite/pull/4356

IGNITE-8761 WAL fsync at rollover should be asynchronous in LOG_ONLY …

…and BACKGROUND modes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8761-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4356.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4356


commit 2cd5d6c91a008291731a6210f4f4afa9813e943e
Author: vd-pyatkov 
Date:   2018-07-10T14:54:30Z

IGNITE-8761 WAL fsync at rollover should be asynchronous in LOG_ONLY and 
BACKGROUND modes




---

Re: RDD spark 2.10 version upgrade & TC suites

[Nikolay Izhikov]

Hello, Igniters.

1. There is no spark_2.10 module in master and ignite-2.6.

2. We don't need "RDD (Spark 2.10)" build. Please, delete it from Team City.

В Чт, 12/07/2018 в 23:19 +0300, Dmitry Pavlov пишет:
> I guess related topic is 
> http://apache-ignite-developers.2346864.n4.nabble.com/Review-request-for-IGNITE-8534-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-td30979.html
>  Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version 
> to 2.3.
> and ticket https://issues.apache.org/jira/browse/IGNITE-8534
> 
> 
> чт, 12 июл. 2018 г. в 19:35, Denis Magda :
> > Nikolay,
> > 
> > Please step in. I still see spark-2.10 module which means we fully support
> > this version.
> > 
> > --
> > Denis
> > 
> > On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov  wrote:
> > 
> > > Hi Igniters,
> > >
> > > Do we need
> > >
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
> > > suite is always fails with exit code 1 and I think I saw discussion about
> > > version change.
> > >
> > > Could I remove this suite from RunAll?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >

signature.asc
Description: This is a digitally signed message part

Re: MTCGA: new failures in builds [1479951] needs to be handled

[Maxim Muzafarov]

Dmity,

Nice idea for such notification. Can you, please, clarify few questions:

* Q1 *:  For such failures (5 times ok than 3 times fail) this notification
would be sent to whole developer list or just for authous of problem
commits?

* Q2 *:  Can we also add notification about new "execution timeouts" for
important Ignite test suites? (e.g. Caches, Activate\Deactivate, PDS)

чт, 12 июл. 2018 г. в 19:29, Dmitry Pavlov :

> I've pushed fix of failure to master.
>
> чт, 12 июл. 2018 г. в 16:25, Dmitry Pavlov :
>
> > Hi Igniters,
> >
> > this notification was generated because this test was stable passing (at
> > least 5 ok) in master and became stable failed (at least 3 failures).
> >
> > Such notifications would not be generated for each case of flaky
> failures,
> > so I hope this feature will help us to identify and fix new failures.
> >
> > I'll fix message format to be more readable soon.
> >
> > It would be pleasure to me to run short talk (webinar) about tests,
> MTCGA,
> > and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.
> >
> > I would also highly appreciate any kind of feedback.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 12 июл. 2018 г. в 16:14, :
> >
> >> Hi Ignite Developer,
> >>
> >> I am MTCGA.Bot, and I've detected some issue on TeamCity to be
> addressed.
> >> I hope you can help.
> >>
> >>  *New test failure in master
> >>
> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
> >>
> >>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-1615751728537497724&branch=%3Cdefault%3E&tab=testDetails
> >>  Changes may led to failure were done by alexey.goncharuk
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825445&personal=false
> ,
> >> eshangareev
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825442&personal=false
> ,
> >> sergey.chugunov
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825439&personal=false
> ,
> >> irakov
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825436&personal=false
> ,
> >> irakov
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825428&personal=false
> ,
> >> ivandasch
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825411&personal=false
> ,
> >> sbt-pereslegin-pa1
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825407&personal=false
> ,
> >> alexey.scherbakoff
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825404&personal=false
> ,
> >> akuznetsov
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825396&personal=false
> ,
> >> vsisko
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825371&personal=false
> ,
> >> pivanov
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825366&personal=false
> ,
> >> dmitriyff
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825351&personal=false
> ,
> >> dmitriyff
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=825348&personal=false
> If
> >> your changes can led to this failure(s), please create issue with label
> >> MakeTeamCityGreenAgain and assign it to you.If you have fix,
> please
> >> set ticket to PA state and write to dev list fix is readyFor
> case
> >> fix will require some time please mute test and set label Muted_Test to
> >> issueIf you know which change caused failure please
> >> contact change author directlyIf you don't know which change
> >> caused failure please send message to dev list to find
> >> outShould you have any questions please contact
> >> dpav...@apache.org or write to dev.listBest
> >> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23
> MSK
> >> 2018
> >
> >
>

[GitHub] ignite pull request #4355: Ignite 2.5.1 p10

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

https://github.com/apache/ignite/pull/4355

Ignite 2.5.1 p10



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p10

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4355.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4355


commit 1cea80d29f4f1c61ed56ad1261b74ed42611bf64
Author: Ilya Lantukh 
Date:   2018-04-06T10:49:10Z

IGNITE-8018 Optimized GridCacheMapEntry initialValue() - Fixes #3686.

Signed-off-by: Alexey Goncharuk 

commit 37fc72542eb6baa8be8b41aecd08a194102d13c1
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 

(cherry picked from commit e491f10)

commit 76e293654e34c927d6c9efc85a12e736b58a21f2
Author: Eduard Shangareev 
Date:   2018-04-06T16:22:07Z

IGNITE-8114 Add fail recovery mechanism to tracking pages - Fixes #3734.

Signed-off-by: dpavlov 

(cherry picked from commit 0829397)

commit 49f11db727febc83297c7f0f5de9e6f98f0197fa
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit 9ad7be2f51b6dcdcdf43fedb298cd4e240f0adab
Author: Ilya Borisov 
Date:   2018-04-09T13:59:32Z

IGNITE-8155 Web Console: Fixed number pattern warning in browser console.

(cherry picked from commit 5d8f570)

commit 4aa56751906e5db7aad025a7193933fa929aae26
Author: Vasiliy Sisko 
Date:   2018-04-09T15:13:21Z

IGNITE-7940 Visor CMD: Added "cache -slp" and "cache -rlp" commands to show 
and reset lost partitions for specified cache.

(cherry picked from commit abfa0f5)

commit cc04c5c70af1bdbba834f73330e73277b60e23fc
Author: Eduard Shangareev 
Date:   2018-04-09T16:15:50Z

IGNITE-8114 Additional fix for Add fail recovery mechanism to tracking pages

(cherry picked from commit 961fc35)

commit c70d85aa36c702ea0f29bd8668e9bf0790f9ba11
Author: Vasiliy Sisko 
Date:   2018-04-10T08:42:24Z

IGNITE-8126 Web Console: Fixed code generation for cache load.

(cherry picked from commit a0a187b)

commit 8d3755b9c58eef12c5fc9cabfc0b1c05f6db716e
Author: Semyon Boikov 
Date:   2018-04-10T08:37:39Z

IGNITE-7222 Added ZooKeeper discovery SPI

commit b096a463c338565a7661f8a853a257518d872997
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

commit 82a4c024fe06ef8c8deeaf762f0cc20a8e481252
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

commit c1745de37891026e0a719f0c1d1afe768dfccbf3
Author: Vasiliy Sisko 
Date:   2018-04-10T10:48:52Z

IGNITE-7927 Web Console: Fixed demo for non-collocated joins.

(cherry picked from commit 647620b)

commit b28287d1861fd841a18d0eef95eff309d21a55ef
Author: Alexey Goncharuk 
Date:   2018-04-10T13:22:28Z

IGNITE-8025 Future must fail if assertion error has been thrown in the 
worker thread

commit a832f2b2e5788c45114c3cb5529d7cf53d08f9a6
Author: Andrey Kuznetsov 
Date:   2018-04-10T14:30:12Z

ignite-7772 System workers critical failures handling

Signed-off-by: Andrey Gura 

commit 912433ba9aa113508d05930691b251eccd8f5870
Author: Aleksey Plekhanov 
Date:   2018-04-10T15:54:03Z

IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly to 
provided failure handler

Signed-off-by: Andrey Gura 

commit 99feab6ace66d011b677fd4d57b44fc54da8fd4f
Author: Alexey Goncharuk 
Date:   2018-04-10T17:33:47Z

IGNITE-6430 Complete failing test early

commit 526fb0ee612ef71fde58a1274db35e8205304a63
Author: Dmitriy Sorokin 
Date:   2018-04-10T19:20:41Z

IGNITE-8101 Ability to terminate system workers by JMX for test purposes.

Signed-off-by: Andrey Gura 

commit b4cb2f0df944534743a9d73811e047eda572258c
Author: mcherkasov 
Date:   2018-04-11T00:27:20Z

IGNITE-8153 Nodes fail to connect each other when SSL is enabled - Fixes 
#3773.

Signed-off-by: Valentin Kulichenko 

commit b4cc9f2d45d78c360abe224165e707c23533469e
Author: Pavel Kovalenko 
Date:   2018-04-11T08:23:46Z

IGNITE-7871 Implemented additional synchronization phase for correct 
partition counters update

commit 9abfee69aa153888456f9e8574ece1f2d0cbe4d9
Author: dmitrievanthony 
Date:   2018-04-10T09:46:43Z

IGNITE-8059: Integrate decis