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

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 a

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

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 tim

Re: RDD spark 2.10 version upgrade & TC suites

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

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

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.

Re: RDD spark 2.10 version upgrade & TC suites

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/20

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

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

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

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=724690740754

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

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 a

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

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

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

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 hop

Re: RDD spark 2.10 version upgrade & TC suites

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

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

Github user SomeFire closed the pull request at: https://github.com/apache/ignite/pull/1596 ---

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

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

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

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 Proj

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4334 ---

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

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 Alt

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

Pavel Pereslegin created IGNITE-9000: Summary: [Test Failed] IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails sometimes. Key: IGNITE-9000 URL: https://issues.apache.org/jira/browse/IGNITE-9000

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

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 T

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4198 ---

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

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 app

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

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

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

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://githu

Re: Async cache groups rebalance not started with rebalanceOrder ZERO

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 Maxi

Re: MVCC and IgniteDataStreamer

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 г

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

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

Neighbors exclusion

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 excludeNeighbo

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

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/

TeamCity: Mass run-all during weekend

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

Application of various Complex object types

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 to

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

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 I

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

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 c

Re: Application of various Complex object types

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

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

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 P

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

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 i

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4331 ---

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4296 ---

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

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

Re: Neighbors exclusion

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 th

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

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=IgniteT

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

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 > Ig

Re: Application of various Complex object types

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

Re: MVCC and IgniteDataStreamer

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 s

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

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=65234792228

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

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 TeamCi

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

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 Alter