[jira] [Created] (IGNITE-11711) Web console: MS SQL server missing JDBC download link
Ilya Borisov created IGNITE-11711: - Summary: Web console: MS SQL server missing JDBC download link Key: IGNITE-11711 URL: https://issues.apache.org/jira/browse/IGNITE-11711 Project: Ignite Issue Type: Bug Components: wizards Reporter: Ilya Borisov Assignee: Vasiliy Sisko Attachments: image-2019-04-10-12-54-22-561.png What happens: In configuration / advanced / caches / store if user selects "JDBC Pojo store factory" and "MS SQL Server" dialect, a link labeled "Download JDBC drivers?" is displayed. When "oracle" or "IBM" dialects are selected, the link leads to a proper download page, while "MS" dialect link leads nowhere. !image-2019-04-10-12-54-22-561.png! Expected behavior: If there is a download page for MS JDBC driver, add it's URL to JDBC_LINKS provider. If there's none, maybe don't show the link or show appropriate plain text? The issue was reproduced in master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11710) Web Console: Expose callback to ui-grid.api for manipulations with ui-grid.
Alexey Kuznetsov created IGNITE-11710: - Summary: Web Console: Expose callback to ui-grid.api for manipulations with ui-grid. Key: IGNITE-11710 URL: https://issues.apache.org/jira/browse/IGNITE-11710 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov In some situations we need access to ui-grid.api lets introduce this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Request for contributors permissions
Done, you're in. Feel free to take over open tickets/issues. - Denis On Tue, Apr 9, 2019 at 1:33 PM wrote: > Sure. > > Username: olemogyl > Email is same: olek...@reseguiden.se > > - > Oleksii > > -Original Message- > From: Denis Magda > Sent: Tuesday, April 9, 2019 8:22 PM > To: dev > Subject: Re: Request for contributors permissions > > Hello Oleksii, > > Sure, please tell your JIRA ID. > > - > Denis > > > On Tue, Apr 9, 2019 at 10:18 AM Oleksii Mohylin > wrote: > > > Hello > > > > > > > > I would like to become a contributor of Apache Ignite project. I'm > > working on an OSGI application project with cache implementation by > > Apache Ignite and have already discovered some issues. Could you > > please assign my account to proper user group in Jira? > > > > > > > > Thanks! > > > > Oleksii > > > > > >
RE: Request for contributors permissions
Sure. Username: olemogyl Email is same: olek...@reseguiden.se - Oleksii -Original Message- From: Denis Magda Sent: Tuesday, April 9, 2019 8:22 PM To: dev Subject: Re: Request for contributors permissions Hello Oleksii, Sure, please tell your JIRA ID. - Denis On Tue, Apr 9, 2019 at 10:18 AM Oleksii Mohylin wrote: > Hello > > > > I would like to become a contributor of Apache Ignite project. I'm > working on an OSGI application project with cache implementation by > Apache Ignite and have already discovered some issues. Could you > please assign my account to proper user group in Jira? > > > > Thanks! > > Oleksii > >
Re: Request for contributors permissions
Hello Oleksii, Sure, please tell your JIRA ID. - Denis On Tue, Apr 9, 2019 at 10:18 AM Oleksii Mohylin wrote: > Hello > > > > I would like to become a contributor of Apache Ignite project. I'm working > on an OSGI application project with cache implementation by Apache Ignite > and have already discovered some issues. Could you please assign my account > to proper user group in Jira? > > > > Thanks! > > Oleksii > >
Request for contributors permissions
Hello I would like to become a contributor of Apache Ignite project. I'm working on an OSGI application project with cache implementation by Apache Ignite and have already discovered some issues. Could you please assign my account to proper user group in Jira? Thanks! Oleksii
Re: Cluster discovery via Consul
I would support this idea of having integrations in separate Github repositories. Ignite is already overwhelmed with a bunch of integrations which complicates testing, release procedures, maintenance. Think that we, as the community, should revisit the current project structure and move even key integrations like Spark or SpringData to separate repositories. That's another discussion. - Denis On Tue, Apr 9, 2019 at 2:40 AM Ilya Kasnacheev wrote: > Hello! > > I'm not sure that we should bundle Consul intergration with Ignite. We have > a huge number of integrations and most of those are poorly maintained. I > think that you should develop it separately, deploy releases to maven > centra;/ They will be as easily reachable as our own artifacts this way. > > Otherwise, the answers is 1) why not, and 2) we're not sure, give it a try. > > Regards, > -- > Ilya Kasnacheev > > > вт, 9 апр. 2019 г. в 05:38, Saikat Maitra : > > > Hi Ilya, > > > > I wanted to raise an PR to include TCPConsulIPFinder as part of Ignite > > modules and wanted to discuss if consul orbitz client can be used or > shall > > we implement it differently. > > > > > > Regards, > > Saikat > > > > On Mon, Apr 8, 2019 at 6:07 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > > wrote: > > > > > Hello! > > > > > > Looks like there's a ready solution for your problem. What do you have > > left > > > unsolved? > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > пн, 8 апр. 2019 г. в 02:42, Saikat Maitra : > > > > > > > Hi, > > > > > > > > I am looking into this issue > > > > https://issues.apache.org/jira/browse/IGNITE-1204 and found > something > > > > similar ignite consul cluster discovery client here > > > > > > > > [https://github.com/andrea-zanetti/ignite-consul] > > > > > > > > This library depends on consul orbitz client [ > > > > https://github.com/rickfast/consul-client] > > > > > > > > I wanted to connect to understand if it is something we can use to > > build > > > > the consul discovery module? > > > > > > > > Regards, > > > > Saikat > > > > > > > > > >
[jira] [Created] (IGNITE-11709) .NET thin client: introduce ClusterGroup methods
Alexandr Shapkin created IGNITE-11709: - Summary: .NET thin client: introduce ClusterGroup methods Key: IGNITE-11709 URL: https://issues.apache.org/jira/browse/IGNITE-11709 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Alexandr Shapkin Assignee: Alexandr Shapkin Fix For: 2.8 Let's start implementing IClusterGroup methods for thin client. Desired functionality, according to the regular client * ForAttribute * ForCacheNodes * ForDotNet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Broken master
Hello, Igniters. Current master is broken with this commit: https://github.com/apache/ignite/commit/c23f6b0c11df9c0a9cd55e87e0f9b4c6771ce43f Andrew, please, fix it. ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project ignite-core: Compilation failure: Compilation failure: [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/mvcc/MvccUtils.java:[38,38] cannot find symbol [ERROR] symbol: class TransactionMixedModeException [ERROR] location: package org.apache.ignite.transactions [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/mvcc/MvccUtils.java:[40,38] cannot find symbol [ERROR] symbol: class TransactionUnsupportedConcurrencyException [ERROR] location: package org.apache.ignite.transactions [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java:[66,38] cannot find symbol [ERROR] symbol: class TransactionMixedModeException [ERROR] location: package org.apache.ignite.transactions [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java:[70,38] cannot find symbol [ERROR] symbol: class TransactionUnsupportedConcurrencyException [ERROR] location: package org.apache.ignite.transactions [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/odbc/OdbcRequestHandler.java:[42,38] cannot find symbol [ERROR] symbol: class TransactionMixedModeException [ERROR] location: package org.apache.ignite.transactions [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/odbc/OdbcRequestHandler.java:[43,38] cannot find symbol [ERROR] symbol: class TransactionUnsupportedConcurrencyException [ERROR] location: package org.apache.ignite.transactions [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/mvcc/MvccUtils.java:[718,27] cannot find symbol [ERROR] symbol: class TransactionUnsupportedConcurrencyException [ERROR] location: class org.apache.ignite.internal.processors.cache.mvcc.MvccUtils [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/mvcc/MvccUtils.java:[724,27] cannot find symbol [ERROR] symbol: class TransactionMixedModeException [ERROR] location: class org.apache.ignite.internal.processors.cache.mvcc.MvccUtils [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java:[1151,26] cannot find symbol [ERROR] symbol: class TransactionMixedModeException [ERROR] location: class org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java:[1153,26] cannot find symbol [ERROR] symbol: class TransactionUnsupportedConcurrencyException [ERROR] location: class org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/odbc/OdbcRequestHandler.java:[986,26] cannot find symbol [ERROR] symbol: class TransactionMixedModeException [ERROR] location: class org.apache.ignite.internal.processors.odbc.odbc.OdbcRequestHandler [ERROR] /home/dragon/src/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/odbc/OdbcRequestHandler.java:[988,26] cannot find symbol [ERROR] symbol: class TransactionUnsupportedConcurrencyException [ERROR] location: class org.apache.ignite.internal.processors.odbc.odbc.OdbcRequestHandler [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :ignite-core ``` signature.asc Description: This is a digitally signed message part
[jira] [Created] (IGNITE-11708) Unable to run tests under IgniteConfigVariationsAbstractTest class
Ivan Fedotov created IGNITE-11708: - Summary: Unable to run tests under IgniteConfigVariationsAbstractTest class Key: IGNITE-11708 URL: https://issues.apache.org/jira/browse/IGNITE-11708 Project: Ignite Issue Type: Bug Reporter: Ivan Fedotov Assignee: Ivan Fedotov It seems that test classes that extend from IgniteConfigVariationsAbstractTest cannot be started with JUnit4 @Test annotation. It is easy to check: if throw exception in any test methods, nothing will happen. Reason can be in rule chain in IgniteConfigVariationsAbstractTest class [1], maybe it destroys existing test workflow. [1] https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/IgniteConfigVariationsAbstractTest.java#L62 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11707) Tcp Discovery should drop pending metrics update message when new message is received
Alexey Goncharuk created IGNITE-11707: - Summary: Tcp Discovery should drop pending metrics update message when new message is received Key: IGNITE-11707 URL: https://issues.apache.org/jira/browse/IGNITE-11707 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11706) DistributedMetaStoragePersistentTest.testConflictingData is flaky in zookeeper suite.
Ivan Bessonov created IGNITE-11706: -- Summary: DistributedMetaStoragePersistentTest.testConflictingData is flaky in zookeeper suite. Key: IGNITE-11706 URL: https://issues.apache.org/jira/browse/IGNITE-11706 Project: Ignite Issue Type: Test Reporter: Ivan Bessonov Assignee: Ivan Bessonov [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4285807788261365029=testDetails_IgniteTests24Java8=%3Cdefault%3E] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11705) Jdbc Thin: add ability to control affinity cache size.
Alexander Lapin created IGNITE-11705: Summary: Jdbc Thin: add ability to control affinity cache size. Key: IGNITE-11705 URL: https://issues.apache.org/jira/browse/IGNITE-11705 Project: Ignite Issue Type: Task Components: jdbc Reporter: Alexander Lapin Within AffinityCache there are two properties DISTRIBUTIONS_CACHE_LIMIT and SQL_CACHE_LIMIT that are hard coded. We should add an ability to control given parameters within some sort of configuration. IgniteSystemProperties is not an option however. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer
Alexey Goncharuk created IGNITE-11704: - Summary: Write tombstones during rebalance to get rid of deferred delete buffer Key: IGNITE-11704 URL: https://issues.apache.org/jira/browse/IGNITE-11704 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk Currently Ignite relies on deferred delete buffer in order to handle write-remove conflicts during rebalance. Given the limit size of the buffer, this approach is fundamentally flawed, especially in case when persistence is enabled. I suggest to extend the logic of data storage to be able to store key tombstones - to keep version for deleted entries. The tombstones will be stored when rebalance is in progress and should be cleaned up when rebalance is completed. Later this approach may be used to implement fast partition rebalance based on merkle trees (in this case, tombstones should be written on an incomplete baseline). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11703) CPP: Add default BinaryType methods implementations where possible
Igor Sapego created IGNITE-11703:
Summary: CPP: Add default BinaryType methods implementations where
possible
Key: IGNITE-11703
URL: https://issues.apache.org/jira/browse/IGNITE-11703
Project: Ignite
Issue Type: Improvement
Components: platforms
Affects Versions: 2.7
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 2.8
Currently, most of specifications of {{BinaryType}} template have the same
default implementations of certain methods, which may be implemented by
default. Here is the list:
{{GetTypeId}}
{{GetFieldId}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11702) GridCacheNearOnlyTopologySelfTest.testNodeLeave is flaky.
Ivan Bessonov created IGNITE-11702: -- Summary: GridCacheNearOnlyTopologySelfTest.testNodeLeave is flaky. Key: IGNITE-11702 URL: https://issues.apache.org/jira/browse/IGNITE-11702 Project: Ignite Issue Type: Test Reporter: Ivan Bessonov Assignee: Ivan Bessonov [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5748284805523586815=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Cluster discovery via Consul
Hello! I'm not sure that we should bundle Consul intergration with Ignite. We have a huge number of integrations and most of those are poorly maintained. I think that you should develop it separately, deploy releases to maven centra;/ They will be as easily reachable as our own artifacts this way. Otherwise, the answers is 1) why not, and 2) we're not sure, give it a try. Regards, -- Ilya Kasnacheev вт, 9 апр. 2019 г. в 05:38, Saikat Maitra : > Hi Ilya, > > I wanted to raise an PR to include TCPConsulIPFinder as part of Ignite > modules and wanted to discuss if consul orbitz client can be used or shall > we implement it differently. > > > Regards, > Saikat > > On Mon, Apr 8, 2019 at 6:07 AM Ilya Kasnacheev > wrote: > > > Hello! > > > > Looks like there's a ready solution for your problem. What do you have > left > > unsolved? > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 8 апр. 2019 г. в 02:42, Saikat Maitra : > > > > > Hi, > > > > > > I am looking into this issue > > > https://issues.apache.org/jira/browse/IGNITE-1204 and found something > > > similar ignite consul cluster discovery client here > > > > > > [https://github.com/andrea-zanetti/ignite-consul] > > > > > > This library depends on consul orbitz client [ > > > https://github.com/rickfast/consul-client] > > > > > > I wanted to connect to understand if it is something we can use to > build > > > the consul discovery module? > > > > > > Regards, > > > Saikat > > > > > >
[jira] [Created] (IGNITE-11701) SQL: Reflect in documentation change of system views schema from "IGNITE" to "SYS"
Vladimir Ozerov created IGNITE-11701: Summary: SQL: Reflect in documentation change of system views schema from "IGNITE" to "SYS" Key: IGNITE-11701 URL: https://issues.apache.org/jira/browse/IGNITE-11701 Project: Ignite Issue Type: Task Components: documentation Reporter: Vladimir Ozerov Assignee: Artem Budnikov Fix For: 2.8 Previously all system views were located in "IGNITE" schema. Now we moved them to "SYS" because this is more intuitive and consistent with other database vendors. Need to do two things: # Updated documentation of system views: change "IGNITE" schema to "SYS" # Add a balloon informing users that before AI 2.8 system views were located in "IGNITE" schema and that previous behavior could be forced with "-DIGNITE_SQL_SYSTEM_SCHEMA_NAME_IGNITE=true" system property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Make the TeamCity console quiet.
Maksim, I like such approach. If nobody objects let's go ahead and try it out. вт, 9 апр. 2019 г. в 10:38, Maksim Stepachev : > > Ivan, > > 1. It'll some selector which changes ENV parameter for build run with quiet > by default. > 2. Yes, the additional log config will be added for TC. > > > пн, 8 апр. 2019 г. в 17:08, Павлухин Иван : > > > Hi Maxim, > > > > Thank you for continuing with that initiative. Could you please > > elaborate on following: > > 1. What changes are required on TC? > > 2. Will everything work without changes on a developer's local machine? > > > > пн, 8 апр. 2019 г. в 13:13, Maksim Stepachev : > > > > > > Hi, everyone! > > > > > > I want to push the topic up and discuss a final solution about the quiet > > > console. > > > > > > The suggestion above: > > > 1. Rollover will be locked. > > > Pros: Only one big file in an archive. > > > Cons: Max size of the file isn't limited. > > > 2. Run all will contain a parameter for switch off the quiet mode. > > > 3. New config: log4j-tc-test.xml for TeamCity environment. > > > > > > чт, 14 февр. 2019 г. в 15:51, Павлухин Иван : > > > > > > > Maksim, > > > > > > > > I tried configuration with quite console and unlimited log file on my > > > > machine. Naively configured in log4j-test.xml it works not so fine in > > > > development environment because log file is appended by each test > > > > execution. Console redirection works better in development > > > > environment. Should we have separate log config for TC? > > > > > > > > By the way log redirection does not work well for every test in > > > > development environment. Sometimes it seems that it could be easier to > > > > work with file. Sometimes IDEA shrinks console logs. Igniters, do you > > > > have ideas how to work with logs produced by tests more convenient? > > > > > > > > пн, 11 февр. 2019 г. в 17:29, Eduard Shangareev < > > > > eduard.shangar...@gmail.com>: > > > > > > > > > > Maksim, > > > > > > > > > > sounds good. > > > > > > > > > > 1) Can we just turn off log rollover? > > > > > 2) I believe, that we need the ability to override this by setting > > > > > parameter for Run All. > > > > > > > > > > > > > > > > > > > > On Mon, Feb 11, 2019 at 4:12 PM Maksim Stepachev < > > > > maksim.stepac...@gmail.com> > > > > > wrote: > > > > > > > > > > > Ivan, > > > > > > > > > > > > Yes. It happens because we use the RollingFileAppender for a file > > > > logging. > > > > > > This appender has the next properties: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Can I increase MaxFileSize by 200MB or more? I suppose these limits > > > > were > > > > > > added for cases when the test writes a log. It makes the guarantee > > that > > > > > > logs less than 10*10 = 100MBs. But it's wrong if it writes into the > > > > console > > > > > > too. > > > > > > > > > > > > пн, 11 февр. 2019 г. в 13:14, Павлухин Иван : > > > > > > > > > > > > > Maksim, > > > > > > > > > > > > > > Generally I like the idea. But there is one thing which bothers > > me a > > > > > > > little bit. Usually I use "Download full build log" link to > > download > > > > > > > log and then examine it as a single file. AFAIK artifact with > > logs > > > > > > > contains several files. Could you suggest a way how can I > > > > conveniently > > > > > > > explore files archive as a single file? > > > > > > > > > > > > > > пн, 11 февр. 2019 г. в 13:04, Ilya Kasnacheev < > > > > ilya.kasnach...@gmail.com > > > > > > >: > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > Can we do IGNITE_QUIET=true for runAlls triggered by bot (along > > > > with > > > > > > > > SCALE_FACTOR) and false for manually triggered builds (or > > > > retriggered > > > > > > > > failures)? > > > > > > > > > > > > > > > > Regards, > > > > > > > > -- > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > пн, 11 февр. 2019 г. в 13:03, Dmitriy Pavlov < > > dpav...@apache.org>: > > > > > > > > > > > > > > > > > ++1 from my side. It is very interesting how overall RunAll > > run > > > > time > > > > > > > will > > > > > > > > > be decreased. > > > > > > > > > > > > > > > > > > My previous experience with TeamCity shows that removing > > pressure > > > > > > from > > > > > > > the > > > > > > > > > console and using adequate logging instead may bring x1.5 - > > x2 > > > > > > > performance > > > > > > > > > boost for tests. > > > > > > > > > > > > > > > > > > One more benefit of moving from synced streams to async > > logging > > > > will > > > > > > > show > > > > > > > > > us that bugs, which we can't see right now. > > > > > > > > > > > > > > > > > > So I absolutely agree to move logging data to a logger. > > > > > > > > > > > > > > > > > > пн, 11 февр. 2019 г. в 11:14, Maksim Stepachev < > > > > > > > maksim.stepac...@gmail.com > > > > > > > > > >: > > > > > > > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > When I was working with flaky tests, I was
[jira] [Created] (IGNITE-11700) Document disabled WAL during rebalance
Alexey Goncharuk created IGNITE-11700: - Summary: Document disabled WAL during rebalance Key: IGNITE-11700 URL: https://issues.apache.org/jira/browse/IGNITE-11700 Project: Ignite Issue Type: Task Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Make the TeamCity console quiet.
Ivan, 1. It'll some selector which changes ENV parameter for build run with quiet by default. 2. Yes, the additional log config will be added for TC. пн, 8 апр. 2019 г. в 17:08, Павлухин Иван : > Hi Maxim, > > Thank you for continuing with that initiative. Could you please > elaborate on following: > 1. What changes are required on TC? > 2. Will everything work without changes on a developer's local machine? > > пн, 8 апр. 2019 г. в 13:13, Maksim Stepachev : > > > > Hi, everyone! > > > > I want to push the topic up and discuss a final solution about the quiet > > console. > > > > The suggestion above: > > 1. Rollover will be locked. > > Pros: Only one big file in an archive. > > Cons: Max size of the file isn't limited. > > 2. Run all will contain a parameter for switch off the quiet mode. > > 3. New config: log4j-tc-test.xml for TeamCity environment. > > > > чт, 14 февр. 2019 г. в 15:51, Павлухин Иван : > > > > > Maksim, > > > > > > I tried configuration with quite console and unlimited log file on my > > > machine. Naively configured in log4j-test.xml it works not so fine in > > > development environment because log file is appended by each test > > > execution. Console redirection works better in development > > > environment. Should we have separate log config for TC? > > > > > > By the way log redirection does not work well for every test in > > > development environment. Sometimes it seems that it could be easier to > > > work with file. Sometimes IDEA shrinks console logs. Igniters, do you > > > have ideas how to work with logs produced by tests more convenient? > > > > > > пн, 11 февр. 2019 г. в 17:29, Eduard Shangareev < > > > eduard.shangar...@gmail.com>: > > > > > > > > Maksim, > > > > > > > > sounds good. > > > > > > > > 1) Can we just turn off log rollover? > > > > 2) I believe, that we need the ability to override this by setting > > > > parameter for Run All. > > > > > > > > > > > > > > > > On Mon, Feb 11, 2019 at 4:12 PM Maksim Stepachev < > > > maksim.stepac...@gmail.com> > > > > wrote: > > > > > > > > > Ivan, > > > > > > > > > > Yes. It happens because we use the RollingFileAppender for a file > > > logging. > > > > > This appender has the next properties: > > > > > > > > > > > > > > > > > > > > > > > > > Can I increase MaxFileSize by 200MB or more? I suppose these limits > > > were > > > > > added for cases when the test writes a log. It makes the guarantee > that > > > > > logs less than 10*10 = 100MBs. But it's wrong if it writes into the > > > console > > > > > too. > > > > > > > > > > пн, 11 февр. 2019 г. в 13:14, Павлухин Иван : > > > > > > > > > > > Maksim, > > > > > > > > > > > > Generally I like the idea. But there is one thing which bothers > me a > > > > > > little bit. Usually I use "Download full build log" link to > download > > > > > > log and then examine it as a single file. AFAIK artifact with > logs > > > > > > contains several files. Could you suggest a way how can I > > > conveniently > > > > > > explore files archive as a single file? > > > > > > > > > > > > пн, 11 февр. 2019 г. в 13:04, Ilya Kasnacheev < > > > ilya.kasnach...@gmail.com > > > > > >: > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > Can we do IGNITE_QUIET=true for runAlls triggered by bot (along > > > with > > > > > > > SCALE_FACTOR) and false for manually triggered builds (or > > > retriggered > > > > > > > failures)? > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > пн, 11 февр. 2019 г. в 13:03, Dmitriy Pavlov < > dpav...@apache.org>: > > > > > > > > > > > > > > > ++1 from my side. It is very interesting how overall RunAll > run > > > time > > > > > > will > > > > > > > > be decreased. > > > > > > > > > > > > > > > > My previous experience with TeamCity shows that removing > pressure > > > > > from > > > > > > the > > > > > > > > console and using adequate logging instead may bring x1.5 - > x2 > > > > > > performance > > > > > > > > boost for tests. > > > > > > > > > > > > > > > > One more benefit of moving from synced streams to async > logging > > > will > > > > > > show > > > > > > > > us that bugs, which we can't see right now. > > > > > > > > > > > > > > > > So I absolutely agree to move logging data to a logger. > > > > > > > > > > > > > > > > пн, 11 февр. 2019 г. в 11:14, Maksim Stepachev < > > > > > > maksim.stepac...@gmail.com > > > > > > > > >: > > > > > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > > > > > > When I was working with flaky tests, I was surprised that > one > > > of > > > > > the > > > > > > > > > reasons for failure was a log appender blocking the > console. > > > > > > > > > > > > > > > > > > > > > > > > > > > I suppose it happened because of a TeamCity agent > communicating > > > > > with > > > > > > java > > > > > > > > > out through Linux pipe. This is a problem for tests with > 1GB > > > log > > > > > > history. > > > > > > > > > > > > > > > >
Re: Ignite 2.7.5 Release scope
Hello, Dmitriy. Any news about release? Do you need assistance with it? вт, 2 апр. 2019 г. в 20:04, Dmitriy Pavlov : > Ivan P., it seems the netty approach you've proposed works well. Thank you. > > Igniters, please take a look at following fix: > https://github.com/apache/ignite/pull/6384 > It allows us to start under Java 12 and under Java 11- (as it). > > Sincerely, > Dmitriy Pavlov > > пт, 29 мар. 2019 г. в 22:57, Dmitriy Pavlov : > > > Denis, the issue here is that we don't know for sure. We see just one > > blocking issue with accessing NioAccessObject. > > > > And there are 3 different scenario related to this issue fix: > > - fixes won't help, and we should find out other options on how to create > > a direct buffer from pointer - needed for durable memory, Java 12 goes > to a > > later release. > > - some fix would help, but other issues come, Java 12 goes to some later > > release > > - some from proposed fixes works, nothing else needs to be done - 1-2 > days > > > > If it latest scenario, I would include as much as we can (1-2 days extra > > are comparable with minimal voting time). > > > > BTW, I've checked scripts it does not work for me, I will ask Andrey > > G/Peter for advice on Monday. > > > > Sincerely, > > Dmitriy Pavlov > > > > > > пт, 29 мар. 2019 г. в 20:47, Denis Magda : > > > >> Folks, > >> > >> What are the efforts to support Java 12? Let's do 2.7.6 shortly if the > >> fixes are time-consuming. > >> > >> - > >> Denis > >> > >> > >> On Fri, Mar 29, 2019 at 10:08 AM Dmitriy Pavlov > >> wrote: > >> > >> > Hi Igniters, > >> > > >> > I would like to announce code freeze for 2.7.5. Only one open ticket > is > >> > there (reopened): https://issues.apache.org/jira/browse/IGNITE-11600 > >> (if > >> > we > >> > can't start using Java 12 we should clearly state it in scripts/code). > >> > > >> > We're entering to Stabilization phase for > >> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.5 > >> and > >> > only blockers may be included into scope. See > >> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > for > >> > more > >> > details. > >> > > >> > Sincerely, > >> > Dmitriy Pavlov > >> > > >> > пт, 29 мар. 2019 г. в 13:51, Dmitriy Pavlov : > >> > > >> > > Hi Denis, > >> > > > >> > > I'm not talking about months. In this discussion, Andrey and Ivan > >> > proposed > >> > > a couple of fixes that may help. > >> > > > >> > > It will require a day or two to check if it helps. If it not helpful > >> then > >> > > we should modify startup scripts to say clearly that Java 12 is not > >> > > supported. > >> > > > >> > > Now under Java 12 Ignite suggests to set startup parameters, but > even > >> > with > >> > > correct parameters, it fails and says please set parameters. Totally > >> > > unclear for end-user. > >> > > > >> > > I've reopened https://issues.apache.org/jira/browse/IGNITE-11600 > >> > > > >> > > Sincerely, > >> > > Dmitriy Pavlov > >> > > > >> > > чт, 28 мар. 2019 г. в 18:51, Denis Magda : > >> > > > >> > >> If the failure handler improvements will lower down a number of > >> > >> false-positive cluster shutdowns then I'm for the fix inclusion to > >> the > >> > >> release. > >> > >> > >> > >> As for Java 12, I would put to the next release that we can make > >> shortly > >> > >> after this one. We don't need to wait for months if there are some > >> > urgent > >> > >> fixes. > >> > >> > >> > >> - > >> > >> Denis > >> > >> > >> > >> > >> > >> On Thu, Mar 28, 2019 at 8:46 AM Dmitriy Pavlov > > >> > >> wrote: > >> > >> > >> > >> > Denis, I also +1 for python fix. Today is the planned date of > code > >> > >> freeze, > >> > >> > so today or tomorrow I'll announce it. > >> > >> > > >> > >> > Only one thing was suggested is the fix for failure handlers. I > >> don't > >> > >> > deeply understand the pros and cons, but I'm sure we should > >> courteous > >> > >> > enough for wait experienced folks to come to a consensus. > >> > >> > > >> > >> > One more thing I suggest to check after code freeze, it is Java > >> 12. It > >> > >> does > >> > >> > not work now, but with thanks to Andrey G and Ivan P. we probably > >> have > >> > >> not > >> > >> > very complex solution for this. > >> > >> > > >> > >> > So these 2 fixes are last candidates to come to scope. WDYT? > >> > >> > > >> > >> > Sincerely, > >> > >> > Dmitriy Pavlov > >> > >> > > >> > >> > чт, 28 мар. 2019 г. в 18:10, Denis Magda : > >> > >> > > >> > >> > > Yes, the Python example's fix makes sense - that's a usability > >> issue > >> > >> and > >> > >> > > doesn't affect the core components. > >> > >> > > > >> > >> > > In general, I would suggest us to do a code freeze and push > other > >> > >> changes > >> > >> > > to another release. We can't include everything. > >> > >> > > > >> > >> > > - > >> > >> > > Denis > >> > >> > > > >> > >> > > > >> > >> > > On Thu, Mar 28, 2019 at 3:01 AM Ilya Kasnacheev < > >> > >> > ilya.kasnach...@gmail.com > >> > >> > > > > >> > >> > > wrote: > >>
[jira] [Created] (IGNITE-11699) Node can't start after forced shutdown if the wal archiver disabled
Pavel Vinokurov created IGNITE-11699:
Summary: Node can't start after forced shutdown if the wal
archiver disabled
Key: IGNITE-11699
URL: https://issues.apache.org/jira/browse/IGNITE-11699
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 2.7
Reporter: Pavel Vinokurov
If a server node killed with the disabled wal archive, it could fail on start
with following exception:
{code:java}
[18:37:53,887][SEVERE][sys-stripe-1-#2][G] Failed to execute runnable.
java.lang.IllegalStateException: Failed to get page IO instance (page content
is corrupted)
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85)
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97)
at
org.apache.ignite.internal.pagemem.wal.record.delta.MetaPageUpdatePartitionDataRecord.applyDelta(MetaPageUpdatePartitionDataRecord.java:109)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyPageDelta(GridCacheDatabaseSharedManager.java:2532)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$performBinaryMemoryRestore$11(GridCacheDatabaseSharedManager.java:2327)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApplyPage$12(GridCacheDatabaseSharedManager.java:2441)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApply$13(GridCacheDatabaseSharedManager.java:2479)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:550)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
The reproducer is attached(works only on Linux).
Steps to run the reproducer.
1. Copy config/server.xml into IGNITE_HOME/config folder;
2. Set IGNITE_HOME in the CorruptionReproducer class;
3. Launch CorruptionReproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
