Re: Apache Ignite 2.7 release

[Nikolay Izhikov]

Hello, Pavel.

IGNITE-6055 merged to master.

Please, update your code accordingly.
You can take edits in CPP, .Net, NodeJS thin clients as example.

В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> PR is fully ready.
> 
> I'm waiting final approve from Vladimir Ozerov.
> 
> Hope, This will be merged in master on Monday :).
> 
> В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> > Hi Nikolay,
> > 
> > Thank you for the heads up. The dependency should be resolved before the 
> > clients are merged to master, so the sooner you merge the PR the better.
> > 
> > p.
> > 
> > On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov  
> > wrote:
> > > Hello, Pavel.
> > > 
> > > Please, be aware of IGNITE-6055 [1]
> > > 
> > > I'm edit thin protocol in that ticket.
> > > I can't support changes in Python and PHP clients, because, they are not 
> > > merged in master, yet.
> > > Write me, If you have any questions about new fields.
> > > 
> > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > 
> > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > Hi Nikolay,
> > > > 
> > > > Python [1], PHP [2], and Node.js [3] thin clients will get into the 
> > > > release.
> > > > 
> > > > Thanks,
> > > > p.
> > > > 
> > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782
> > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783
> > > > [3] https://jira.apache.org/jira/browse/IGNITE-
> > > > 
> > > > 
> > > > On Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan 
> > > >  wrote:
> > > > > Thanks, Nikolay!
> > > > > 
> > > > > I think it is important to include the links to all important Jira 
> > > > > tickets
> > > > > in this thread, so that the community can track them.
> > > > > 
> > > > > D.
> > > > > 
> > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov 
> > > > > 
> > > > > wrote:
> > > > > 
> > > > > > Hello, Dmitriy.
> > > > > > 
> > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > > 
> > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > Hi Nikolay,
> > > > > > > 
> > > > > > > Thanks for being the release manager!
> > > > > > > 
> > > > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > > > high-level tickets, that are not plain bug fixes, which will be
> > > > > > 
> > > > > > interesting
> > > > > > > for the community to notice?
> > > > > > > 
> > > > > > > For example, here are some significant tasks that the community 
> > > > > > > is either
> > > > > > > working on or has been working on:
> > > > > > > 
> > > > > > > - Node.JS client
> > > > > > > - Python client
> > > > > > > - Transactional SQL (MVCC)
> > > > > > > - service grid stabilization
> > > > > > > - SQL memory utilization improvements
> > > > > > > - more?
> > > > > > > 
> > > > > > > Can you please solicit status from the community for these tasks?
> > > > > > > 
> > > > > > > D.
> > > > > > > 
> > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov 
> > > > > > > 
> > > > > > > wrote:
> > > > > > > 
> > > > > > > > Hello, Igniters.
> > > > > > > > 
> > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > 
> > > > > > > > It's time to start discussion of release. [1]
> > > > > > > > 
> > > > > > > > Current code freeze date is September, 30.
> > > > > > > > If you have any objections - please, responsd to this thread.
> > > > > > > > 
> > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > 
> > > > > > Apache+Ignite+2.7
> > > > > > 
> > > > 
> > > > 

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

[GitHub] ignite pull request #3973: IGNITE-6055: SQL: Add String length constraint

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Apache Ignite 2.7 release

[Pavel Petroshenko]

Thank you, Nikolay. Will do.

p.

On Tue, Aug 28, 2018 at 12:05 AM, Nikolay Izhikov 
wrote:

> Hello, Pavel.
>
> IGNITE-6055 merged to master.
>
> Please, update your code accordingly.
> You can take edits in CPP, .Net, NodeJS thin clients as example.
>
> В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> > PR is fully ready.
> >
> > I'm waiting final approve from Vladimir Ozerov.
> >
> > Hope, This will be merged in master on Monday :).
> >
> > В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> > > Hi Nikolay,
> > >
> > > Thank you for the heads up. The dependency should be resolved before
> the clients are merged to master, so the sooner you merge the PR the better.
> > >
> > > p.
> > >
> > > On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov 
> wrote:
> > > > Hello, Pavel.
> > > >
> > > > Please, be aware of IGNITE-6055 [1]
> > > >
> > > > I'm edit thin protocol in that ticket.
> > > > I can't support changes in Python and PHP clients, because, they are
> not merged in master, yet.
> > > > Write me, If you have any questions about new fields.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > >
> > > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > > Hi Nikolay,
> > > > >
> > > > > Python [1], PHP [2], and Node.js [3] thin clients will get into
> the release.
> > > > >
> > > > > Thanks,
> > > > > p.
> > > > >
> > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782
> > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783
> > > > > [3] https://jira.apache.org/jira/browse/IGNITE-
> > > > >
> > > > >
> > > > > On Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org> wrote:
> > > > > > Thanks, Nikolay!
> > > > > >
> > > > > > I think it is important to include the links to all important
> Jira tickets
> > > > > > in this thread, so that the community can track them.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> nizhi...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, Dmitriy.
> > > > > > >
> > > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > > >
> > > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > > Hi Nikolay,
> > > > > > > >
> > > > > > > > Thanks for being the release manager!
> > > > > > > >
> > > > > > > > I am getting a bit lost in all these tickets. Can we specify
> some
> > > > > > > > high-level tickets, that are not plain bug fixes, which will
> be
> > > > > > >
> > > > > > > interesting
> > > > > > > > for the community to notice?
> > > > > > > >
> > > > > > > > For example, here are some significant tasks that the
> community is either
> > > > > > > > working on or has been working on:
> > > > > > > >
> > > > > > > > - Node.JS client
> > > > > > > > - Python client
> > > > > > > > - Transactional SQL (MVCC)
> > > > > > > > - service grid stabilization
> > > > > > > > - SQL memory utilization improvements
> > > > > > > > - more?
> > > > > > > >
> > > > > > > > Can you please solicit status from the community for these
> tasks?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> nizhi...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hello, Igniters.
> > > > > > > > >
> > > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > >
> > > > > > > > > It's time to start discussion of release. [1]
> > > > > > > > >
> > > > > > > > > Current code freeze date is September, 30.
> > > > > > > > > If you have any objections - please, responsd to this
> thread.
> > > > > > > > >
> > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > >
> > > > > > > Apache+Ignite+2.7
> > > > > > >
> > > > >
> > > > >
>

[GitHub] ignite pull request #4630: IGNITE-9319 added extra log when cache have been ...

[akalash]

GitHub user akalash opened a pull request:

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

IGNITE-9319 added extra log when cache have been empty



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

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

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

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

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

This closes #4630


commit 1a5d463cad20005d116a25a8c600f0fed15649e3
Author: Anton Kalashnikov 
Date:   2018-08-28T07:29:15Z

IGNITE-9319 added extra log when cache have been empty




---

[GitHub] ignite pull request #4610: IGNITE-9362 SQL: Remove NODES.IS_LOCAL attribute

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-9394) MVCC: pds corrupted after grid restart.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-9394:


 Summary: MVCC: pds corrupted after grid restart.
 Key: IGNITE-9394
 URL: https://issues.apache.org/jira/browse/IGNITE-9394
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Mashenkov


Ignite fails to apply unfinished checkpoint after restart.



java.lang.AssertionError: Assertion error on row: CacheObjectImpl [val=null, 
hasValBytes=true]CacheObjectImpl [val=null, hasValBytes=true], expireT
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2286)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.put(BPlusTree.java:2221)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.update(IgniteCacheOffheapManagerImpl.java:23
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.update(GridCacheOffheapManager.java:16
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.update(IgniteCacheOffheapManagerImpl.java:438)
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyUpdate(GridCacheDatabaseSharedManager.java:24
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.ja
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitio
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFutur
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.AssertionError
 at 
org.apache.ignite.internal.processors.cache.tree.AbstractDataLeafIO.storeByOffset(AbstractDataLeafIO.java:67)
 at 
org.apache.ignite.internal.processors.cache.tree.AbstractDataLeafIO.storeByOffset(AbstractDataLeafIO.java:35)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.store(BPlusIO.java:183)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.insert(BPlusIO.java:270)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertSimple(BPlusTree.java:3395)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:3377)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$2500(BPlusTree.java:3257)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:435)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:416)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5594)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5579)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:346)
 at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:276)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$12300(BPlusTree.java:87)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:3569)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7600(BPlusTree.java:3257)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2531)
 at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2250)
 ... 14 more



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

[jira] [Created] (IGNITE-9395) Incorrect link to javadoc

[Yury Gerzhedovich (JIRA)]

Yury Gerzhedovich created IGNITE-9395:
-

 Summary: Incorrect link to javadoc
 Key: IGNITE-9395
 URL: https://issues.apache.org/jira/browse/IGNITE-9395
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.6, 2.5
Reporter: Yury Gerzhedovich


Javadoc's links refer to 1.0.0 version of Ignite instead of latest one. 

For example at page [https://apacheignite.readme.io/docs/events]  there is link 
javadoc to [https://ignite.apache.org/releases/1.0.0/javadoc/] 

need to fix it to latest version of javadoc - 
[https://ignite.apache.org/releases/latest/javadoc/] 

Seems it issue for all other pages - need to recheck and fix it.



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

[GitHub] ignite pull request #4628: IGNITE-9393: Fixed bug in reduce function in data...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4621: IGNITE-9367 CPP: ODBC client crashes after execut...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4631: Ignite-8149-2-merged-tc

[pavlukhin]

GitHub user pavlukhin opened a pull request:

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

Ignite-8149-2-merged-tc

For Team City.

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

$ git pull https://github.com/gridgain/apache-ignite ignite-8149-2-merged-tc

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

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

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

This closes #4631


commit 6e7550574fac914bbd4f8c79eface578e2a032a6
Author: Igor Seliverstov 
Date:   2018-01-23T09:51:36Z

Merge branch 'master' into ignite-4191

# Conflicts:
#   
modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
#   modules/core/src/main/java/org/apache/ignite/internal/GridTopic.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheSharedContext.java
#   modules/core/src/main/java/org/apache/ignite/internal/sql/SqlParser.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

commit 033bbaa4a26f3cfc61a2a1d7bfa88adaeb8a234b
Author: Alexander Paschenko 
Date:   2018-01-23T11:56:23Z

Merge remote-tracking branch 'apache/master' into ignite-5571

# Conflicts:
#   
modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

commit b0699afff4677b06022970437fe65ecc955c6da4
Author: Alexander Paschenko 
Date:   2018-01-23T12:25:42Z

Merge remote-tracking branch 'origin/ignite-4191' into ignite-5571

# Conflicts:
#   
modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteClientCacheInitializationFailTest.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DmlStatementsProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/H2CachedStatementKey.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/ddl/DdlStatementsProcessor.java
#   
modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/DynamicIndexAbstractSelfTest.java
#   
modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/H2DynamicTableSelfTest.java

commit ae52faf5f5170a327282344a7fe03227eadedc53
Author: Alexander Paschenko 
Date:   2018-01-23T15:31:35Z

IGNITE-5571 Post-merge fix

commit 5b7d0a7e79342d07b122393b5725073fb0e9033e
Author: Alexander Paschenko 
Date:   2018-01-23T15:50:34Z

IGNITE-5571 Post-merge fix

commit d95939a55cb0e48824c02f998dbfc77a4ed1d3dc
Author: Igor Seliverstov 
Date:   2018-01-24T11:29:57Z

Merge branch 'master' into ignite-4191

commit 472d6d75e573094a3b31831678eaffbaca92aa29
Author: Igor Seliverstov 
Date:   2018-01-24T14:07:02Z

fix after merge

commit 9c1d20e5fc7ce721180b5da20600799905c6e229
Author: rkondakov 
Date:   2018-01-31T10:28:52Z

IGNITE-6353 Integrate mvcc support in scan query protocol

commit 8418d877a01547886125cc59aedbb2935c791ae4
Author: Igor Seliverstov 
Date:   2018-02-01T13:52:01Z

Merge branch 'master' into ignite-4191

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheDatabaseSharedManager.java

commit 7b19fa2c0c1aed0ccc4760aeb602c5ffedb72078
Author: Igor Seliverstov 
Date:   2018-02-01T16:52:19Z

Fix after merge

commit 6d7a729cf587d20b5e8efd50115ad9e0bb6da56c
Author: Igor Seliverstov 
Date:   2018-02-09T10:22:34Z

Merge branch 'master' into ignite-4191

# Conflicts:
#   
modules/clients/src/test/java/org/apache/ignite/jdbc/thin/JdbcThinConnectionSelfTest.java
#   
modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/ConnectionProperties.java
#   
modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/ConnectionPropertiesImpl.java
#   
modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcThinStatement.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheAffinitySharedManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java
#   
modules/core/src/main/java/org/apache/ignite/internal/sql/SqlKeyword.ja

[GitHub] ignite pull request #4632: IGNITE-9312 Remove unnecessary @SuppressWarnings ...

[ololo3000]

GitHub user ololo3000 opened a pull request:

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

IGNITE-9312 Remove unnecessary @SuppressWarnings annotation



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

$ git pull https://github.com/ololo3000/ignite IGNITE-9312

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

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

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

This closes #4632


commit 70a3af50aa3703d4a4ada443e0a4ac1634598517
Author: ololo3000 
Date:   2018-08-28T12:08:50Z

IGNITE-9312 Remove unnecessary @SuppressWarnings annotation




---

[jira] [Created] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml

[Stepan Pilschikov (JIRA)]

Stepan Pilschikov created IGNITE-9396:
-

 Summary: ML Examples: can't run examples, not enough dependencies 
in pom.xml
 Key: IGNITE-9396
 URL: https://issues.apache.org/jira/browse/IGNITE-9396
 Project: Ignite
  Issue Type: Bug
  Components: ml
Reporter: Stepan Pilschikov


Trying to run ml-examples and can't compile example project because several 
dependencies didn't added in pom.xml

Execution:
 Using JB IDEA Run->Run class to execute current class
 or 
 `java -classpath [all classpaths which are listed in pom file] class name`
 or compile with maven also failed
 `mvn clean compile`

Exception:
 Can't compile project. not enough dipendencies

Missing dependencies:
{code:xml}

com.github.fommil.netlib
core



org.springframework.data
spring-data-commons



org.springframework
spring-beans



org.springframework
spring-context



com.h2database
h2

{code}

com.github.fommil.netlib, springframework.* and h2 need to run - 
org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample



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

[jira] [Created] (IGNITE-9397) IgniteSqlDeleteBenchmark fails to run with java.util.NoSuchElementException

[Ivan Artukhov (JIRA)]

Ivan Artukhov created IGNITE-9397:
-

 Summary: IgniteSqlDeleteBenchmark fails to run with 
java.util.NoSuchElementException
 Key: IGNITE-9397
 URL: https://issues.apache.org/jira/browse/IGNITE-9397
 Project: Ignite
  Issue Type: Bug
  Components: yardstick
Affects Versions: 2.6
Reporter: Ivan Artukhov
 Attachments: r.properties

*Setup*
1 server and 1 client node
Attached the property file

*Steps*
Run 
{code}
$ bash bin/benchmark-run-all.sh config/r.properties
{code}

*Result*
An exception during warm-up:
{code}
Finishing main test [ts=1535464476907, date=Tue Aug 28 16:54:36 MSK 2018]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
java.util.NoSuchElementException
at java.util.AbstractQueue.remove(AbstractQueue.java:117)
at 
org.apache.ignite.yardstick.cache.dml.IgniteSqlDeleteBenchmark.test(IgniteSqlDeleteBenchmark.java:73)
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)
at java.lang.Thread.run(Thread.java:748)
{code}



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

Ignite new contributor

[Ravil Galeyev]

Hi Team,

I'd like to join to Apache Ignite development.
Especially to the ML part.
Currently, I work on IGNITE-9285

and I'm going to continue work with subtasks from IGNITE-9281
 (ML starter tasks).

My Jira login is rgaleyev

Best regards,
Ravil

[jira] [Created] (IGNITE-9398) Reduce time on processing CustomDiscoveryMessage by discovery worker

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-9398:
---

 Summary: Reduce time on processing CustomDiscoveryMessage by 
discovery worker
 Key: IGNITE-9398
 URL: https://issues.apache.org/jira/browse/IGNITE-9398
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.6, 2.5, 2.4
Reporter: Pavel Kovalenko
 Fix For: 2.7


Processing discovery CustomMessage may take significant values of time (0.5-0.7 
seconds) before sending to next node in the topology. This significantly 
accumulates the total time of PME if topology has multiple nodes.
Let X = time of processing discovery message by discovery-msg-worker on each 
node before sending to next node. 
Let N = number of nodes in the topology.
Then the minimal total time of exchange will be:
T = N * X

We shouldn't make heavy actions when process discovery message. Best solution 
will be separated thread that will do it, while discovery-msg-worker will just 
pass a message to that thread and send a message immediately to another node in 
topology.

This affects both TcpDiscoverySpi and ZkDiscoverySpi.

{noformat}
[11:59:33,134][INFO][tcp-disco-msg-worker-#2][TcpDiscoverySpi] Enqueued message 
type = TcpDiscoveryCustomEventMessage id = 
e4b542b6561-a38dfe31-dcfd-430b-acb3-5a531db4197e time = 0
[11:59:33,537][INFO][tcp-disco-msg-worker-#2][GridSnapshotAwareClusterStateProcessorImpl]
 Received activate request with BaselineTopology[id=0]
[11:59:33,549][INFO][tcp-disco-msg-worker-#2][GridSnapshotAwareClusterStateProcessorImpl]
 Started state transition: true
[11:59:33,752][INFO][exchange-worker-#62][time] Started exchange init 
[topVer=AffinityTopologyVersion [topVer=110, minorTopVer=1], crd=true, 
evt=DISCOVERY_CUSTOM_EVT, evtNode=a38dfe31-dcfd-430b-acb3-5a531db4197e, 
customEvt=ChangeGlobalStateMessage 
[id=cea542b6561-47395de6-c204-4576-a0a3-99ec53d41ac3, 
reqId=5b651439-7a6a-43fc-9cb0-d646c3380576, 
initiatingNodeId=a38dfe31-dcfd-430b-acb3-5a531db4197e, activate=true, 
baselineTopology=BaselineTopology [id=0, branchingHash=-69412111965, 
branchingType='New BaselineTopology', baselineNodes=[node42, node43, node44, 
node45, node46, node47, node48, node49, node50, node51, node52, node53, node54, 
node55, node56, node57, node58, node59, node1, node4, node5, node2, node3, 
node8, node9, node6, node7, node60, node61, node62, node63, node64, node65, 
node66, node67, node68, node69, node70, node71, node72, node73, node74, node75, 
node76, node77, node78, node79, node80, node81, node82, node83, node84, node85, 
node86, node87, node88, node89, node90, node91, node92, node93, node94, node95, 
node96, node97, node10, node98, node11, node99, node12, node13, node14, node15, 
node16, node100, node17, node18, node19, node108, node107, node106, node105, 
node104, node103, node102, node101, node109, node20, node21, node22, node23, 
node24, node25, node26, node27, node28, node29, node110, node30, node31, 
node32, node33, node34, node35, node36, node37, node38, node39, node40, 
node41]], forceChangeBaselineTopology=false, timestamp=1535101173015], 
allowMerge=false]
[11:59:33,753][INFO][exchange-worker-#62][GridDhtPartitionsExchangeFuture] 
Start activation process [nodeId=1906b9c3-73f4-4c30-85cc-cf6b99c3bab9, 
client=false, topVer=AffinityTopologyVersion [topVer=110, minorTopVer=1]]
[11:59:33,756][INFO][exchange-worker-#62][FilePageStoreManager] Resolved page 
store work directory: 
/storage/ssd/avolkov/tiden/snapshots-180824-114937/test_pitr/ignite.server.1/work/db/node1
[11:59:33,756][INFO][exchange-worker-#62][FileWriteAheadLogManager] Resolved 
write ahead log work directory: 
/storage/ssd/avolkov/tiden/snapshots-180824-114937/test_pitr/ignite.server.1/work/db/wal/node1
[11:59:33,756][INFO][exchange-worker-#62][FileWriteAheadLogManager] Resolved 
write ahead log archive directory: 
/storage/ssd/avolkov/tiden/snapshots-180824-114937/test_pitr/ignite.server.1/work/db/wal/archive/node1
[11:59:33,757][INFO][exchange-worker-#62][FileWriteAheadLogManager] Started 
write-ahead log manager [mode=LOG_ONLY]
[11:59:33,763][INFO][tcp-disco-msg-worker-#2][TcpDiscoverySpi] Processed 
message type = TcpDiscoveryCustomEventMessage id = 
e4b542b6561-a38dfe31-dcfd-430b-acb3-5a531db4197e time = 629
{noformat}




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

[jira] [Created] (IGNITE-9399) Document new WAL history size configuration parameter

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-9399:


 Summary: Document new WAL history size configuration parameter
 Key: IGNITE-9399
 URL: https://issues.apache.org/jira/browse/IGNITE-9399
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Alexey Goncharuk






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

[GitHub] ignite pull request #4626: IGNITE-9389 Avoid deadlocks on cache#close()

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Exchange stucks while node restoring state from WAL

[Pavel Kovalenko]

Hello Maxim,

I think you're going in the right direction, but why you perform binary
recovery only in the case when a node in the baseline?
I think that node can also perform binary recovery before the first
exchange is started in case of
1) First activation
2) Baseline change

In all of these cases, you need just local available CacheDescriptors to
restore binary state from WAL.
I would like also see a test when Ignite is stopped in the middle of a
checkpoint and binary recovery succeed before PME in that case also.


ср, 22 авг. 2018 г. в 15:31, Pavel Kovalenko :

> Hello Maxim,
>
> Thank you for your work. I will review your changes within the next
> several days.
>
> 2018-08-22 11:12 GMT+03:00 Maxim Muzafarov :
>
>> Pavel,
>>
>> Thank you for so detailed introduction into the root of the problem of
>> ticket IGNITE-7196.
>> As you mentioned before, we can divide this ticket into two sub-tasks. So,
>> I will
>> file new issue for `Logical consistency recovery`. I think it's more
>> convenient way
>> for reviewing and merging each of these high level Steps (PRs).
>>
>> Currently, let's focus on `Physical(binary) consistency recovery` as the
>> most critical
>> part of this issue and synchronize our vision and vision of other
>> community
>> members
>> on implementation details of Step 1. From this point everything what I'm
>> saying is about
>> only binary recovery.
>>
>>
>> I think PR is almost ready (I need to check TC carefully).
>> Can you look at my changes? Am I going the right way?
>>
>> PR: https://github.com/apache/ignite/pull/4520
>> Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-727
>> JIRA: https://issues.apache.org/jira/browse/IGNITE-7196
>>
>>
>> These are my milestones which I've tried to solve:
>> 1. On first time cluster activation no changes required. We should keep
>> this behavior.
>>
>> 2. `startMemoryPolicies` earlier if need.
>> Now at the master branch data regions starts at onActivate method called.
>> If we are  trying
>> to restore binary state on node reconnects to cluster we should start
>> regions earlier.
>>
>> 3. `suspendLogging` method added to switch off handlers.
>> Keep fast PDS cleanup when joining is not in BLT (or belongs to another
>> BLT).
>> Restore memory and metastorage initialization required `WALWriter` and
>> `FileWriteHandle`
>> to be started. They can lock directory\files and block cleanups.
>>
>> 4. `isBaselineNode` check before resumming logging.
>> The same as point 3. Local node gets discovery data and determines
>> #isLocalNodeNotInBaseline.
>> If node not in current baseline it performs cleanup local PDS and we
>> should
>> reset state of
>> previously initialized at startup metastorage instance.
>>
>> 5. `cacheProcessorStarted` callback added to restore memory at startup.
>> We can restore memory only after having info about all
>> `CacheGroupDescriptor`. To achieve this
>> we should do restoring at the moment `GridCacheProcessor` started.
>>
>> 6. Move `fsync` for `MemoryRecoveryRecord` at node startup.
>> We are fsync'ing it inside running PME. Suppose, it used for recovery
>> actions and\or control
>> cluster state outside Ignite project (methods `nodeStart` and
>> `nodeStartedPointers` of this
>> are not used at Ignite project code). I've moved them at the node startup,
>> but may be we should
>> dumping timestamp only at the time of node activation. Not sure.
>>
>> 7. `testBinaryRecoverBeforeExchange` test added to check restore before
>> PME.
>> Not sure that we should repeat wal reading logic as it was in
>> `testApplyDeltaRecords` test for
>> checking memory restoring. Suppose, minimally necessary condition is to
>> check `lastRestored` and
>> `checkpointHistory` states of database manager's (they should happend
>> before node joins to cluster).
>>
>> I will create separate ticket and refactor these minor issues after we
>> will
>> finish with 7196:
>> - simlify registerMBeans methods for
>> `Ignite\GridCacheDatabaseSharedManager`
>> - add @Override annotations if missed
>> - fix abbreviations regarding IdeaAbbrPlugin
>> - createDataRegionConfiguration method can be removed and simplified
>> - startMemoryPolicies rename to startDataRegion
>> - output messages format fix code style needed
>> - fix format javadoc's
>> - make inner classes private
>> - missed logging for cleanupCheckpointDirectory,
>> cleanupCheckpointDirectory, cleanupWalDirectories
>>
>> On Fri, 3 Aug 2018 at 18:20 Pavel Kovalenko  wrote:
>>
>> > Maxim,
>> >
>> > In the addition to my answer, I propose to divide the whole task into 2
>> > steps:
>> > 1) Physical consistency recovery before PME.
>> > 2) Logical consistency recovery before PME.
>> >
>> > The first step can be done before the discovery manager start, as it no
>> > needs any information about caches, it operates only with pages binary
>> > data. On this step, we can do points a) and b) from answer 3) and fsync
>> the
>> > state of the page memory.
>> > The second step is much harder to impleme

[jira] [Created] (IGNITE-9400) TC bot: add progress bar to history page

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-9400:


 Summary: TC bot: add progress bar to history page
 Key: IGNITE-9400
 URL: https://issues.apache.org/jira/browse/IGNITE-9400
 Project: Ignite
  Issue Type: Improvement
Reporter: Ilya Lantukh


History page (like */all.html?branch=master*) takes significant amount of time 
to load, and it would be helpful to replace spinning wheel with progress bar.



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

[jira] [Created] (IGNITE-9401) Newly added testRollbackOnTopologyLockPessimistic has a race which leads to suite hang.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-9401:
-

 Summary: Newly added testRollbackOnTopologyLockPessimistic has a  
race which leads to suite hang.
 Key: IGNITE-9401
 URL: https://issues.apache.org/jira/browse/IGNITE-9401
 Project: Ignite
  Issue Type: Bug
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
 Fix For: 2.7






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

[jira] [Created] (IGNITE-9402) IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnWALWritingFail2 because of LogOnly mode

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-9402:
-

 Summary: 
IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnWALWritingFail2 because of 
LogOnly mode
 Key: IGNITE-9402
 URL: https://issues.apache.org/jira/browse/IGNITE-9402
 Project: Ignite
  Issue Type: Test
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov


IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnWALWritingFail2 failed 
because it can lost last WAL data which have not flushed yet.



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

[GitHub] ignite pull request #4633: IGNITE-9401 Race fix.

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

IGNITE-9401 Race fix.



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

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

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

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

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

This closes #4633






---

[GitHub] ignite pull request #4634: IGNITE-8485: force encrypted mode for all caches

[nizhikov]

GitHub user nizhikov opened a pull request:

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

IGNITE-8485: force encrypted mode for all caches



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

$ git pull https://github.com/nizhikov/ignite IGNITE-8485-forced

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

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

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

This closes #4634


commit 241eeab3dea6dae3652d106e7f835be0f081f89a
Author: Nikolay Izhikov 
Date:   2018-06-25T10:22:59Z

IGNITE-8485: TDE Implementation

commit 763ebc413a6b9d395a71ac7024f028228f4dd710
Author: Nikolay Izhikov 
Date:   2018-06-25T19:46:41Z

Merge branch 'master' into IGNITE-8485

commit 410c7be5e0ebab67b0b74331559ed4f9548d2601
Author: Nikolay Izhikov 
Date:   2018-06-25T20:04:01Z

IGNITE-8485: Code review fixes.

commit 43b9cde1fc373cfecf7ebcf19b72d87e2e8653f4
Author: Nikolay Izhikov 
Date:   2018-06-26T08:33:59Z

IGNITE-8485: Code review fixes.

commit efac7b2b46729a73421b7738fea47171a71c2440
Author: Nikolay Izhikov 
Date:   2018-06-26T08:44:54Z

IGNITE-8485: Code review fixes.

commit 03855222fdab19c1173b9d2931d7b1db463f066e
Author: Nikolay Izhikov 
Date:   2018-06-26T08:45:39Z

IGNITE-8485: Code review fixes.

commit 02f7cffbee852345ed690e67100bbd701d03c429
Author: Nikolay Izhikov 
Date:   2018-06-26T08:58:07Z

IGNITE-8485: Code review fixes.

commit 6a884eaf9e3dfce7f177a59e591dd430b609a303
Author: Nikolay Izhikov 
Date:   2018-06-26T09:13:19Z

IGNITE-8485: Code review fixes.

commit 53a7eaaeb78190f69d2ecd8b3d775e7efc3dd65d
Author: Nikolay Izhikov 
Date:   2018-06-26T10:57:34Z

Merge branch 'master' into IGNITE-8485

commit f1581e53a6f6bcd066c9c2820570d11f586be516
Author: Nikolay Izhikov 
Date:   2018-06-26T11:03:28Z

IGNITE-8485: Code review fixes.

commit 4e4142eb28f3346e35a98d08ce65641c24834c4d
Author: Nikolay Izhikov 
Date:   2018-06-26T14:17:03Z

Merge branch 'master' into IGNITE-8485

commit 284177c8447f8baabab8d6553132c8c9da662359
Author: Nikolay Izhikov 
Date:   2018-06-26T14:28:45Z

IGNITE-8485: Code review fixes.

commit 9b222135db1a73d40c8973711581fe0768ad0528
Author: Nikolay Izhikov 
Date:   2018-06-26T14:34:30Z

IGNITE-8485: Code review fixes.

commit 5d237570ec02f53f4aadcc8f189e064bea45faa2
Author: Nikolay Izhikov 
Date:   2018-06-26T14:54:18Z

IGNITE-8485: Code review fixes.

commit 5894c498fa2516097256b0e1aa0ed67776dbab31
Author: Nikolay Izhikov 
Date:   2018-06-26T16:04:27Z

IGNITE-8485: Fix flaky test. Add encryption supported check.

commit 049cd0a554785511b2cadb0f90a8a4f60440dc93
Author: Nikolay Izhikov 
Date:   2018-06-26T16:30:34Z

IGNITE-8485: Code review fixes.

commit 4d4d0e2686b1f6c3894df90256493a8ea7d2b852
Author: Nikolay Izhikov 
Date:   2018-06-27T15:46:52Z

Merge branch 'master' into IGNITE-8485

commit 6af7e8be9f069ec5d6f1e9ee3457f67bc81f2763
Author: Nikolay Izhikov 
Date:   2018-06-28T15:43:49Z

IGNITE-8485: Code review fixes.

commit 6b6fb4d8eedc77d1be1490a5d45e4e2024ef1354
Author: Nikolay Izhikov 
Date:   2018-06-29T09:28:01Z

IGNITE-8485: Code review(In progress). Compilation failed.

commit fc6d0256b9b11dce822365b03798334f4a28f0c1
Author: Nikolay Izhikov 
Date:   2018-06-29T09:33:11Z

IGNITE-8485: revert unnecessary changes

commit af86e66bd4bf61e15e65cbc8ead95b0581e6fd2f
Author: Nikolay Izhikov 
Date:   2018-06-29T10:55:26Z

IGNITE-8485: Refactor encryption of DataRecord

commit 5127a6c03ef3aacbc179323c4e7737a045c481df
Author: Nikolay Izhikov 
Date:   2018-06-29T10:57:38Z

IGNITE-8485: Compilation fix

commit cde18b0127f8237c37bdace85e2659f826d6c75d
Author: Nikolay Izhikov 
Date:   2018-06-29T11:00:44Z

IGNITE-8485: minor fix

commit a20669026981141e70ab54956facc394536f6b2c
Author: Nikolay Izhikov 
Date:   2018-06-29T11:12:33Z

IGNITE-8485: minor fix

commit 4849f51067f040c514980d0734173c5ca98f13d4
Author: Nikolay Izhikov 
Date:   2018-06-29T15:04:33Z

IGNITE-8485: Test fixed.

commit bd312865091f6ed40e609b2e508754a92743c434
Author: Nikolay Izhikov 
Date:   2018-06-29T15:20:52Z

IGNITE-8485: minor fix.

commit 9cab4a1ccb1ef3b2b93f1da3f559e464a4ed157d
Author: Nikolay Izhikov 
Date:   2018-06-29T15:23:03Z

Undo edit

commit 9308e0f7e3f0ec07f126ea2d601ac625d0a1ef16
Author: Nikolay Izhikov 
Date:   2018-06-29T15:29:39Z

Merge branch 'master' into IGNITE-8485

commit eefa124153f6ad7529ef4991e7d391c09cc278de
Author: Nikolay Izhikov 
Date:   2018-06-29T16:13:40Z

IGNITE-8485: Test fix

commit 6acad7c10cd3a6b46382abd1e0dcef52eaded378
Author: Nikolay Izhikov 
Date:   2018-07-02T08:40:02Z

IGNITE-8485: Test fix




---

[GitHub] ignite pull request #4635: IGNITE-9149 Get rid of logging remaining supplier...

[ololo3000]

GitHub user ololo3000 opened a pull request:

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

IGNITE-9149 Get rid of logging remaining supplier nodes rebalance time



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

$ git pull https://github.com/ololo3000/ignite IGNITE-9149

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

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

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

This closes #4635


commit f3320b678b9f1be17bff433b32d8cc2cf26d1ae2
Author: ololo3000 
Date:   2018-08-28T14:24:18Z

IGNITE-9149 Get rid of logging remaining supplier nodes rebalance time




---

Re: Apache Ignite 2.7 release

[Nikolay Izhikov]

Hello, Igniters.

I think we should discuss the release schedule.

Current dates are following:

* Code Freeze: September 30, 2018
* Voting Date: October 1, 2018
* Release Date: October 15, 2018

We discussed it privately with Vladimir Ozerov.

Is seems better to reschedule a bit:

* Scope freeze - September 17 - We should have a full list of tickets 
for 2.7 here.
* Code freeze - October 01 - We should merge all 2.7 tickets to master 
here.
* Vote - October 08.

What do you think?


В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> I hope Vyacheslav can comment better than me. I suppose it is, more or
> less, rectifications and clarifications of design aspects. Not overall
> redesign.
> 
> I also hope Igniters, especially Services experts, will join the discussion
> in the separate topic. Now after a couple of days there is no reaction.
> 
> сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan :
> 
> > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov 
> > wrote:
> > 
> > > Hi Dmitriy, I suppose it highly depends on how fast community will come
> > 
> > to
> > > a consensus about design. So it is up to us to make this happen
> > > 
> > 
> > I am confused then. If we are still discussing design, then we are miles
> > away. Do you know if there anything in service grid that has already been
> > implemented and can be released?
> > 

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

Re: Compression prototype

[Vyacheslav Daradur]

I have another suggestion which may help us reduce objects size
extremely - implementing some kind of SQL Scheme.

For now, BinaryObject's format is too excessive - each serialized
object stores offset of every serialized field even if the offset can
be easily calculated.

If we move this metadata from a serialized object to a separate entity
- this will reduce an object's size.
On Mon, Aug 27, 2018 at 2:53 PM Vyacheslav Daradur  wrote:
>
> According to my benchmarks - zstd compression algorithm [1] looks very
> interesting, it has a high compression ratio with quite good speed.
> AFAIK it supports external dictionaries, but I'm not sure about using
> it with "on the fly building" dictionaries. Anyway, have look at (it
> has ASF 2.0 friendly license).
>
> Also, here is data generator / loader [1]. If it will be useful for
> you we should ask Nikolay Izhikov to share public docs to start.
>
> [1] https://github.com/facebook/zstd
> [2] https://github.com/nizhikov/ignite-cod-data-loader
> On Mon, Aug 27, 2018 at 2:11 PM Ilya Kasnacheev
>  wrote:
> >
> > Hello Vyacheslav!
> >
> > Unfortunately I have not found any efficient algorithms that will allow me
> > to use external dictionary as a pre-processed data structure. If plain gzip
> > is used without dictionary, the compression is around 0.7, as opposed to
> > 0.4 that I will get with custom implementation, AFAIR the performance was
> > also worse. I didn't really try it with dictionary, but I assume
> > performance will be even worse since it will have to scan dictionary before
> > getting to actual data.
> >
> > We have such a huge array of tests that we can just run them all with
> > compression enabled, see if there are any new failures. But the impact of
> > my commit is fairly low, it is only triggered when data is written to page
> > (maybe to WAL also?), and we don't really do much frivolous stuff to pages.
> >
> > Still, I am very much interested in finding existing compression
> > implementations with support of external dictionary; I am also very much
> > interested in having different implementations of compression for Apache
> > Ignite (such as per page compression) and comparing them by benchmark and
> > by code impact. I am also very interested in large standard datasets for
> > Apache Ignite (or generators thereof) so that we can run precise benchmarks
> > on various compression schemes. If you have any of the following, please
> > get back to me.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 27 авг. 2018 г. в 11:35, Vyacheslav Daradur :
> >
> > > Hi Igniters!
> > >
> > > Ilya, I'm glad to see one more person who is interested in the
> > > compression feature in Ignite.
> > >
> > > I looked through the pull request and want to share following thoughts:
> > >
> > > It's very dangerous using a custom algorithm in this way - you store
> > > serialized data separate from a dictionary and there are a lot of
> > > points when we may lose data: rebalancing, serialization errors, node
> > > rebooting and so on.
> > >
> > > I'd suggest the following ways to improve reliability:
> > > - use well know algorithms: zstd, deflater, lzma, gzip e.g. that
> > > allows us to decompress data in any situation
> > > - store the dictionary inside page with data
> > >
> > > Also, we have a lot of discussions [1] [2] about compression on
> > > BinaryObject and BinaryMarshaller level and Vladimir Ozerov was
> > > strictly against a compression on this level.
> > > If something has changed since then, you may look through [1] [2] [3]
> > > I've done a lot of research in algorithms comparison it may be useful
> > > for you.
> > >
> > > [1]
> > > http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html
> > > [2]
> > > http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-td20679.html
> > > [3] https://issues.apache.org/jira/browse/IGNITE-3592
> > > [4] https://issues.apache.org/jira/browse/IGNITE-5226
> > > [5] https://github.com/daradurvs/ignite-compression
> > > On Sat, Aug 25, 2018 at 2:51 AM Denis Magda  wrote:
> > > >
> > > > >
> > > > > Currently, the dictionary for decompression is only stored on heap.
> > > After
> > > > > restart there's compressed data in the PDS, but there's no dictionary
> > > :)
> > > >
> > > >
> > > > Basically, it means that I've lost my data, right? How about persisting
> > > > data to disk.
> > > >
> > > > Overall, we need Vladimir Ozerov to check the contribution. He was the
> > > one
> > > > who sponsored the IEP and knows the area best.
> > > >
> > > > --
> > > > Denis
> > > >
> > > > On Fri, Aug 24, 2018 at 4:31 AM Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello!
> > > > >
> > > > > It is somewhat a part of IEP-20, since I have updated it with this
> > > > > particular direction.
> > > > >
> > > > > Regards,
> > > > >
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > > 2018-08-24 2:56 GMT+03:00 Denis Magd

[GitHub] ignite pull request #4633: IGNITE-9401 Race fix.

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Compression prototype

[Ilya Kasnacheev]

Hello!

Yes, we can tinker with BinaryObject format, which is currently clearly
excessive.

But the best part with compression, it will automatically remove this
redundancy for us, for free. Even if we had hairy XML as binary object
format, it will still compress roughly to the same number of bytes. If we
will have fast transparent compression, we can just skip this work. Of
course, codifying offsets can have other uses, but it also have a lot of
limitations.

Regards,
-- 
Ilya Kasnacheev


вт, 28 авг. 2018 г. в 18:30, Vyacheslav Daradur :

> I have another suggestion which may help us reduce objects size
> extremely - implementing some kind of SQL Scheme.
>
> For now, BinaryObject's format is too excessive - each serialized
> object stores offset of every serialized field even if the offset can
> be easily calculated.
>
> If we move this metadata from a serialized object to a separate entity
> - this will reduce an object's size.
> On Mon, Aug 27, 2018 at 2:53 PM Vyacheslav Daradur 
> wrote:
> >
> > According to my benchmarks - zstd compression algorithm [1] looks very
> > interesting, it has a high compression ratio with quite good speed.
> > AFAIK it supports external dictionaries, but I'm not sure about using
> > it with "on the fly building" dictionaries. Anyway, have look at (it
> > has ASF 2.0 friendly license).
> >
> > Also, here is data generator / loader [1]. If it will be useful for
> > you we should ask Nikolay Izhikov to share public docs to start.
> >
> > [1] https://github.com/facebook/zstd
> > [2] https://github.com/nizhikov/ignite-cod-data-loader
> > On Mon, Aug 27, 2018 at 2:11 PM Ilya Kasnacheev
> >  wrote:
> > >
> > > Hello Vyacheslav!
> > >
> > > Unfortunately I have not found any efficient algorithms that will
> allow me
> > > to use external dictionary as a pre-processed data structure. If plain
> gzip
> > > is used without dictionary, the compression is around 0.7, as opposed
> to
> > > 0.4 that I will get with custom implementation, AFAIR the performance
> was
> > > also worse. I didn't really try it with dictionary, but I assume
> > > performance will be even worse since it will have to scan dictionary
> before
> > > getting to actual data.
> > >
> > > We have such a huge array of tests that we can just run them all with
> > > compression enabled, see if there are any new failures. But the impact
> of
> > > my commit is fairly low, it is only triggered when data is written to
> page
> > > (maybe to WAL also?), and we don't really do much frivolous stuff to
> pages.
> > >
> > > Still, I am very much interested in finding existing compression
> > > implementations with support of external dictionary; I am also very
> much
> > > interested in having different implementations of compression for
> Apache
> > > Ignite (such as per page compression) and comparing them by benchmark
> and
> > > by code impact. I am also very interested in large standard datasets
> for
> > > Apache Ignite (or generators thereof) so that we can run precise
> benchmarks
> > > on various compression schemes. If you have any of the following,
> please
> > > get back to me.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 27 авг. 2018 г. в 11:35, Vyacheslav Daradur :
> > >
> > > > Hi Igniters!
> > > >
> > > > Ilya, I'm glad to see one more person who is interested in the
> > > > compression feature in Ignite.
> > > >
> > > > I looked through the pull request and want to share following
> thoughts:
> > > >
> > > > It's very dangerous using a custom algorithm in this way - you store
> > > > serialized data separate from a dictionary and there are a lot of
> > > > points when we may lose data: rebalancing, serialization errors, node
> > > > rebooting and so on.
> > > >
> > > > I'd suggest the following ways to improve reliability:
> > > > - use well know algorithms: zstd, deflater, lzma, gzip e.g. that
> > > > allows us to decompress data in any situation
> > > > - store the dictionary inside page with data
> > > >
> > > > Also, we have a lot of discussions [1] [2] about compression on
> > > > BinaryObject and BinaryMarshaller level and Vladimir Ozerov was
> > > > strictly against a compression on this level.
> > > > If something has changed since then, you may look through [1] [2] [3]
> > > > I've done a lot of research in algorithms comparison it may be useful
> > > > for you.
> > > >
> > > > [1]
> > > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html
> > > > [2]
> > > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-td20679.html
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-3592
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-5226
> > > > [5] https://github.com/daradurvs/ignite-compression
> > > > On Sat, Aug 25, 2018 at 2:51 AM Denis Magda 
> wrote:
> > > > >
> > > > > >
> > > > > > Currently, the dictionary for decompression is only stored on
> heap.
> > > > After
> > > > > > res

[GitHub] ignite pull request #4636: IGNITE-9398 Async notification to discovery spi l...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-9398 Async notification to discovery spi listener



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

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

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

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

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

This closes #4636






---

Re: Apache Ignite 2.7 release

[Dmitriy Setrakyan]

Hi Nikolai,

Generally looks OK, however, It is hard to comment on your schedule without
seeing a full list of all must-have features we plan to add to this
release. I am hoping that the community will see this list at some point.

D.

On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov 
wrote:

> Hello, Igniters.
>
> I think we should discuss the release schedule.
>
> Current dates are following:
>
> * Code Freeze: September 30, 2018
> * Voting Date: October 1, 2018
> * Release Date: October 15, 2018
>
> We discussed it privately with Vladimir Ozerov.
>
> Is seems better to reschedule a bit:
>
> * Scope freeze - September 17 - We should have a full list of
> tickets for 2.7 here.
> * Code freeze - October 01 - We should merge all 2.7 tickets to
> master here.
> * Vote - October 08.
>
> What do you think?
>
>
> В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> > I hope Vyacheslav can comment better than me. I suppose it is, more or
> > less, rectifications and clarifications of design aspects. Not overall
> > redesign.
> >
> > I also hope Igniters, especially Services experts, will join the
> discussion
> > in the separate topic. Now after a couple of days there is no reaction.
> >
> > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan :
> >
> > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov  >
> > > wrote:
> > >
> > > > Hi Dmitriy, I suppose it highly depends on how fast community will
> come
> > >
> > > to
> > > > a consensus about design. So it is up to us to make this happen
> > > >
> > >
> > > I am confused then. If we are still discussing design, then we are
> miles
> > > away. Do you know if there anything in service grid that has already
> been
> > > implemented and can be released?
> > >
>

Re: Ignite new contributor

[Denis Magda]

Hello Ravil and welcome to the community!

I've added you to the contributor's list in JIRA. Please feel free to take
over the tasks.

--
Denis

On Tue, Aug 28, 2018 at 7:04 AM Ravil Galeyev  wrote:

> Hi Team,
>
> I'd like to join to Apache Ignite development.
> Especially to the ML part.
> Currently, I work on IGNITE-9285
> 
> and I'm going to continue work with subtasks from IGNITE-9281
>  (ML starter tasks).
>
> My Jira login is rgaleyev
>
> Best regards,
> Ravil
>

[GitHub] ignite pull request #4637: IGNITE-1678 IgniteAtomicSequence: make following ...

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-1678 IgniteAtomicSequence: make following reservations in advance



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

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

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

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

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

This closes #4637


commit ed9c2d27cdac5e65fe1689a4583678b9cbd1b3d1
Author: Dmitriy Govorukhin 
Date:   2018-08-26T07:35:01Z

IGNITE-1678 add percentage for atomic seq reservation in config + interfaces

commit cbfe5932a4b1230bb1aac8075004eea73479e7b2
Author: Dmitriy Govorukhin 
Date:   2018-08-26T07:53:47Z

IGNITE-1678 add percentage as parameter for atomic seq

commit 4a1d0c244fe015c7aaee7861857e84f05b985fc2
Author: Dmitriy Govorukhin 
Date:   2018-08-26T09:31:07Z

IGNITE-1678 add new test + small test updates

commit 839f43adf80a04e4a2778983560031592a20a89e
Author: Dmitriy Govorukhin 
Date:   2018-08-26T11:45:49Z

IGNITE-1678 first implementation (fully not working)

commit bd46569fc1e1f65709ac7a838f9b76d4df5c39d9
Author: Dmitriy Govorukhin 
Date:   2018-08-26T17:36:22Z

IGNITE-1678 minor test fix

commit 62bc2c94601d15a3eb3c939313ae88fbb81ca0fb
Author: Dmitriy Govorukhin 
Date:   2018-08-26T18:29:52Z

IGNITE-1678 fix config for chaining

commit 2d2627056ca288d95c68934286c0e80e66b4ca4e
Author: Dmitriy Govorukhin 
Date:   2018-08-26T18:48:07Z

IGNITE-1678 set default reservation percentage as 100

commit cf9a98f938f740c226b71ad73e734ac1834d97fe
Author: Dmitriy Govorukhin 
Date:   2018-08-27T10:44:39Z

IGNITE-1678 minor assert added + fix NPE

commit 0415064f4dbbfb3bea6d359467af1525af235b68
Author: Dmitriy Govorukhin 
Date:   2018-08-28T08:36:57Z

IGNITE-1678 rework reservation, add reservation context

commit 589297a406421a72254f949a1b0cb19cf14b9a26
Author: Dmitriy Govorukhin 
Date:   2018-08-28T09:42:21Z

IGNITE-1678 test refactoring

commit 4cdaf252de5526c19ba8672ac10819e9a983e1a1
Author: Dmitriy Govorukhin 
Date:   2018-08-28T16:50:00Z

Merge branch 'master' into ignite-1678

commit 7d1cf05c37867aab1a6496a97cf6ffc4727c8501
Author: Dmitriy Govorukhin 
Date:   2018-08-28T19:14:35Z

IGNITE-1678 add benchmarks




---

Re: Apache Ignite 2.7 release

[Denis Magda]

Nikolay, Igniters, let me help you with the list.

That what I was tracking on my side (something we can announce). Don't have
a JIRA ticket for every ticket but CC-ed everyone who claimed to be in
charge. Nikolay, please work with the community members to add these
capabilities to the release wiki page. If something doesn't get delivered
then let's exclude it.

1. Partition map exchange optimizations. Are we releasing any of them? *(Sergey
Chugunov, Andrey Mashenkov)*
https://cwiki.apache.org/confluence/display/IGNITE/IEP-25%3A+Partition+Map+Exchange+hangs+resolving

2. Java 9/10/11 Support. Are we on track to support it better? *(Peter,
Vladimir)*.

3. SQL *(Vladimir)*:

   - Transactional SQL beta?
   - Basic monitoring facilities (inline index alerts, page reads/writes
   per type)?
   - SQL index update optimizations? (
   
https://cwiki.apache.org/confluence/display/IGNITE/IEP-19%3A+SQL+index+update+optimizations
   )
   - ODBC/JDBC session management
   - Result set offload to disk. Looks it doesn't get to the release?
   https://issues.apache.org/jira/browse/IGNITE-7526

4. JCache 1.1 support. Completed!

5. Transparent data encryption? What exactly goes in 2.7? *(Nikolay)*.

6. Ignite + Informatica integration

7. Ignite and Spring Session integration (heard it was done but the ticket
is still Open):
https://issues.apache.org/jira/browse/IGNITE-2741

8. Service Grid 2.0. What exactly goes in 2.7? (*Vyacheslav)*
https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid

9. Ignite Multi Map *(Amir, Anton)*
https://issues.apache.org/jira/browse/IGNITE-640

10. Thin Clients:

   - Node.JS (https://issues.apache.org/jira/browse/IGNITE-) - *Pavel
   Petroshenko*
   - Python (https://issues.apache.org/jira/browse/IGNITE-7782) - *Pavel
   Petroshenko, **Dmitry Melnichuk*
   - PHP (https://issues.apache.org/jira/browse/IGNITE-7783) - *Pavel P.,
   Ekaterina*
   - C++: *Igor S.*
   - Affinity awareness for thin clients (*Igor S.*):
   
https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients

11. Machine and Deep Learning (preprocessing APIs, TensorFlow integration,
extra algorithms) - *Yuri and our ML experts*



On Tue, Aug 28, 2018 at 10:17 AM Dmitriy Setrakyan 
wrote:

> Hi Nikolai,
>
> Generally looks OK, however, It is hard to comment on your schedule without
> seeing a full list of all must-have features we plan to add to this
> release. I am hoping that the community will see this list at some point.
>
> D.
>
> On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov 
> wrote:
>
> > Hello, Igniters.
> >
> > I think we should discuss the release schedule.
> >
> > Current dates are following:
> >
> > * Code Freeze: September 30, 2018
> > * Voting Date: October 1, 2018
> > * Release Date: October 15, 2018
> >
> > We discussed it privately with Vladimir Ozerov.
> >
> > Is seems better to reschedule a bit:
> >
> > * Scope freeze - September 17 - We should have a full list of
> > tickets for 2.7 here.
> > * Code freeze - October 01 - We should merge all 2.7 tickets to
> > master here.
> > * Vote - October 08.
> >
> > What do you think?
> >
> >
> > В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> > > I hope Vyacheslav can comment better than me. I suppose it is, more or
> > > less, rectifications and clarifications of design aspects. Not overall
> > > redesign.
> > >
> > > I also hope Igniters, especially Services experts, will join the
> > discussion
> > > in the separate topic. Now after a couple of days there is no reaction.
> > >
> > > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan :
> > >
> > > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <
> dpavlov@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hi Dmitriy, I suppose it highly depends on how fast community will
> > come
> > > >
> > > > to
> > > > > a consensus about design. So it is up to us to make this happen
> > > > >
> > > >
> > > > I am confused then. If we are still discussing design, then we are
> > miles
> > > > away. Do you know if there anything in service grid that has already
> > been
> > > > implemented and can be released?
> > > >
> >
>

[GitHub] ignite pull request #4638: Ignite 2.4.8 p3

[gromtech]

GitHub user gromtech opened a pull request:

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

Ignite 2.4.8 p3



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

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

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

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

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

This closes #4638


commit ce8f6bcffe85d16c93e4ca8f9b8be894cd9fe9f9
Author: Pavel Kovalenko 
Date:   2018-03-21T14:32:51Z

IGNITE-6113 Fixed version handling.

commit aae4e97b786e1bc9b2353ddee61ff7077b8d759c
Author: Pavel Kovalenko 
Date:   2018-03-06T18:22:40Z

IGNITE-6113 Return back old implementation instead of 'removeIf' - Fixes 
#3609.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 8c3731e83296e1750c7c098b283c3fd8584b1be4)

commit d60d4fd8f6abe652a5618e5644fb978bcb1495b0
Author: Denis Mekhanikov 
Date:   2018-03-20T02:19:35Z

IGNITE-7794 - Share persisted marshaller mappings when connecting - Fixes 
#3620.

Signed-off-by: Valentin Kulichenko 
(cherry picked from commit c4ccf55dd6eb22102c56e211812eb4ccc206f4a7)

commit 70efde3305a1559231583f453aeb228ed2d40896
Author: Valentin Kulichenko 
Date:   2018-03-20T02:20:20Z

Added new test to suite

Signed-off-by: Valentin Kulichenko 
(cherry picked from commit baf08bc9501676e418dab2431211a659ae421d25)

commit 002e4d650c072c0927a93075e79d2ab1652b475d
Author: EdShangGG 
Date:   2018-03-22T14:58:39Z

IGNITE-8007 We should treat as empty any partition as empty if it doesn't 
have any data - Fixes #3677.

(cherry picked from commit 14f7bce)

commit 699561265ae616b5eb75897343be84d8c83be804
Author: Anton Kalashnikov 
Date:   2018-03-21T15:53:15Z

GG-13631 fix GridDhtPartitionDemandLegacyMessage

(cherry picked from commit ffbc56e)

commit 37c8033c72ac4fd1ec1e419ba68142c4fe11ad8b
Author: tledkov-gridgain 
Date:   2018-03-13T09:37:29Z

IGNITE-7860: JDBC thin: changed default socket buffer size to 64Kb. This 
closes #3600.

commit 130adcf29ddb61f8e9baa784b81454d3ed7c3b75
Author: Pavel Tupitsyn 
Date:   2018-01-26T08:48:14Z

IGNITE-7530 .NET: Fix GetAll memory usage and performance in binary mode

This closes #3436

commit 824004909b23a9a7d599500967af34103acb8c47
Author: Igor Sapego 
Date:   2018-01-30T12:56:17Z

IGNITE-6810: Implemented SSL support for ODBC.

This closes #3361

commit 82da0b5e9dc2ee2339c3fb1023e35d415bf1b647
Author: Pavel Kuznetsov 
Date:   2018-02-07T12:37:52Z

IGNITE-6217: Added benchmark to compare JDBC vs native SQL

This closes #2558

commit 701c6f141f6812ad7bc050a86266e696cf5863ed
Author: tledkov-gridgain 
Date:   2018-02-08T12:29:42Z

IGNITE-6625: JDBC thin: support SSL connection to Ignite node

This closes #3233

commit 2d729bf5c6f6fca9d07be2d57850642ba4b55004
Author: tledkov-gridgain 
Date:   2018-02-09T11:08:15Z

IGNITE-6625: SSL support for thin JDBC: additional fix test; change error 
message

commit 8994f847d7f5f15db73706d9210cdccb1cf3fb26
Author: devozerov 
Date:   2018-02-12T13:34:24Z

IGNITE-7003: Fixed faulty test 
WalModeChangeAdvancedSelfTest.testJoinCoordinator.

commit b142712264007d7397d1594541681a4a7e3d4b93
Author: Igor Sapego 
Date:   2018-02-26T12:02:07Z

IGNITE-7362: Fixed PDO ODBC integration issue

commit a2b2aee52cc65d01f2ecaf9462adc4bd368438ea
Author: Igor Sapego 
Date:   2018-02-28T10:23:12Z

IGNITE-7763: Fixed 32bit tests configurations to prevent OOM

This closes #3557

commit 652f3c4cdbaad40f5de25b06f0c13710aa7f2fd9
Author: Pavel Kuznetsov 
Date:   2018-03-13T12:46:36Z

IGNITE-7531: Data load benchmarks. This closes #3571.

commit 9337a53d9fcd62af87f6760080d350b43e275105
Author: tledkov-gridgain 
Date:   2018-03-16T11:38:38Z

IGNITE-7879: Fixed splitter logic for DISTINCT with subqueries. This closes 
#3634.

commit 7bec8b13cb373002d2a6b1b268d410338259bac2
Author: Igor Sapego 
Date:   2018-03-19T11:17:33Z

IGNITE-7811: Implemented connection failover for ODBC

This closes #3643

commit e512e5e0a2602df0ecfb69b2b5efabce836b04db
Author: Igor Sapego 
Date:   2018-03-20T10:37:02Z

IGNITE-7888: Implemented login timeout for ODBC.

This closes #3657

commit 211fca3a55e84b78ff0c1af04d91e25d6fc846c4
Author: devozerov 
Date:   2018-03-20T11:13:46Z

IGNITE-7984: SQL: improved deadlock handling in DML. This closes #3655.

commit bcd2888d27afe65f1a060e35b99a05ea420979c7
Author: Roman Guseinov 
Date:   2018-02-16T09:57:26Z

IGNITE-7192: Implemented JDBC support FQDN to multiple IPs

This closes #3439

commit d2659d0ec9f6e1a0b905fc7bf23b65fd5522c80a
Author: Alexander Paschenko 
Date:   2018-03-14T09:23:37Z

IGNITE-7253: JDBC thin driver: implemented streaming. This closes #3499. 
This closes #3591.

commit

Retries in write-behind store

[Valentin Kulichenko]

Folks,

Is there a way to limit or disable retries of failed updates in the
write-behind store? I can't find one, it looks like if an update fails, it
is moved to the end of the queue and then eventually retried. If it fails
again, process is repeated.

Such behavior *might* be OK if failures are caused by database being
temporarily unavailable. But what if update fails deterministically, for
example due to a constraint violation? There is absolutely no reason to
retry it, and at the same time it can cause stability and performance
issues when buffer is full with such "broken" updates.

Does it makes sense to add an option that would allow to limit number of
retries (or even disable them)?

-Val

Re: Retries in write-behind store

[Denis Magda]

Val,

Sounds like a handy configuration option. I would allow setting a number of
retries. If the number is set to 0 then a failed update is discarded right
away.

--
Denis

On Tue, Aug 28, 2018 at 9:14 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Folks,
>
> Is there a way to limit or disable retries of failed updates in the
> write-behind store? I can't find one, it looks like if an update fails, it
> is moved to the end of the queue and then eventually retried. If it fails
> again, process is repeated.
>
> Such behavior *might* be OK if failures are caused by database being
> temporarily unavailable. But what if update fails deterministically, for
> example due to a constraint violation? There is absolutely no reason to
> retry it, and at the same time it can cause stability and performance
> issues when buffer is full with such "broken" updates.
>
> Does it makes sense to add an option that would allow to limit number of
> retries (or even disable them)?
>
> -Val
>

[jira] [Created] (IGNITE-9403) TDE - Phase-1. Thin clients

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-9403:
---

 Summary: TDE - Phase-1. Thin clients
 Key: IGNITE-9403
 URL: https://issues.apache.org/jira/browse/IGNITE-9403
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolay Izhikov


We should provide support for a new {{encryptionEnabled}} flag in cache 
configuration for all thin clients:

  - .Net
  - Java
  -  NodeJs
  - Python
  - PHP
  - C++(for now it doesn't have support of {{CacheConfiguration}})

Backward compatibility should be preserved.
A contributor can take 
[commit](https://github.com/apache/ignite/commit/baab0a6ddd3973fb8fca6ecb0a7d841d7d3a72be)
 as an example



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