Re: [DISCUSSION] Release Apache Ignite 2.7.5-rc4
Vyacheslav, > Ivan, try to clean local repo (~/m2) and rebuild the project once again > according to DEVNOTES.txt Thank you for suggestion! But what problem it will solve? пт, 7 июн. 2019 г. в 00:52, Dmitriy Pavlov : > > Hi Vyacheslav, > > I'm sorry for being too formal here, although could you please cast your > vote in > https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E > > And thank you for advice on how to check examples. > > Sincerely > Dmitriy Pavlov > > чт, 6 июн. 2019 г. в 22:37, Vyacheslav Daradur : > > > +1 from me. Built from sources and run several examples. > > > > Ivan, try to clean local repo (~/m2) and rebuild the project once > > again according to DEVNOTES.txt > > > > On Thu, Jun 6, 2019 at 7:37 PM Павлухин Иван wrote: > > > > > > I spent a while running examples for RC from bin package. I did the > > following: > > > 1. "mvn clean install" for src package in order to have all > > > dependencies needed for examples in local maven repo on my machine. > > > 2. Tried to compile and launch examples from bin package. > > > 2.1 Failed claiming that classes from org.jetbrains.annotations are > > > not present on classpath. > > > 2.2. Fixed by adding a corresponding dependency to examples pom > > > manually. Run SQL examples successfully. > > > > > > So, I observed following glitches: > > > 1. Missing dependency containing org.jetbrains.annotations in examples > > > in bin package. > > > 2. "2018 Copyright(C) Apache Software Foundation" with year 2018 in > > > console output when starting ignite (using examples main classes and > > > ignite.sh). > > > 3. Some mix of versions reported by nodes launched in different ways. > > > 3.1 ignite.sh from bin package -- ver. 2.7.5#20190603-sha1:be4f2a15 > > > 3.2. examples main classes from bin package -- ver. > > 2.7.5#19700101-sha1:DEV > > > 3.3. examples main classes from src package -- ver. > > > 2.7.5-SNAPSHOT#19700101-sha1:DEV > > > > > > ср, 5 июн. 2019 г. в 18:59, Dmitriy Pavlov : > > > > > > > > I managed to get some build using build number from 1. Release build > > step > > > > (for that case - 20) > > > > > > > > The result can be found here > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4049646&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=artifacts#%2Fsrc > > > > > > > > Pavel T., Peter I., > > > > > > > > Please confirm that it is sufficient. I'll update the release manager > > notes > > > > with steps required to run this configuration. > > > > > > > > Sincerely > > > > Dmitriy Pavlov > > > > > > > > ср, 5 июн. 2019 г. в 18:07, Dmitriy Pavlov : > > > > > > > > > I've found only this step > > > > > > > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildTypeStatusDiv&branch_Releases_ApacheIgniteMain=__all_branches__ > > > > > > > > > > > > > > > It requires some build counter. > > > > > > > > > > Peter I, could you please chime in? > > > > > > > > > > ср, 5 июн. 2019 г. в 18:02, Dmitriy Pavlov : > > > > > > > > > >> Hi Igniters, Pavel T., > > > > >> > > > > >> I'm struggling to find clear steps for building/uploading NuGet > > packages. > > > > >> How can I double check if it was built or not? What should I do? > > > > >> > > > > >> In some internal notes, I've found that NuGet upload can't be > > undone, and > > > > >> in > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process it > > > > >> is a post-release step. > > > > >> > > > > >> Please advise, both here or in private. I will update the > > instructions > > > > >> accordingly. > > > > >> > > > > >> Sincerely > > > > >> Dmitriy Pavlov > > > > >> > > > > >> ср, 5 июн. 2019 г. в 15:27, Dmitriy Pavlov : > > > > >> > > > > >>> Hi Ivan, > > > > >>> > > > > >>> In code there are 2 differences: > > > > >>> - TLSv1.2 is used as a default protocol for Communication in case > > SSL is > > > > >>> used. > > > > >>> - version changed for all pom files, so apache-ignite-src.zip now > > > > >>> contains correct version instead of -SNAPSHOT. > > > > >>> > > > > >>> Sincerely, > > > > >>> Dmitriy Pavlov > > > > >>> > > > > >>> > > > > >>> ср, 5 июн. 2019 г. в 10:49, Павлухин Иван : > > > > >>> > > > > Dmitriy, > > > > > > > > Are there any differences between 2.7.5-rc4 and a previous RC? > > > > > > > > вт, 4 июн. 2019 г. в 20:35, Dmitriy Pavlov : > > > > > > > > > > Dear Community, > > > > > > > > > > > > > > > > > > > > Please use this thread for all non-voting, discussion, questions > > > > related to > > > > > this release. > > > > > > > > > > > > > > > > > > > > Cast your vote here > > > > > > > > > > > https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E > > > > > > > > > > > > > > > Since NuGet is a post-release
Re: SQL query crashes Ignite.
Hello,
This exception is unrelated to memory usage. The logs report that a wrong
schema is used:
Caused by: org.h2.jdbc.JdbcSQLException: Schema "FEATURE_TILE_CACHE" not
found; SQL statement:
Set schema PUBLIC as part of the JDBC connection string or pass it via the
queries:
https://apacheignite-sql.readme.io/docs/jdbc-driver
-
Denis
On Thu, Jun 6, 2019 at 2:14 PM Shane Duan wrote:
> Hi Igniters,
>
> I am testing SQL with Ignite. With the following simple tests, queries
> fails with out-of-memory error, and Ignite is not usable anymore until
> restart.
>
> It seems Ignite need get all the records to be returned in heap first
> before transferring data to client side. This can be problematic since
> even with large heap size, this problem may still happens depend the size
> of the data to be returned and how many concurrent queries
>
> In my case, persistent is on for the data region(named as
> storageWithPersistence); with default heap size (1GB). Here is the simple
> tests:
>
> public class JDBCTestWithTemplate_LargeDataSet {
>
>
> public static void main(String[] args) {
>
> int len = 10 * 1204 * 1024; // 10M
> byte[] binaryData = new byte[len];
> for (int i=0; i < len; i++) {
> binaryData[i] = 1;
> }
>
> Connection conn = null;
> try{
>
> // Create a JDBC connection
> conn = TestUtils.prepareIgniteJDBCConnection(args);
>
> // Create City table based on FeatureTileCacheTemplateName_1_Day
> template
> // This template use a data region with persistent on.
> executeSQL(conn, "DROP TABLE IF EXISTS CITY ");
> executeSQL(conn,
> "CREATE TABLE IF NOT EXISTS CITY (id LONG PRIMARY KEY, val
> BINARY) " +
> "with \"TEMPLATE=" +
> CacheConfigurationTemplates.FeatureTileCacheTemplateName_1_Day+ "\"");
>
>
> String sql = "INSERT INTO CITY (id, val) VALUES(?, ?)";
> PreparedStatement pstmt = conn.prepareStatement(sql);
>
> // create some binary data
> String myData = "Adding test data ...";
>
> // set value for the prepared statement
> for (int i = 0; i < 1000; i++) {
> pstmt.setInt(1, i);
> pstmt.setBytes(2, binaryData);
> pstmt.executeUpdate();
> }
> pstmt.close();
>
> Thread.sleep(1);
>
> try (Statement stmt = conn.createStatement()) {
> try (ResultSet rs =
> stmt.executeQuery("SELECT id, val FROM CITY WHERE id <
> 100")) {
> while(rs.next()) {
> System.out.println(">>> Retrieved id " + rs.getLong(1));
> }
> }
> }
>
>
> } catch (Exception e) {
> System.err.format("Unexpected failure: %s\n", e);
> e.printStackTrace();
> } finally {
> if (conn != null) {
> System.out.print("Dropped database objects...");
> try {
> executeSQL(conn, "DROP TABLE IF EXISTS CITY ");
> conn.close();
> } catch (Exception ignore) {
>
> }
> }
> }
> }
>
> /**
>* Execute SQL command.
>*
>* @param conn Connection.
>* @param sql SQL statement.
>* @throws Exception If failed.
>*/
> private static void executeSQL(Connection conn, String sql) throws
> Exception {
> try (Statement stmt = conn.createStatement()) {
> stmt.executeUpdate(sql);
> }
> }
> }
>
>
> The following are from the Ignite logs:
>
> 2019-06-06 10:45:03,952 INFO
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=9f8714ae, name=cs_ittbix3, uptime=00:04:00.038]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=8]
> ^-- CPU [cur=-100%, avg=-99.07%, GC=0%]
> ^-- PageMemory [pages=254721]
> ^-- Heap [used=179MB, free=82.5%, comm=1024MB]
> ^-- Off-heap [used=1006MB, free=57.13%, comm=1836MB]
> ^-- sysMemPlc region [used=0MB, free=99.99%, comm=100MB]
> ^-- default region [used=4MB, free=99.61%, comm=512MB]
> ^-- metastoreMemPlc region [used=0MB, free=99.94%, comm=100MB]
> ^-- storageWithPersistence region [used=1002MB, free=2.1%,
> comm=1024MB]
> ^-- TxLog region [used=0MB, free=100%, comm=100MB]
> ^-- Ignite persistence [used=11988MB]
> ^-- sysMemPlc region [used=0MB]
> ^-- metastoreMemPlc region [used=unknown]
> ^-- storageWithPersistence region [used=11988MB]
> ^-- TxLog region [used=0MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=6, qSize=0]
> ..
>
> 2019-06-06 10:50:20,011 DEBUG Client request received [reqId=0, addr=/
> 10.212.22.67:54554, req=JdbcQueryExecuteRequest
> [schemaName=FEATURE_TILE_CACHE, pageSize=1024, maxRows=0, sqlQry=SELECT id,
> val FROM CITY WHERE id > 500, args=[], stmtType=SELECT_STATEMENT_TYPE,
> autoCommit=true]]
> 2019-06-06 10:50:20,011 DEBUG Parsed query: `SELECT id, val FROM CITY WHERE
> id > 500` into two step query: GridCacheTwoStepQuery
> [mapQrys=[GridCacheSqlQ
Re: [VOTE] Release Apache Ignite 2.7.5-rc4
+1 - checked ML examples
Best regards,
Yuriy Babak
чт, 6 июн. 2019 г. в 19:16, Павлухин Иван :
> +1
> Launched a couple of nodes using bin package. Run SQL examples
> successfully (but with some troubles along the way).
>
> чт, 6 июн. 2019 г. в 17:01, Igor Sapego :
> >
> > +1 - checked C++ build
> >
> > Best Regards,
> > Igor
> >
> >
> > On Thu, Jun 6, 2019 at 4:33 PM Alexey Goncharuk <
> alexey.goncha...@gmail.com>
> > wrote:
> >
> > > +1 (binding) - checked build from source, persistence example and basic
> > > control.sh commands.
> > >
> > > ср, 5 июн. 2019 г. в 17:48, Andrey Gura :
> > >
> > > > +1 (binding)
> > > >
> > > > On Wed, Jun 5, 2019 at 4:39 PM Ilya Kasnacheev
> > > > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL
> > > > Cluster
> > > > > on Java 11 and Java 8 without tuning any flags.
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > ср, 5 июн. 2019 г. в 09:44, Nikolay Izhikov :
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Nice to have clusters nodes started with ignite.sh in my JVM 11
> > > > > > environment
> > > > > > > without any settings.
> > > > > > >
> > > > > > > -
> > > > > > > Denis
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov <
> dpav...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Dear Community,
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > We have uploaded release candidate to
> > > > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc4/
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > The following staging can be used for a dependent project for
> > > > testing:
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> https://repository.apache.org/content/repositories/orgapacheignite-1463/
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > This is half-release before 2.8 containing Java 11 support
> and
> > > > fixes
> > > > > > for
> > > > > > > > Native Persistence storage.
> > > > > > > >
> > > > > > > > Tag name is 2.7.5-rc4:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc4
> > > > > > > >
> > > > > > > > 2.7.5 changes:
> > > > > > > >
> > > > > > > > * Added Java 11 support
> > > > > > > >
> > > > > > > > * Fixed infinite looping during SSL handshake, affecting Java
> > > > > > 11/Windows
> > > > > > > >
> > > > > > > > * Fixed storage corruption case after incorrectly rotated
> page
> > > > > > > >
> > > > > > > > * Erroneous WAL record after incorrectly rotated page
> processed
> > > > > > > > automatically
> > > > > > > >
> > > > > > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting
> Java
> > > > 11
> > > > > > > >
> > > > > > > > * Launch scripts and some Ignite initialization steps were
> fixed
> > > > for
> > > > > > Java
> > > > > > > > 12
> > > > > > > >
> > > > > > > > * Fixed indexes corruption on node stop under load
> > > > > > > >
> > > > > > > > * Fixed case of node crash during node deactivation
> > > > > > > >
> > > > > > > > * Error message with advice about required JVM parameters
> printed
> > > > when
> > > > > > Java
> > > > > > > > 9+ is used
> > > > > > > >
> > > > > > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Complete list of closed issues:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> > >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
> > > > > > > >
> > > > > > > > DEVNOTES
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > > > > > > >
> > > > > > > > RELEASE NOTES
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
> > > > > > > >
> > > > > > > > The vote is formal, see voting guidelines
> > > > > > > > https://www.apache.org/foundation/voting.html
> > > > > > > >
> > > > > > > > +1 - to accept Apache Ignite 2.7.5-rc4
> > > > > > > >
> > > > > > > > 0 - don't care either way
> > > > > > > >
> > > > > > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc4 (explain
> why)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > See notes on how to verify release here
> > > > > > > >
> > > > > > > > https://www.apache.org/info/verification.html
> > > > > > > >
> > > > > > > > and
> > > > > > > >
> > > > > > > >
>
Re: [DISCUSSION] Release Apache Ignite 2.7.5-rc4
Hi Vyacheslav, I'm sorry for being too formal here, although could you please cast your vote in https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E And thank you for advice on how to check examples. Sincerely Dmitriy Pavlov чт, 6 июн. 2019 г. в 22:37, Vyacheslav Daradur : > +1 from me. Built from sources and run several examples. > > Ivan, try to clean local repo (~/m2) and rebuild the project once > again according to DEVNOTES.txt > > On Thu, Jun 6, 2019 at 7:37 PM Павлухин Иван wrote: > > > > I spent a while running examples for RC from bin package. I did the > following: > > 1. "mvn clean install" for src package in order to have all > > dependencies needed for examples in local maven repo on my machine. > > 2. Tried to compile and launch examples from bin package. > > 2.1 Failed claiming that classes from org.jetbrains.annotations are > > not present on classpath. > > 2.2. Fixed by adding a corresponding dependency to examples pom > > manually. Run SQL examples successfully. > > > > So, I observed following glitches: > > 1. Missing dependency containing org.jetbrains.annotations in examples > > in bin package. > > 2. "2018 Copyright(C) Apache Software Foundation" with year 2018 in > > console output when starting ignite (using examples main classes and > > ignite.sh). > > 3. Some mix of versions reported by nodes launched in different ways. > > 3.1 ignite.sh from bin package -- ver. 2.7.5#20190603-sha1:be4f2a15 > > 3.2. examples main classes from bin package -- ver. > 2.7.5#19700101-sha1:DEV > > 3.3. examples main classes from src package -- ver. > > 2.7.5-SNAPSHOT#19700101-sha1:DEV > > > > ср, 5 июн. 2019 г. в 18:59, Dmitriy Pavlov : > > > > > > I managed to get some build using build number from 1. Release build > step > > > (for that case - 20) > > > > > > The result can be found here > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4049646&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=artifacts#%2Fsrc > > > > > > Pavel T., Peter I., > > > > > > Please confirm that it is sufficient. I'll update the release manager > notes > > > with steps required to run this configuration. > > > > > > Sincerely > > > Dmitriy Pavlov > > > > > > ср, 5 июн. 2019 г. в 18:07, Dmitriy Pavlov : > > > > > > > I've found only this step > > > > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildTypeStatusDiv&branch_Releases_ApacheIgniteMain=__all_branches__ > > > > > > > > > > > > It requires some build counter. > > > > > > > > Peter I, could you please chime in? > > > > > > > > ср, 5 июн. 2019 г. в 18:02, Dmitriy Pavlov : > > > > > > > >> Hi Igniters, Pavel T., > > > >> > > > >> I'm struggling to find clear steps for building/uploading NuGet > packages. > > > >> How can I double check if it was built or not? What should I do? > > > >> > > > >> In some internal notes, I've found that NuGet upload can't be > undone, and > > > >> in > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process it > > > >> is a post-release step. > > > >> > > > >> Please advise, both here or in private. I will update the > instructions > > > >> accordingly. > > > >> > > > >> Sincerely > > > >> Dmitriy Pavlov > > > >> > > > >> ср, 5 июн. 2019 г. в 15:27, Dmitriy Pavlov : > > > >> > > > >>> Hi Ivan, > > > >>> > > > >>> In code there are 2 differences: > > > >>> - TLSv1.2 is used as a default protocol for Communication in case > SSL is > > > >>> used. > > > >>> - version changed for all pom files, so apache-ignite-src.zip now > > > >>> contains correct version instead of -SNAPSHOT. > > > >>> > > > >>> Sincerely, > > > >>> Dmitriy Pavlov > > > >>> > > > >>> > > > >>> ср, 5 июн. 2019 г. в 10:49, Павлухин Иван : > > > >>> > > > Dmitriy, > > > > > > Are there any differences between 2.7.5-rc4 and a previous RC? > > > > > > вт, 4 июн. 2019 г. в 20:35, Dmitriy Pavlov : > > > > > > > > Dear Community, > > > > > > > > > > > > > > > > Please use this thread for all non-voting, discussion, questions > > > related to > > > > this release. > > > > > > > > > > > > > > > > Cast your vote here > > > > > > > > https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E > > > > > > > > > > > > Since NuGet is a post-release step, I will proceed with it > shortly. > > > > > > > > > > > > > > > > Sincerely, > > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > -- > > > Best regards, > > > Ivan Pavlukhin > > > > > > >>> > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > > -- > Best Regards, Vyacheslav D. >
SQL query crashes Ignite.
Hi Igniters,
I am testing SQL with Ignite. With the following simple tests, queries
fails with out-of-memory error, and Ignite is not usable anymore until
restart.
It seems Ignite need get all the records to be returned in heap first
before transferring data to client side. This can be problematic since
even with large heap size, this problem may still happens depend the size
of the data to be returned and how many concurrent queries
In my case, persistent is on for the data region(named as
storageWithPersistence); with default heap size (1GB). Here is the simple
tests:
public class JDBCTestWithTemplate_LargeDataSet {
public static void main(String[] args) {
int len = 10 * 1204 * 1024; // 10M
byte[] binaryData = new byte[len];
for (int i=0; i < len; i++) {
binaryData[i] = 1;
}
Connection conn = null;
try{
// Create a JDBC connection
conn = TestUtils.prepareIgniteJDBCConnection(args);
// Create City table based on FeatureTileCacheTemplateName_1_Day template
// This template use a data region with persistent on.
executeSQL(conn, "DROP TABLE IF EXISTS CITY ");
executeSQL(conn,
"CREATE TABLE IF NOT EXISTS CITY (id LONG PRIMARY KEY, val BINARY) " +
"with \"TEMPLATE=" +
CacheConfigurationTemplates.FeatureTileCacheTemplateName_1_Day+ "\"");
String sql = "INSERT INTO CITY (id, val) VALUES(?, ?)";
PreparedStatement pstmt = conn.prepareStatement(sql);
// create some binary data
String myData = "Adding test data ...";
// set value for the prepared statement
for (int i = 0; i < 1000; i++) {
pstmt.setInt(1, i);
pstmt.setBytes(2, binaryData);
pstmt.executeUpdate();
}
pstmt.close();
Thread.sleep(1);
try (Statement stmt = conn.createStatement()) {
try (ResultSet rs =
stmt.executeQuery("SELECT id, val FROM CITY WHERE id < 100")) {
while(rs.next()) {
System.out.println(">>> Retrieved id " + rs.getLong(1));
}
}
}
} catch (Exception e) {
System.err.format("Unexpected failure: %s\n", e);
e.printStackTrace();
} finally {
if (conn != null) {
System.out.print("Dropped database objects...");
try {
executeSQL(conn, "DROP TABLE IF EXISTS CITY ");
conn.close();
} catch (Exception ignore) {
}
}
}
}
/**
* Execute SQL command.
*
* @param conn Connection.
* @param sql SQL statement.
* @throws Exception If failed.
*/
private static void executeSQL(Connection conn, String sql) throws Exception {
try (Statement stmt = conn.createStatement()) {
stmt.executeUpdate(sql);
}
}
}
The following are from the Ignite logs:
2019-06-06 10:45:03,952 INFO
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=9f8714ae, name=cs_ittbix3, uptime=00:04:00.038]
^-- H/N/C [hosts=1, nodes=1, CPUs=8]
^-- CPU [cur=-100%, avg=-99.07%, GC=0%]
^-- PageMemory [pages=254721]
^-- Heap [used=179MB, free=82.5%, comm=1024MB]
^-- Off-heap [used=1006MB, free=57.13%, comm=1836MB]
^-- sysMemPlc region [used=0MB, free=99.99%, comm=100MB]
^-- default region [used=4MB, free=99.61%, comm=512MB]
^-- metastoreMemPlc region [used=0MB, free=99.94%, comm=100MB]
^-- storageWithPersistence region [used=1002MB, free=2.1%,
comm=1024MB]
^-- TxLog region [used=0MB, free=100%, comm=100MB]
^-- Ignite persistence [used=11988MB]
^-- sysMemPlc region [used=0MB]
^-- metastoreMemPlc region [used=unknown]
^-- storageWithPersistence region [used=11988MB]
^-- TxLog region [used=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=6, qSize=0]
..
2019-06-06 10:50:20,011 DEBUG Client request received [reqId=0, addr=/
10.212.22.67:54554, req=JdbcQueryExecuteRequest
[schemaName=FEATURE_TILE_CACHE, pageSize=1024, maxRows=0, sqlQry=SELECT id,
val FROM CITY WHERE id > 500, args=[], stmtType=SELECT_STATEMENT_TYPE,
autoCommit=true]]
2019-06-06 10:50:20,011 DEBUG Parsed query: `SELECT id, val FROM CITY WHERE
id > 500` into two step query: GridCacheTwoStepQuery
[mapQrys=[GridCacheSqlQuery [qry=SELECT
__Z0.ID __C0_0,
__Z0.VAL __C0_1
FROM FEATURE_TILE_CACHE.CITY __Z0
WHERE __Z0.ID > 500, paramIdxs=[], cols={__C0_0=GridSqlType [type=5,
scale=0, precision=19, displaySize=20, sql=BIGINT], __C0_1=GridSqlType
[type=12, scale=0, precision=2147483647, displaySize=2147483647,
sql=VARBINARY]}, alias=null, sort=[], partitioned=true, node=null,
derivedPartitions=null, hasSubQries=false]], rdc=GridCacheSqlQuery
[qry=SELECT
__C0_0 ID,
__C0_1 VAL
FROM PUBLIC.__T0, paramIdxs=[], cols=null, alias=null, sort=null,
partitioned=false, node=null, derivedPartitions=null, hasSubQries=false],
pageSize=1024, explain=false, originalSql=SEL
Re: [DISCUSSION] Release Apache Ignite 2.7.5-rc4
+1 from me. Built from sources and run several examples. Ivan, try to clean local repo (~/m2) and rebuild the project once again according to DEVNOTES.txt On Thu, Jun 6, 2019 at 7:37 PM Павлухин Иван wrote: > > I spent a while running examples for RC from bin package. I did the following: > 1. "mvn clean install" for src package in order to have all > dependencies needed for examples in local maven repo on my machine. > 2. Tried to compile and launch examples from bin package. > 2.1 Failed claiming that classes from org.jetbrains.annotations are > not present on classpath. > 2.2. Fixed by adding a corresponding dependency to examples pom > manually. Run SQL examples successfully. > > So, I observed following glitches: > 1. Missing dependency containing org.jetbrains.annotations in examples > in bin package. > 2. "2018 Copyright(C) Apache Software Foundation" with year 2018 in > console output when starting ignite (using examples main classes and > ignite.sh). > 3. Some mix of versions reported by nodes launched in different ways. > 3.1 ignite.sh from bin package -- ver. 2.7.5#20190603-sha1:be4f2a15 > 3.2. examples main classes from bin package -- ver. 2.7.5#19700101-sha1:DEV > 3.3. examples main classes from src package -- ver. > 2.7.5-SNAPSHOT#19700101-sha1:DEV > > ср, 5 июн. 2019 г. в 18:59, Dmitriy Pavlov : > > > > I managed to get some build using build number from 1. Release build step > > (for that case - 20) > > > > The result can be found here > > https://ci.ignite.apache.org/viewLog.html?buildId=4049646&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=artifacts#%2Fsrc > > > > Pavel T., Peter I., > > > > Please confirm that it is sufficient. I'll update the release manager notes > > with steps required to run this configuration. > > > > Sincerely > > Dmitriy Pavlov > > > > ср, 5 июн. 2019 г. в 18:07, Dmitriy Pavlov : > > > > > I've found only this step > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildTypeStatusDiv&branch_Releases_ApacheIgniteMain=__all_branches__ > > > > > > > > > It requires some build counter. > > > > > > Peter I, could you please chime in? > > > > > > ср, 5 июн. 2019 г. в 18:02, Dmitriy Pavlov : > > > > > >> Hi Igniters, Pavel T., > > >> > > >> I'm struggling to find clear steps for building/uploading NuGet packages. > > >> How can I double check if it was built or not? What should I do? > > >> > > >> In some internal notes, I've found that NuGet upload can't be undone, and > > >> in https://cwiki.apache.org/confluence/display/IGNITE/Release+Process it > > >> is a post-release step. > > >> > > >> Please advise, both here or in private. I will update the instructions > > >> accordingly. > > >> > > >> Sincerely > > >> Dmitriy Pavlov > > >> > > >> ср, 5 июн. 2019 г. в 15:27, Dmitriy Pavlov : > > >> > > >>> Hi Ivan, > > >>> > > >>> In code there are 2 differences: > > >>> - TLSv1.2 is used as a default protocol for Communication in case SSL is > > >>> used. > > >>> - version changed for all pom files, so apache-ignite-src.zip now > > >>> contains correct version instead of -SNAPSHOT. > > >>> > > >>> Sincerely, > > >>> Dmitriy Pavlov > > >>> > > >>> > > >>> ср, 5 июн. 2019 г. в 10:49, Павлухин Иван : > > >>> > > Dmitriy, > > > > Are there any differences between 2.7.5-rc4 and a previous RC? > > > > вт, 4 июн. 2019 г. в 20:35, Dmitriy Pavlov : > > > > > > Dear Community, > > > > > > > > > > > > Please use this thread for all non-voting, discussion, questions > > related to > > > this release. > > > > > > > > > > > > Cast your vote here > > > > > https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E > > > > > > > > > Since NuGet is a post-release step, I will proceed with it shortly. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > > >>> > > > > -- > Best regards, > Ivan Pavlukhin -- Best Regards, Vyacheslav D.
Re: Merge PRs via GitHub web UI
Dmitriy, Yes, I agree that it is a totally great feature! But I would like to be sure that it does no harm. BTW, I use a copy of git repo on my machine to deal with merges without touching my working tree. чт, 6 июн. 2019 г. в 19:21, Dmitriy Pavlov : > > Hi Ivan, Igniters, > > Merge PRs via GitHub is the greatest change that Infra did recently. > > You can merge PRs without changing your local project state, and which is > why I believe is an absolutely positive thing for the community. Committers > can do a review-merge while waiting for tests run, doing a big feature > locally: any activity they have locally does not affect review now. > > Sincerely, > Dmitriy Pavlov > > чт, 6 июн. 2019 г. в 19:03, Павлухин Иван : > > > It seems that the majority of recent commits were made manually. If I > > am not mistaken there should be a badge with a green text "Verified" > > near a commit if it was made via GitHub web UI. And currently I see > > only a few such commits. > > > > чт, 6 июн. 2019 г. в 18:48, Petr Ivanov : > > > > > > If it was really GitHub problem — it is still single incident among many > > tens of merges every day. > > > Manual merge after review would more erroneous I guess. > > > > > > > > > > On 6 Jun 2019, at 18:43, Павлухин Иван wrote: > > > > > > > > Hi Igniters, > > > > > > > > I find merging PRs using GitHub web UI quite handy. AFAIK it is > > > > possible to merge AI PR in this way. But I heard some rumors that > > > > there were some problems with squashing such merges leading to commits > > > > with multiple parents in master > > > > > > > > From recent there is one commit [1] but I am not sure that GitHub > > > > merge caused it. > > > > > > > > So, my general question is as follows. Should we merge PRs via GitHub > > > > web UI or should we avoid it? > > > > > > > > [1] > > https://github.com/apache/ignite/commit/22652aa9883cfa3fd020658bcb230cea9ea6e4d4 > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > -- Best regards, Ivan Pavlukhin
Re: [DISCUSSION] Release Apache Ignite 2.7.5-rc4
I spent a while running examples for RC from bin package. I did the following: 1. "mvn clean install" for src package in order to have all dependencies needed for examples in local maven repo on my machine. 2. Tried to compile and launch examples from bin package. 2.1 Failed claiming that classes from org.jetbrains.annotations are not present on classpath. 2.2. Fixed by adding a corresponding dependency to examples pom manually. Run SQL examples successfully. So, I observed following glitches: 1. Missing dependency containing org.jetbrains.annotations in examples in bin package. 2. "2018 Copyright(C) Apache Software Foundation" with year 2018 in console output when starting ignite (using examples main classes and ignite.sh). 3. Some mix of versions reported by nodes launched in different ways. 3.1 ignite.sh from bin package -- ver. 2.7.5#20190603-sha1:be4f2a15 3.2. examples main classes from bin package -- ver. 2.7.5#19700101-sha1:DEV 3.3. examples main classes from src package -- ver. 2.7.5-SNAPSHOT#19700101-sha1:DEV ср, 5 июн. 2019 г. в 18:59, Dmitriy Pavlov : > > I managed to get some build using build number from 1. Release build step > (for that case - 20) > > The result can be found here > https://ci.ignite.apache.org/viewLog.html?buildId=4049646&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=artifacts#%2Fsrc > > Pavel T., Peter I., > > Please confirm that it is sufficient. I'll update the release manager notes > with steps required to run this configuration. > > Sincerely > Dmitriy Pavlov > > ср, 5 июн. 2019 г. в 18:07, Dmitriy Pavlov : > > > I've found only this step > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildTypeStatusDiv&branch_Releases_ApacheIgniteMain=__all_branches__ > > > > > > It requires some build counter. > > > > Peter I, could you please chime in? > > > > ср, 5 июн. 2019 г. в 18:02, Dmitriy Pavlov : > > > >> Hi Igniters, Pavel T., > >> > >> I'm struggling to find clear steps for building/uploading NuGet packages. > >> How can I double check if it was built or not? What should I do? > >> > >> In some internal notes, I've found that NuGet upload can't be undone, and > >> in https://cwiki.apache.org/confluence/display/IGNITE/Release+Process it > >> is a post-release step. > >> > >> Please advise, both here or in private. I will update the instructions > >> accordingly. > >> > >> Sincerely > >> Dmitriy Pavlov > >> > >> ср, 5 июн. 2019 г. в 15:27, Dmitriy Pavlov : > >> > >>> Hi Ivan, > >>> > >>> In code there are 2 differences: > >>> - TLSv1.2 is used as a default protocol for Communication in case SSL is > >>> used. > >>> - version changed for all pom files, so apache-ignite-src.zip now > >>> contains correct version instead of -SNAPSHOT. > >>> > >>> Sincerely, > >>> Dmitriy Pavlov > >>> > >>> > >>> ср, 5 июн. 2019 г. в 10:49, Павлухин Иван : > >>> > Dmitriy, > > Are there any differences between 2.7.5-rc4 and a previous RC? > > вт, 4 июн. 2019 г. в 20:35, Dmitriy Pavlov : > > > > Dear Community, > > > > > > > > Please use this thread for all non-voting, discussion, questions > related to > > this release. > > > > > > > > Cast your vote here > > > https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E > > > > > > Since NuGet is a post-release step, I will proceed with it shortly. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > -- > Best regards, > Ivan Pavlukhin > > >>> -- Best regards, Ivan Pavlukhin
Re: Merge PRs via GitHub web UI
Hi Ivan, Igniters, Merge PRs via GitHub is the greatest change that Infra did recently. You can merge PRs without changing your local project state, and which is why I believe is an absolutely positive thing for the community. Committers can do a review-merge while waiting for tests run, doing a big feature locally: any activity they have locally does not affect review now. Sincerely, Dmitriy Pavlov чт, 6 июн. 2019 г. в 19:03, Павлухин Иван : > It seems that the majority of recent commits were made manually. If I > am not mistaken there should be a badge with a green text "Verified" > near a commit if it was made via GitHub web UI. And currently I see > only a few such commits. > > чт, 6 июн. 2019 г. в 18:48, Petr Ivanov : > > > > If it was really GitHub problem — it is still single incident among many > tens of merges every day. > > Manual merge after review would more erroneous I guess. > > > > > > > On 6 Jun 2019, at 18:43, Павлухин Иван wrote: > > > > > > Hi Igniters, > > > > > > I find merging PRs using GitHub web UI quite handy. AFAIK it is > > > possible to merge AI PR in this way. But I heard some rumors that > > > there were some problems with squashing such merges leading to commits > > > with multiple parents in master > > > > > > From recent there is one commit [1] but I am not sure that GitHub > > > merge caused it. > > > > > > So, my general question is as follows. Should we merge PRs via GitHub > > > web UI or should we avoid it? > > > > > > [1] > https://github.com/apache/ignite/commit/22652aa9883cfa3fd020658bcb230cea9ea6e4d4 > > > > > > -- > > > Best regards, > > > Ivan Pavlukhin > > > > > -- > Best regards, > Ivan Pavlukhin >
Re: [VOTE] Release Apache Ignite 2.7.5-rc4
+1
Launched a couple of nodes using bin package. Run SQL examples
successfully (but with some troubles along the way).
чт, 6 июн. 2019 г. в 17:01, Igor Sapego :
>
> +1 - checked C++ build
>
> Best Regards,
> Igor
>
>
> On Thu, Jun 6, 2019 at 4:33 PM Alexey Goncharuk
> wrote:
>
> > +1 (binding) - checked build from source, persistence example and basic
> > control.sh commands.
> >
> > ср, 5 июн. 2019 г. в 17:48, Andrey Gura :
> >
> > > +1 (binding)
> > >
> > > On Wed, Jun 5, 2019 at 4:39 PM Ilya Kasnacheev
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL
> > > Cluster
> > > > on Java 11 and Java 8 without tuning any flags.
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > ср, 5 июн. 2019 г. в 09:44, Nikolay Izhikov :
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> > > > > > +1 (binding)
> > > > > >
> > > > > > Nice to have clusters nodes started with ignite.sh in my JVM 11
> > > > > environment
> > > > > > without any settings.
> > > > > >
> > > > > > -
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > > On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov
> > > > > wrote:
> > > > > >
> > > > > > > Dear Community,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > We have uploaded release candidate to
> > > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc4/
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > The following staging can be used for a dependent project for
> > > testing:
> > > > > > >
> > > > > > >
> > > > >
> > > https://repository.apache.org/content/repositories/orgapacheignite-1463/
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > This is half-release before 2.8 containing Java 11 support and
> > > fixes
> > > > > for
> > > > > > > Native Persistence storage.
> > > > > > >
> > > > > > > Tag name is 2.7.5-rc4:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc4
> > > > > > >
> > > > > > > 2.7.5 changes:
> > > > > > >
> > > > > > > * Added Java 11 support
> > > > > > >
> > > > > > > * Fixed infinite looping during SSL handshake, affecting Java
> > > > > 11/Windows
> > > > > > >
> > > > > > > * Fixed storage corruption case after incorrectly rotated page
> > > > > > >
> > > > > > > * Erroneous WAL record after incorrectly rotated page processed
> > > > > > > automatically
> > > > > > >
> > > > > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java
> > > 11
> > > > > > >
> > > > > > > * Launch scripts and some Ignite initialization steps were fixed
> > > for
> > > > > Java
> > > > > > > 12
> > > > > > >
> > > > > > > * Fixed indexes corruption on node stop under load
> > > > > > >
> > > > > > > * Fixed case of node crash during node deactivation
> > > > > > >
> > > > > > > * Error message with advice about required JVM parameters printed
> > > when
> > > > > Java
> > > > > > > 9+ is used
> > > > > > >
> > > > > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Complete list of closed issues:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
> > > > > > >
> > > > > > > DEVNOTES
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > > > > > >
> > > > > > > RELEASE NOTES
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
> > > > > > >
> > > > > > > The vote is formal, see voting guidelines
> > > > > > > https://www.apache.org/foundation/voting.html
> > > > > > >
> > > > > > > +1 - to accept Apache Ignite 2.7.5-rc4
> > > > > > >
> > > > > > > 0 - don't care either way
> > > > > > >
> > > > > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc4 (explain why)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > See notes on how to verify release here
> > > > > > >
> > > > > > > https://www.apache.org/info/verification.html
> > > > > > >
> > > > > > > and
> > > > > > >
> > > > > > >
> > > > >
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-ReleaseVerification
> > > > > > >
> > > > > > > This vote will be open for at least 72 hours till June 7, 18:00
> > > UTC.
> > > > > > >
> > > > > > >
> > > > >
> > >
> > https://www.timeanddate.com/countdown/to?year=2019&month=6&day=7&hour=18&min=0&sec=0&p0=utc-1
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Best Regards,
> > > > > > >
> > > > > > > Dmitriy Pavlov
> > > > > > >
Re: Merge PRs via GitHub web UI
It seems that the majority of recent commits were made manually. If I am not mistaken there should be a badge with a green text "Verified" near a commit if it was made via GitHub web UI. And currently I see only a few such commits. чт, 6 июн. 2019 г. в 18:48, Petr Ivanov : > > If it was really GitHub problem — it is still single incident among many tens > of merges every day. > Manual merge after review would more erroneous I guess. > > > > On 6 Jun 2019, at 18:43, Павлухин Иван wrote: > > > > Hi Igniters, > > > > I find merging PRs using GitHub web UI quite handy. AFAIK it is > > possible to merge AI PR in this way. But I heard some rumors that > > there were some problems with squashing such merges leading to commits > > with multiple parents in master > > > > From recent there is one commit [1] but I am not sure that GitHub > > merge caused it. > > > > So, my general question is as follows. Should we merge PRs via GitHub > > web UI or should we avoid it? > > > > [1] > > https://github.com/apache/ignite/commit/22652aa9883cfa3fd020658bcb230cea9ea6e4d4 > > > > -- > > Best regards, > > Ivan Pavlukhin > -- Best regards, Ivan Pavlukhin
Re: Merge PRs via GitHub web UI
If it was really GitHub problem — it is still single incident among many tens of merges every day. Manual merge after review would more erroneous I guess. > On 6 Jun 2019, at 18:43, Павлухин Иван wrote: > > Hi Igniters, > > I find merging PRs using GitHub web UI quite handy. AFAIK it is > possible to merge AI PR in this way. But I heard some rumors that > there were some problems with squashing such merges leading to commits > with multiple parents in master > > From recent there is one commit [1] but I am not sure that GitHub > merge caused it. > > So, my general question is as follows. Should we merge PRs via GitHub > web UI or should we avoid it? > > [1] > https://github.com/apache/ignite/commit/22652aa9883cfa3fd020658bcb230cea9ea6e4d4 > > -- > Best regards, > Ivan Pavlukhin
Re: Merge PRs via GitHub web UI
Hello! I always use scripts/apply-pull-request.sh The only downside that it will fail unrecoverably if there are any conflicts. Regards, -- Ilya Kasnacheev чт, 6 июн. 2019 г. в 18:43, Павлухин Иван : > Hi Igniters, > > I find merging PRs using GitHub web UI quite handy. AFAIK it is > possible to merge AI PR in this way. But I heard some rumors that > there were some problems with squashing such merges leading to commits > with multiple parents in master > > From recent there is one commit [1] but I am not sure that GitHub > merge caused it. > > So, my general question is as follows. Should we merge PRs via GitHub > web UI or should we avoid it? > > [1] > https://github.com/apache/ignite/commit/22652aa9883cfa3fd020658bcb230cea9ea6e4d4 > > -- > Best regards, > Ivan Pavlukhin >
Merge PRs via GitHub web UI
Hi Igniters, I find merging PRs using GitHub web UI quite handy. AFAIK it is possible to merge AI PR in this way. But I heard some rumors that there were some problems with squashing such merges leading to commits with multiple parents in master >From recent there is one commit [1] but I am not sure that GitHub merge caused it. So, my general question is as follows. Should we merge PRs via GitHub web UI or should we avoid it? [1] https://github.com/apache/ignite/commit/22652aa9883cfa3fd020658bcb230cea9ea6e4d4 -- Best regards, Ivan Pavlukhin
Re: [VOTE] Release Apache Ignite 2.7.5-rc4
+1 - checked C++ build
Best Regards,
Igor
On Thu, Jun 6, 2019 at 4:33 PM Alexey Goncharuk
wrote:
> +1 (binding) - checked build from source, persistence example and basic
> control.sh commands.
>
> ср, 5 июн. 2019 г. в 17:48, Andrey Gura :
>
> > +1 (binding)
> >
> > On Wed, Jun 5, 2019 at 4:39 PM Ilya Kasnacheev
> > wrote:
> > >
> > > +1
> > >
> > > Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL
> > Cluster
> > > on Java 11 and Java 8 without tuning any flags.
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > ср, 5 июн. 2019 г. в 09:44, Nikolay Izhikov :
> > >
> > > > +1 (binding)
> > > >
> > > > В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> > > > > +1 (binding)
> > > > >
> > > > > Nice to have clusters nodes started with ignite.sh in my JVM 11
> > > > environment
> > > > > without any settings.
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > > >
> > > > > On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov
> > > > wrote:
> > > > >
> > > > > > Dear Community,
> > > > > >
> > > > > >
> > > > > >
> > > > > > We have uploaded release candidate to
> > > > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc4/
> > > > > >
> > > > > >
> > > > > >
> > > > > > The following staging can be used for a dependent project for
> > testing:
> > > > > >
> > > > > >
> > > >
> > https://repository.apache.org/content/repositories/orgapacheignite-1463/
> > > > > >
> > > > > >
> > > > > >
> > > > > > This is half-release before 2.8 containing Java 11 support and
> > fixes
> > > > for
> > > > > > Native Persistence storage.
> > > > > >
> > > > > > Tag name is 2.7.5-rc4:
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc4
> > > > > >
> > > > > > 2.7.5 changes:
> > > > > >
> > > > > > * Added Java 11 support
> > > > > >
> > > > > > * Fixed infinite looping during SSL handshake, affecting Java
> > > > 11/Windows
> > > > > >
> > > > > > * Fixed storage corruption case after incorrectly rotated page
> > > > > >
> > > > > > * Erroneous WAL record after incorrectly rotated page processed
> > > > > > automatically
> > > > > >
> > > > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java
> > 11
> > > > > >
> > > > > > * Launch scripts and some Ignite initialization steps were fixed
> > for
> > > > Java
> > > > > > 12
> > > > > >
> > > > > > * Fixed indexes corruption on node stop under load
> > > > > >
> > > > > > * Fixed case of node crash during node deactivation
> > > > > >
> > > > > > * Error message with advice about required JVM parameters printed
> > when
> > > > Java
> > > > > > 9+ is used
> > > > > >
> > > > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > > > >
> > > > > >
> > > > > >
> > > > > > Complete list of closed issues:
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
> > > > > >
> > > > > > DEVNOTES
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > > > > >
> > > > > > RELEASE NOTES
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
> > > > > >
> > > > > > The vote is formal, see voting guidelines
> > > > > > https://www.apache.org/foundation/voting.html
> > > > > >
> > > > > > +1 - to accept Apache Ignite 2.7.5-rc4
> > > > > >
> > > > > > 0 - don't care either way
> > > > > >
> > > > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc4 (explain why)
> > > > > >
> > > > > >
> > > > > >
> > > > > > See notes on how to verify release here
> > > > > >
> > > > > > https://www.apache.org/info/verification.html
> > > > > >
> > > > > > and
> > > > > >
> > > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-ReleaseVerification
> > > > > >
> > > > > > This vote will be open for at least 72 hours till June 7, 18:00
> > UTC.
> > > > > >
> > > > > >
> > > >
> >
> https://www.timeanddate.com/countdown/to?year=2019&month=6&day=7&hour=18&min=0&sec=0&p0=utc-1
> > > > > >
> > > > > >
> > > > > >
> > > > > > Best Regards,
> > > > > >
> > > > > > Dmitriy Pavlov
> > > > > >
> > > >
> >
>
Re: [VOTE] Release Apache Ignite 2.7.5-rc4
+1 (binding) - checked build from source, persistence example and basic
control.sh commands.
ср, 5 июн. 2019 г. в 17:48, Andrey Gura :
> +1 (binding)
>
> On Wed, Jun 5, 2019 at 4:39 PM Ilya Kasnacheev
> wrote:
> >
> > +1
> >
> > Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL
> Cluster
> > on Java 11 and Java 8 without tuning any flags.
> > --
> > Ilya Kasnacheev
> >
> >
> > ср, 5 июн. 2019 г. в 09:44, Nikolay Izhikov :
> >
> > > +1 (binding)
> > >
> > > В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> > > > +1 (binding)
> > > >
> > > > Nice to have clusters nodes started with ignite.sh in my JVM 11
> > > environment
> > > > without any settings.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov
> > > wrote:
> > > >
> > > > > Dear Community,
> > > > >
> > > > >
> > > > >
> > > > > We have uploaded release candidate to
> > > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc4/
> > > > >
> > > > >
> > > > >
> > > > > The following staging can be used for a dependent project for
> testing:
> > > > >
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapacheignite-1463/
> > > > >
> > > > >
> > > > >
> > > > > This is half-release before 2.8 containing Java 11 support and
> fixes
> > > for
> > > > > Native Persistence storage.
> > > > >
> > > > > Tag name is 2.7.5-rc4:
> > > > >
> > > > >
> > > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc4
> > > > >
> > > > > 2.7.5 changes:
> > > > >
> > > > > * Added Java 11 support
> > > > >
> > > > > * Fixed infinite looping during SSL handshake, affecting Java
> > > 11/Windows
> > > > >
> > > > > * Fixed storage corruption case after incorrectly rotated page
> > > > >
> > > > > * Erroneous WAL record after incorrectly rotated page processed
> > > > > automatically
> > > > >
> > > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java
> 11
> > > > >
> > > > > * Launch scripts and some Ignite initialization steps were fixed
> for
> > > Java
> > > > > 12
> > > > >
> > > > > * Fixed indexes corruption on node stop under load
> > > > >
> > > > > * Fixed case of node crash during node deactivation
> > > > >
> > > > > * Error message with advice about required JVM parameters printed
> when
> > > Java
> > > > > 9+ is used
> > > > >
> > > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > > >
> > > > >
> > > > >
> > > > > Complete list of closed issues:
> > > > >
> > > > >
> > > > >
> > >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
> > > > >
> > > > > DEVNOTES
> > > > >
> > > > >
> > > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > > > >
> > > > > RELEASE NOTES
> > > > >
> > > > >
> > > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
> > > > >
> > > > > The vote is formal, see voting guidelines
> > > > > https://www.apache.org/foundation/voting.html
> > > > >
> > > > > +1 - to accept Apache Ignite 2.7.5-rc4
> > > > >
> > > > > 0 - don't care either way
> > > > >
> > > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc4 (explain why)
> > > > >
> > > > >
> > > > >
> > > > > See notes on how to verify release here
> > > > >
> > > > > https://www.apache.org/info/verification.html
> > > > >
> > > > > and
> > > > >
> > > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-ReleaseVerification
> > > > >
> > > > > This vote will be open for at least 72 hours till June 7, 18:00
> UTC.
> > > > >
> > > > >
> > >
> https://www.timeanddate.com/countdown/to?year=2019&month=6&day=7&hour=18&min=0&sec=0&p0=utc-1
> > > > >
> > > > >
> > > > >
> > > > > Best Regards,
> > > > >
> > > > > Dmitriy Pavlov
> > > > >
> > >
>
Re: Ignite stops working suddenly during dev
Hello Denis, As for p.1 - fully agree. For p.2 - I have some ideas to be implemented in the future in Ignite 3.0, will share some ideas later. чт, 6 июн. 2019 г. в 13:29, Denis Magda : > Hey Igniters, > > I'd like us to brainstorm how to solve the following usability issue. > > A user starts developing an app and can change the data model via a > configuration or DDL frequently. However, if there is an incompatible data > model change like a type/field modification Ignite will fail to restart or > begins throwing "wrong data type" exceptions. > > A solution for these scenarios is to clean the "marshaller/" folder. Guess > who knows this trick? A few of us. Had to do this all the time while baking > a demo for one of the recent shows and here is a good example of users' > hardships: > > https://stackoverflow.com/questions/56384773/apache-ignite-programmatically-destroy-persistent-cache > > How do you see this needs to be addressed considering: > >1. Current Ignite serialization format - a special message that explains >what to clean and where or some sort of automation? >2. Future storage independent format - when binary serialization logic >will be revisited. @Alex Goncharuk, please step in. > > > - > Denis >
Re: [TC] Examples suite issues
Success run was on java8 [1], failed on java9 [1] https://ci.ignite.apache.org/viewLog.html?buildId=4054730&buildTypeId=IgniteTests24Java8_Examples&tab=buildLog&branch_IgniteTests24Java8=%3Cdefault%3E&_focus=1512#_state=1503 [2] https://ci.ignite.apache.org/viewLog.html?buildId=4053973&buildTypeId=IgniteTests24Java8_Examples&tab=buildLog&_focus=1628 В Чт, 06/06/2019 в 15:23 +0300, Nikolay Izhikov пишет: > Petr, Ivan. > > > Is IgniteExamplesSparkSelfTestSuite running on TC today? > > Yes. > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3622497482827788237&tab=testDetails > > But test is flacky. > > I'm almost sure, the TC settings differs in different builds. > Petr, can you check it? > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > > Exception means, there is no scala classes on classpath. > > ``` > java.lang.NoClassDefFoundError: scala/App$class > at > org.apache.ignite.spark.examples.IgniteDataFrameSelfTest.testDataFrameWriteExample(IgniteDataFrameSelfTest.java:52) > Caused by: java.lang.ClassNotFoundException: scala.App$class > > > > В Чт, 06/06/2019 в 15:06 +0300, Павлухин Иван пишет: > > Nikolay, > > > > Just to finish the story. Is IgniteExamplesSparkSelfTestSuite running > > on TC today? > > > > чт, 6 июн. 2019 г. в 15:00, Nikolay Izhikov : > > > > > > Petr. > > > > > > Scala profile already exists in ignite-examples. > > > But is wan't used in "Build Ignite" > > > > > > https://github.com/apache/ignite/blob/master/examples/pom.xml#L174 > > > > > > В Чт, 06/06/2019 в 14:56 +0300, Petr Ivanov пишет: > > > > Still cannot find addition of `scala` profile in that PR. > > > > > > > > Am I missing something? > > > > > > > > > On 5 Jun 2019, at 15:10, Maxim Muzafarov wrote: > > > > > > > > > > Folks, > > > > > > > > > > I've checked PR [1] and it seems to me it fixes the main issue with a > > > > > spark examples. > > > > > After adding `scala` profile the [Example] Suite in the master branch > > > > > starts to fail - [2] and it works fine in the PR branch [3] (Javadocs > > > > > also compiles). > > > > > > > > > > Not sure, but adding this profile also fixes the [Check Code Style] > > > > > Suite too which is failing [4] in the master branch on compile > > > > > `ignite-scalar` module. I will investigate it more shortly. > > > > > > > > > > [1] https://github.com/apache/ignite/pull/6587 > > > > > [2] > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > > > > > [3] > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=pull%2F6587%2Fhead&tab=buildTypeStatusDiv > > > > > [4] > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4046113&buildTypeId=IgniteTests24Java8_CheckCodeStyle > > > > > > > > > > > > > > > On Wed, 5 Jun 2019 at 12:35, Petr Ivanov wrote: > > > > > > > > > > > > I've added 'scala' profile to ~Build Apache Ignite~. > > > > > > Can you check please that everything is OK now? > > > > > > > > > > > > > On 5 Jun 2019, at 12:16, Nikolay Izhikov > > > > > > > wrote: > > > > > > > > > > > > > > Petr. > > > > > > > > > > > > > > Current PR solves the following issue: "Data Frame examples > > > > > > > crashes in master". > > > > > > > > > > > > > > We need to solve one more issue: > > > > > > > > > > > > > > "Data Frame examples not tested on TC" - this require "scala" > > > > > > > profile in "Build Ignite" suite. > > > > > > > > > > > > > > > > > > > > > В Ср, 05/06/2019 в 12:05 +0300, Petr Ivanov пишет: > > > > > > > > > On 5 Jun 2019, at 11:49, Nikolay Izhikov > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > > > > > > > > > > > > Because this change fix the issue described in the ticket [1] > > > > > > > > > > > > > > > > So changes in intermediate commits were reverted in branch? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Can you describe the problem once more, please? Is it > > > > > > > > > > about > > > > > > > > > > > > > > > > > > :ignite-examples module not being build in ~Build Apache > > > > > > > > > Ignite~ ? > > > > > > > > > > > > > > > > > > Spark examples activated only if `scala` profile enabled. > > > > > > > > > There is no `scala` profile in "~Build Apache Ignite~", only > > > > > > > > > `all-scala`. > > > > > > > > > > > > > > > > Let's add 'scala' profile into build. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11881 > > > > > > > > > > > > > > > > > > ср, 5 июн. 2019 г. в 10:59, Petr Ivanov : > > > > > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > >
Re: [TC] Examples suite issues
Petr, Ivan. > Is IgniteExamplesSparkSelfTestSuite running on TC today? Yes. https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3622497482827788237&tab=testDetails But test is flacky. I'm almost sure, the TC settings differs in different builds. Petr, can you check it? https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv Exception means, there is no scala classes on classpath. ``` java.lang.NoClassDefFoundError: scala/App$class at org.apache.ignite.spark.examples.IgniteDataFrameSelfTest.testDataFrameWriteExample(IgniteDataFrameSelfTest.java:52) Caused by: java.lang.ClassNotFoundException: scala.App$class В Чт, 06/06/2019 в 15:06 +0300, Павлухин Иван пишет: > Nikolay, > > Just to finish the story. Is IgniteExamplesSparkSelfTestSuite running > on TC today? > > чт, 6 июн. 2019 г. в 15:00, Nikolay Izhikov : > > > > Petr. > > > > Scala profile already exists in ignite-examples. > > But is wan't used in "Build Ignite" > > > > https://github.com/apache/ignite/blob/master/examples/pom.xml#L174 > > > > В Чт, 06/06/2019 в 14:56 +0300, Petr Ivanov пишет: > > > Still cannot find addition of `scala` profile in that PR. > > > > > > Am I missing something? > > > > > > > On 5 Jun 2019, at 15:10, Maxim Muzafarov wrote: > > > > > > > > Folks, > > > > > > > > I've checked PR [1] and it seems to me it fixes the main issue with a > > > > spark examples. > > > > After adding `scala` profile the [Example] Suite in the master branch > > > > starts to fail - [2] and it works fine in the PR branch [3] (Javadocs > > > > also compiles). > > > > > > > > Not sure, but adding this profile also fixes the [Check Code Style] > > > > Suite too which is failing [4] in the master branch on compile > > > > `ignite-scalar` module. I will investigate it more shortly. > > > > > > > > [1] https://github.com/apache/ignite/pull/6587 > > > > [2] > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > > > > [3] > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=pull%2F6587%2Fhead&tab=buildTypeStatusDiv > > > > [4] > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4046113&buildTypeId=IgniteTests24Java8_CheckCodeStyle > > > > > > > > > > > > On Wed, 5 Jun 2019 at 12:35, Petr Ivanov wrote: > > > > > > > > > > I've added 'scala' profile to ~Build Apache Ignite~. > > > > > Can you check please that everything is OK now? > > > > > > > > > > > On 5 Jun 2019, at 12:16, Nikolay Izhikov > > > > > > wrote: > > > > > > > > > > > > Petr. > > > > > > > > > > > > Current PR solves the following issue: "Data Frame examples crashes > > > > > > in master". > > > > > > > > > > > > We need to solve one more issue: > > > > > > > > > > > > "Data Frame examples not tested on TC" - this require "scala" > > > > > > profile in "Build Ignite" suite. > > > > > > > > > > > > > > > > > > В Ср, 05/06/2019 в 12:05 +0300, Petr Ivanov пишет: > > > > > > > > On 5 Jun 2019, at 11:49, Nikolay Izhikov > > > > > > > > wrote: > > > > > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > > > > > > > > > > Because this change fix the issue described in the ticket [1] > > > > > > > > > > > > > > So changes in intermediate commits were reverted in branch? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Can you describe the problem once more, please? Is it about > > > > > > > > > > > > > > > > :ignite-examples module not being build in ~Build Apache > > > > > > > > Ignite~ ? > > > > > > > > > > > > > > > > Spark examples activated only if `scala` profile enabled. > > > > > > > > There is no `scala` profile in "~Build Apache Ignite~", only > > > > > > > > `all-scala`. > > > > > > > > > > > > > > Let's add 'scala' profile into build. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11881 > > > > > > > > > > > > > > > > ср, 5 июн. 2019 г. в 10:59, Petr Ivanov : > > > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > > > 2. Can you describe the problem once more, please? Is it about > > > > > > > > > :ignite-examples module not being build in ~Build Apache > > > > > > > > > Ignite~ ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 4 Jun 2019, at 20:34, Nikolay Izhikov > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > > > Root of the issue is in our maven profiles hierarchy. > > > > > > > > > > > > > > > > > > > > "Build Ignite" suite on TC activate 'all-scala' and > > > > > > >
Re: [TC] Examples suite issues
Nikolay, Just to finish the story. Is IgniteExamplesSparkSelfTestSuite running on TC today? чт, 6 июн. 2019 г. в 15:00, Nikolay Izhikov : > > Petr. > > Scala profile already exists in ignite-examples. > But is wan't used in "Build Ignite" > > https://github.com/apache/ignite/blob/master/examples/pom.xml#L174 > > В Чт, 06/06/2019 в 14:56 +0300, Petr Ivanov пишет: > > Still cannot find addition of `scala` profile in that PR. > > > > Am I missing something? > > > > > On 5 Jun 2019, at 15:10, Maxim Muzafarov wrote: > > > > > > Folks, > > > > > > I've checked PR [1] and it seems to me it fixes the main issue with a > > > spark examples. > > > After adding `scala` profile the [Example] Suite in the master branch > > > starts to fail - [2] and it works fine in the PR branch [3] (Javadocs > > > also compiles). > > > > > > Not sure, but adding this profile also fixes the [Check Code Style] > > > Suite too which is failing [4] in the master branch on compile > > > `ignite-scalar` module. I will investigate it more shortly. > > > > > > [1] https://github.com/apache/ignite/pull/6587 > > > [2] > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > > > [3] > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=pull%2F6587%2Fhead&tab=buildTypeStatusDiv > > > [4] > > > https://ci.ignite.apache.org/viewLog.html?buildId=4046113&buildTypeId=IgniteTests24Java8_CheckCodeStyle > > > > > > > > > On Wed, 5 Jun 2019 at 12:35, Petr Ivanov wrote: > > > > > > > > I've added 'scala' profile to ~Build Apache Ignite~. > > > > Can you check please that everything is OK now? > > > > > > > > > On 5 Jun 2019, at 12:16, Nikolay Izhikov wrote: > > > > > > > > > > Petr. > > > > > > > > > > Current PR solves the following issue: "Data Frame examples crashes > > > > > in master". > > > > > > > > > > We need to solve one more issue: > > > > > > > > > > "Data Frame examples not tested on TC" - this require "scala" profile > > > > > in "Build Ignite" suite. > > > > > > > > > > > > > > > В Ср, 05/06/2019 в 12:05 +0300, Petr Ivanov пишет: > > > > > > > On 5 Jun 2019, at 11:49, Nikolay Izhikov > > > > > > > wrote: > > > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > > > > > > > > Because this change fix the issue described in the ticket [1] > > > > > > > > > > > > So changes in intermediate commits were reverted in branch? > > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Can you describe the problem once more, please? Is it about > > > > > > > > > > > > > > :ignite-examples module not being build in ~Build Apache Ignite~ ? > > > > > > > > > > > > > > Spark examples activated only if `scala` profile enabled. > > > > > > > There is no `scala` profile in "~Build Apache Ignite~", only > > > > > > > `all-scala`. > > > > > > > > > > > > Let's add 'scala' profile into build. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11881 > > > > > > > > > > > > > > ср, 5 июн. 2019 г. в 10:59, Petr Ivanov : > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > > 2. Can you describe the problem once more, please? Is it about > > > > > > > > :ignite-examples module not being build in ~Build Apache > > > > > > > > Ignite~ ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 4 Jun 2019, at 20:34, Nikolay Izhikov > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > > > Root of the issue is in our maven profiles hierarchy. > > > > > > > > > > > > > > > > > > "Build Ignite" suite on TC activate 'all-scala' and examples > > > > > > > > > module have > > > > > > > > > > > > > > > > only 'scala' profile. > > > > > > > > > To reduce copy-pase I added 'scala' profile of examples module > > > > > > > > > > > > > > > > activation based on system property 'scala-examples'. > > > > > > > > > > > > > > > > > > So, for now my PR [1] fixes both issues with examples module: > > > > > > > > > > > > > > > > > > 1. Unnecessary dependecies that leads to Spark examples crash. > > > > > > > > > 2. Spark examples not tested on TC. > > > > > > > > > > > > > > > > > > After merge of PR [1] we should add this property to "Build > > > > > > > > > Ignite" > > > > > > > > > > > > > > > > suite. > > > > > > > > > > > > > > > > > > Is there any objections? > > > > > > > > > > > > > > > > > > [1] https://github.com/apache/ignite/pull/6587 > > > > > > > > > > > > > > > > > > [2] > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4041670&buildTypeId=IgniteTests24Java8_Examples&tab=testsInfo&branch_IgniteTests24Java8=pull%2F6587%2Fhead > > > > > > > > > > > > > > > > > > > > > > > > > > > В Вт, 04/06/2019
Re: [TC] Examples suite issues
Petr. Scala profile already exists in ignite-examples. But is wan't used in "Build Ignite" https://github.com/apache/ignite/blob/master/examples/pom.xml#L174 В Чт, 06/06/2019 в 14:56 +0300, Petr Ivanov пишет: > Still cannot find addition of `scala` profile in that PR. > > Am I missing something? > > > On 5 Jun 2019, at 15:10, Maxim Muzafarov wrote: > > > > Folks, > > > > I've checked PR [1] and it seems to me it fixes the main issue with a > > spark examples. > > After adding `scala` profile the [Example] Suite in the master branch > > starts to fail - [2] and it works fine in the PR branch [3] (Javadocs > > also compiles). > > > > Not sure, but adding this profile also fixes the [Check Code Style] > > Suite too which is failing [4] in the master branch on compile > > `ignite-scalar` module. I will investigate it more shortly. > > > > [1] https://github.com/apache/ignite/pull/6587 > > [2] > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > > [3] > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=pull%2F6587%2Fhead&tab=buildTypeStatusDiv > > [4] > > https://ci.ignite.apache.org/viewLog.html?buildId=4046113&buildTypeId=IgniteTests24Java8_CheckCodeStyle > > > > > > On Wed, 5 Jun 2019 at 12:35, Petr Ivanov wrote: > > > > > > I've added 'scala' profile to ~Build Apache Ignite~. > > > Can you check please that everything is OK now? > > > > > > > On 5 Jun 2019, at 12:16, Nikolay Izhikov wrote: > > > > > > > > Petr. > > > > > > > > Current PR solves the following issue: "Data Frame examples crashes in > > > > master". > > > > > > > > We need to solve one more issue: > > > > > > > > "Data Frame examples not tested on TC" - this require "scala" profile > > > > in "Build Ignite" suite. > > > > > > > > > > > > В Ср, 05/06/2019 в 12:05 +0300, Petr Ivanov пишет: > > > > > > On 5 Jun 2019, at 11:49, Nikolay Izhikov > > > > > > wrote: > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > > > > > > Because this change fix the issue described in the ticket [1] > > > > > > > > > > So changes in intermediate commits were reverted in branch? > > > > > > > > > > > > > > > > > > > > > > > 2. Can you describe the problem once more, please? Is it about > > > > > > > > > > > > :ignite-examples module not being build in ~Build Apache Ignite~ ? > > > > > > > > > > > > Spark examples activated only if `scala` profile enabled. > > > > > > There is no `scala` profile in "~Build Apache Ignite~", only > > > > > > `all-scala`. > > > > > > > > > > Let's add 'scala' profile into build. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11881 > > > > > > > > > > > > ср, 5 июн. 2019 г. в 10:59, Petr Ivanov : > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > 1. Why does your PR show only single file changed? > > > > > > > 2. Can you describe the problem once more, please? Is it about > > > > > > > :ignite-examples module not being build in ~Build Apache Ignite~ ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 4 Jun 2019, at 20:34, Nikolay Izhikov > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > Root of the issue is in our maven profiles hierarchy. > > > > > > > > > > > > > > > > "Build Ignite" suite on TC activate 'all-scala' and examples > > > > > > > > module have > > > > > > > > > > > > > > only 'scala' profile. > > > > > > > > To reduce copy-pase I added 'scala' profile of examples module > > > > > > > > > > > > > > activation based on system property 'scala-examples'. > > > > > > > > > > > > > > > > So, for now my PR [1] fixes both issues with examples module: > > > > > > > > > > > > > > > > 1. Unnecessary dependecies that leads to Spark examples crash. > > > > > > > > 2. Spark examples not tested on TC. > > > > > > > > > > > > > > > > After merge of PR [1] we should add this property to "Build > > > > > > > > Ignite" > > > > > > > > > > > > > > suite. > > > > > > > > > > > > > > > > Is there any objections? > > > > > > > > > > > > > > > > [1] https://github.com/apache/ignite/pull/6587 > > > > > > > > > > > > > > > > [2] > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4041670&buildTypeId=IgniteTests24Java8_Examples&tab=testsInfo&branch_IgniteTests24Java8=pull%2F6587%2Fhead > > > > > > > > > > > > > > > > > > > > > > > > В Вт, 04/06/2019 в 16:56 +0300, Nikolay Izhikov пишет: > > > > > > > > > I moved jackson dependencies to maven-javadoc-plugin > > > > > > > > > additional > > > > > > > > > > > > > > dependencies. > > > > > > > > > Seems, it solves both issues: Data Frame examples and javadoc > > > > > > > > > > > > > > generation. > > > > > > > > > > > > > > > > > > But, Data Frame e
Re: [TC] Examples suite issues
Still cannot find addition of `scala` profile in that PR. Am I missing something? > On 5 Jun 2019, at 15:10, Maxim Muzafarov wrote: > > Folks, > > I've checked PR [1] and it seems to me it fixes the main issue with a > spark examples. > After adding `scala` profile the [Example] Suite in the master branch > starts to fail - [2] and it works fine in the PR branch [3] (Javadocs > also compiles). > > Not sure, but adding this profile also fixes the [Check Code Style] > Suite too which is failing [4] in the master branch on compile > `ignite-scalar` module. I will investigate it more shortly. > > [1] https://github.com/apache/ignite/pull/6587 > [2] > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > [3] > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples&branch_IgniteTests24Java8=pull%2F6587%2Fhead&tab=buildTypeStatusDiv > [4] > https://ci.ignite.apache.org/viewLog.html?buildId=4046113&buildTypeId=IgniteTests24Java8_CheckCodeStyle > > > On Wed, 5 Jun 2019 at 12:35, Petr Ivanov wrote: >> >> I've added 'scala' profile to ~Build Apache Ignite~. >> Can you check please that everything is OK now? >> >>> On 5 Jun 2019, at 12:16, Nikolay Izhikov wrote: >>> >>> Petr. >>> >>> Current PR solves the following issue: "Data Frame examples crashes in >>> master". >>> >>> We need to solve one more issue: >>> >>> "Data Frame examples not tested on TC" - this require "scala" profile in >>> "Build Ignite" suite. >>> >>> >>> В Ср, 05/06/2019 в 12:05 +0300, Petr Ivanov пишет: > On 5 Jun 2019, at 11:49, Nikolay Izhikov wrote: > >> 1. Why does your PR show only single file changed? > > Because this change fix the issue described in the ticket [1] So changes in intermediate commits were reverted in branch? > >> 2. Can you describe the problem once more, please? Is it about > > :ignite-examples module not being build in ~Build Apache Ignite~ ? > > Spark examples activated only if `scala` profile enabled. > There is no `scala` profile in "~Build Apache Ignite~", only `all-scala`. Let's add 'scala' profile into build. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11881 > > ср, 5 июн. 2019 г. в 10:59, Petr Ivanov : > >> Nikolay, >> >> >> 1. Why does your PR show only single file changed? >> 2. Can you describe the problem once more, please? Is it about >> :ignite-examples module not being build in ~Build Apache Ignite~ ? >> >> >> >>> On 4 Jun 2019, at 20:34, Nikolay Izhikov wrote: >>> >>> Hello, Igniters. >>> >>> Root of the issue is in our maven profiles hierarchy. >>> >>> "Build Ignite" suite on TC activate 'all-scala' and examples module have >> >> only 'scala' profile. >>> To reduce copy-pase I added 'scala' profile of examples module >> >> activation based on system property 'scala-examples'. >>> >>> So, for now my PR [1] fixes both issues with examples module: >>> >>> 1. Unnecessary dependecies that leads to Spark examples crash. >>> 2. Spark examples not tested on TC. >>> >>> After merge of PR [1] we should add this property to "Build Ignite" >> >> suite. >>> >>> Is there any objections? >>> >>> [1] https://github.com/apache/ignite/pull/6587 >>> >>> [2] >> >> https://ci.ignite.apache.org/viewLog.html?buildId=4041670&buildTypeId=IgniteTests24Java8_Examples&tab=testsInfo&branch_IgniteTests24Java8=pull%2F6587%2Fhead >>> >>> >>> В Вт, 04/06/2019 в 16:56 +0300, Nikolay Izhikov пишет: I moved jackson dependencies to maven-javadoc-plugin additional >> >> dependencies. Seems, it solves both issues: Data Frame examples and javadoc >> >> generation. But, Data Frame examples still doesn't shows in tc log. Will investigate it, shortly. >> >> https://ci.ignite.apache.org/viewLog.html?buildId=4039945&tab=queuedBuildOverviewTab https://ci.ignite.apache.org/viewLog.html?buildId=4039943& В Вт, 04/06/2019 в 15:45 +0300, Павлухин Иван пишет: > Would be great if it is possible. > > вт, 4 июн. 2019 г. в 15:43, Nikolay Izhikov : >> >> I used to think it's forbidden to use direct version in pom.xml. >> We should keep all versions in parent pom. >> >> >> В Вт, 04/06/2019 в 15:36 +0300, Павлухин Иван пишет: >>> Nikolay, >>> >>> It was already observed that removal of jackson dependencies from >>> examples module would lead to a Javadoc build job failure (for >>> examples module). One way to fix it is changing jackson depen
Re: Hello
Hi, thank you for interest in Apache Ignite and welcome to Apache Ignite Community. Let me share a short guide on how to start contributing https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite Once you will find a ticket you would like to start with, please share your JIRA ID, and someone from PMC will add you to the contributors' list. Sincerely Dmitriy Pavlov чт, 6 июн. 2019 г. в 14:27, : > "Hello" to everyone in the community > I'd like to try myself as Apache Ignite contributor > > Thanks >
Hello
"Hello" to everyone in the community I'd like to try myself as Apache Ignite contributor Thanks
[jira] [Created] (IGNITE-11898) Java Thin: Implement Best Effort Affinity
Aleksey Plekhanov created IGNITE-11898: -- Summary: Java Thin: Implement Best Effort Affinity Key: IGNITE-11898 URL: https://issues.apache.org/jira/browse/IGNITE-11898 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov See linked IEP-23. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Ignite stops working suddenly during dev
Hey Igniters, I'd like us to brainstorm how to solve the following usability issue. A user starts developing an app and can change the data model via a configuration or DDL frequently. However, if there is an incompatible data model change like a type/field modification Ignite will fail to restart or begins throwing "wrong data type" exceptions. A solution for these scenarios is to clean the "marshaller/" folder. Guess who knows this trick? A few of us. Had to do this all the time while baking a demo for one of the recent shows and here is a good example of users' hardships: https://stackoverflow.com/questions/56384773/apache-ignite-programmatically-destroy-persistent-cache How do you see this needs to be addressed considering: 1. Current Ignite serialization format - a special message that explains what to clean and where or some sort of automation? 2. Future storage independent format - when binary serialization logic will be revisited. @Alex Goncharuk, please step in. - Denis
[MTCGA]: new failures in builds [4051276] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Platform .NET (Core Linux) https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformNetCoreLinux&branch=%3Cdefault%3E&tab=buildTypeStatusDiv Changes may lead to failure were done by - nizhi...@apache.org https://ci.ignite.apache.org/viewModification.html?modId=886045 - kaa@yandex.ru https://ci.ignite.apache.org/viewModification.html?modId=886056 - vane...@gmail.com https://ci.ignite.apache.org/viewModification.html?modId=885991 - vsi...@gridgain.com https://ci.ignite.apache.org/viewModification.html?modId=886032 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 10:38:20 06-06-2019
