date:20171116

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #2871: Ignite-gg-12960

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #2896: IGNITE-6649: Add EvictionPolicy factory support i...

Github user AMashenkov closed the pull request at:

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


---

Re: Add support of distributed matrices for OLS regression. (PR #3030 / IGNITE-5846)

2017-11-16 Thread Alexey Zinoviev

The documentation is corect, all changes are added for internals in
reality, without changes in API.


17 нояб. 2017 г. 1:35 AM пользователь "Denis Magda" 
написал:

> Hi Alex,
>
> Impressive, thanks for sharing this with us. Btw, do we need to tweak the
> existing OLS documentation to mention the contributed changes?
> https://apacheignite.readme.io/docs/ols-multiple-linear-regression
>
> —
> Denis
>
> > On Nov 16, 2017, at 5:55 AM, Alexey Zinoviev 
> wrote:
> >
> > Hello,
> >
> > I've added support of distributed OLS regression per
> > IGNITE-5846 [1] and would want to push these to master.
> >
> > Changes impact "ml" module, more details of portion of code can be
> > found in PR #3030 [2]. Yury Babak [3], Oleg Ignatenko[4] did review and
> > sanity
> > check.
> >
> > The main idea was to keep OLS Regression as algorithm and add support of
> > many operations on SparseDistributedMatrix and
> SparseBlockDistributedMatrix.
> >
> > To implement this functionality I added SparseBlockDistributedVector and
> > SparseDistributedVector classes. Also a few operations on distributed
> > vectors and matrices were implemented using power of affinity.
> >
> > The successful build could be found here [5]
> >
> >
> > [1]  https://issues.apache.org/jira/browse/IGNITE-5846
> > [2]  https://github.com/apache/ignite/pull/3030
> > [3] https://github.com/ybabak
> > [4] https://github.com/oignatenko
> > [5]
> > https://ci.ignite.apache.org/viewLog.html?buildId=945536;
> buildTypeId=Ignite20Tests_IgniteMl=buildResultsDiv
> >
> > Sincerely yours,
> > Alex
>
>

[jira] [Created] (IGNITE-6944) Fail to execute task with immutable list string

2017-11-16 Thread Edmond Tsang (JIRA)

Edmond Tsang created IGNITE-6944:


 Summary: Fail to execute task with immutable list string
 Key: IGNITE-6944
 URL: https://issues.apache.org/jira/browse/IGNITE-6944
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: binary
Affects Versions: 2.3
Reporter: Edmond Tsang


Exception occurs when executing task with immutable list of string due to not 
able to find method readResolve/writeReplace for binary object.

It appears this is caused by a side effect of Jira 
https://issues.apache.org/jira/browse/IGNITE-6485 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6943) Web console: LoadCahces method should activate cluster if persistent is configured, otherwise method doesn't work due to cluster is inactive

2017-11-16 Thread Pavel Konstantinov (JIRA)

Pavel Konstantinov created IGNITE-6943:
--

 Summary: Web console: LoadCahces method should activate cluster if 
persistent is configured, otherwise method doesn't work due to cluster is 
inactive
 Key: IGNITE-6943
 URL: https://issues.apache.org/jira/browse/IGNITE-6943
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: wizards
Affects Versions: 2.3
Reporter: Pavel Konstantinov
 Fix For: 2.4






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

WEBINARS: Apache Ignite Essentials for Architects and Java Developers

Igniters,

I’m pleased to invite all of you to a series of webinars that will introduce 
you to the fundamental capabilities of in-memory computing platforms such as 
Apache Ignite.

That will be a mix of theory and practice. A lot of code examples are waiting 
to be shown so that you can apply the theory in practice right away. The series 
consists of two parts.

More details are here:
https://blogs.apache.org/ignite/entry/apache-ignite-essentials-series-for

Please help to spread a word about this event!
https://twitter.com/denismagda/status/931318985353605120

—
Denis

IGNITE-6745. Status

2017-11-16 Thread Cergey

Hi, igniters

 

Why no one commented on the patch and pull request
(https://github.com/apache/ignite/pull/2970) ?  What should I do ?

 

Regards,

Cergey Chaulin

Re: Meetup tonight in Santa Clara CA: "In-Memory Computing Essentials for Java Developers"

Tom,

Thanks for promoting the workshop! Igniters, minor correction, that’s gonna be 
the first 2.5 hours advanced workshop on Ignite internals and capabilities. 
Join me at 6.30 PM today if you’re Silicon Valley.

By the end of the workshop the you will learn how:

• Configure and deploy Apache Ignite clusters

• Partitioning and replication works at the nutshells

• Process distributed data sets using key-value, SQL and compute APIs

• Apply collocated processing concept in practice

• Configure SQL schemas and tap into SQL language

• Enable and utilize persistence.

—
Denis

> On Nov 16, 2017, at 6:04 AM, Tom Diederich  wrote:
> 
> Igniters, those of you in the San Francisco Bay Area are invited to tonight's 
> meetup in Santa Clara. It features Ignite PMC Chair Denis Magda who will 
> deliver a 90-minute  hands-on workshop titled : "In-Memory Computing 
> Essentials for Java Developers "
> 
> More info and RSVP here : 
> Tom
> 
> 
> 
> 
>

Re: Add support of distributed matrices for OLS regression. (PR #3030 / IGNITE-5846)

Hi Alex,

Impressive, thanks for sharing this with us. Btw, do we need to tweak the 
existing OLS documentation to mention the contributed changes? 
https://apacheignite.readme.io/docs/ols-multiple-linear-regression

—
Denis

> On Nov 16, 2017, at 5:55 AM, Alexey Zinoviev  wrote:
> 
> Hello,
> 
> I've added support of distributed OLS regression per
> IGNITE-5846 [1] and would want to push these to master.
> 
> Changes impact "ml" module, more details of portion of code can be
> found in PR #3030 [2]. Yury Babak [3], Oleg Ignatenko[4] did review and
> sanity
> check.
> 
> The main idea was to keep OLS Regression as algorithm and add support of
> many operations on SparseDistributedMatrix and SparseBlockDistributedMatrix.
> 
> To implement this functionality I added SparseBlockDistributedVector and
> SparseDistributedVector classes. Also a few operations on distributed
> vectors and matrices were implemented using power of affinity.
> 
> The successful build could be found here [5]
> 
> 
> [1]  https://issues.apache.org/jira/browse/IGNITE-5846
> [2]  https://github.com/apache/ignite/pull/3030
> [3] https://github.com/ybabak
> [4] https://github.com/oignatenko
> [5]
> https://ci.ignite.apache.org/viewLog.html?buildId=945536=Ignite20Tests_IgniteMl=buildResultsDiv
> 
> Sincerely yours,
> Alex

Re: request for contributors permissions

Hello Sergey,

Granted the permissions. Please go ahead and pick ticket you like.

Some extra info that might be useful for you.

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

—
Denis

> On Nov 16, 2017, at 4:29 AM, Сергей Трудов  wrote:
> 
> Hello.
> 
> I want to resolve bugs and create new features :)
> 
> Jira account: sv.trudov
> 
> Best regards,
> Trudov Sergey

Re: request for contributors permissions

Hi,

Welcome to the community!


Some extra info that might be useful for you.

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

—
Denis

> On Nov 16, 2017, at 4:41 AM, Zetsubou Toshio  
> wrote:
> 
> Hello!
> 
> I need permissions to assign jira task to me
> My account: vv.timoshenko
> 
> Thanks!

Re: Adding Persistent Memory Support for Ignite

2017-11-16 Thread Dmitriy Setrakyan

Hi Mulugeta,

Where can I find documentation about LLPL to understand how memory and
persistence are handled there?

D.

On Thu, Nov 16, 2017 at 7:16 AM, Mammo, Mulugeta 
wrote:

> Hi all,
>
>
>
> Ignite, when persistence mode is enabled, stores data and indexes on disk.
> To minimize the latency of disks, several tuning options can be applied.
> Setting the page size of a memory region to match the page size of the
> underlying storage, using a separate disk for the WAL, and using
> production-level SSDs are just a few of them [
> https://apacheignite.readme.io/docs/durable-memory-tuning#
> section-native-persistence-related-tuning ].
>
> A persistent memory store with low latency and high capacity offers a
> viable alternative to disks. In light of this, we are proposing to make use
> of our Low Level Persistent Library (LLPL), https://github.com/pmem/pcj/
> tree/master/LLPL, to offer a persistent memory storage for Ignite.
>
> At this point, we envision two distinct implementation options:
>
> 1.  Data and indexes will continue to be stored in the off-heap memory
> but the disk will be replaced by a persistent memory. Since persistence
> memory in this option is not a file system, the logic currently offered by
> WAL file and the partition files would have to be implemented from scratch.
>
> 2.  In this option, we eliminate the current check-point process and
> the WAL file. We will use a memory region defined by LLPL to store data and
> indexes. There will be no off-heap memory. DRAM will be exclusively used to
> store hot cache entries just like the on-heap cache is in the current
> implementation.
>
> In both cases, there are more details and subtleties that have to handled
> - e.g. the atomic and transactional guarantees offered. More clarifications
> will be given as we go along. And, feel free to provide your thoughts.
>
> Thanks,
> Mulugeta
>
>

[jira] [Created] (IGNITE-6942) Auto re-connect to other node in case of failure of current

2017-11-16 Thread Mikhail Cherkasov (JIRA)

Mikhail Cherkasov created IGNITE-6942:
-

 Summary: Auto re-connect to other node in case of failure of 
current
 Key: IGNITE-6942
 URL: https://issues.apache.org/jira/browse/IGNITE-6942
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: sql
Reporter: Mikhail Cherkasov
 Fix For: 2.4


it will be great to have a re-connect feature for thin driver, in case if 
server failure it should choose another server node from a list of server nods.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3054: Ignite-gg-12940

GitHub user AMashenkov opened a pull request:

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

Ignite-gg-12940



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

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

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

https://github.com/apache/ignite/pull/3054.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 #3054


commit c3e8a832098887a0fd09b6e8f63d6a8cbaa20eb9
Author: Pavel Tupitsyn 
Date:   2016-11-11T15:00:36Z

.NET: Fix DataStreamerTestTopologyChange tests

commit a2a3bedce1a232c0c1db6f5e2b737ab47be250b0
Author: sboikov 
Date:   2016-11-14T06:44:48Z

Fixed IgniteStartFromStreamConfigurationTest to stop started node.

commit 85a4b966fdfb7018d1c91b73df1659082128f786
Author: Pavel Tupitsyn 
Date:   2016-11-14T10:38:33Z

IGNITE-4216 .NET: Fix PlatformAffinityFunction to inject resource into 
baseFunc

commit 6e36a7950db84913ddfd0d98f5a0b50923d2a29c
Author: tledkov-gridgain 
Date:   2016-11-15T09:42:29Z

IGNITE-3191: Fields are now sorted for binary objects which don't implement 
Binarylizable interface. This closes #1197.

commit e39888a08da313bec4d30f96488eccb36b4abacc
Author: Vasiliy Sisko 
Date:   2016-11-17T04:41:05Z

IGNITE-4163 Fixed load range queries.

commit 3eacc0b59c27be6b4b3aaa09f84b867ba42b449f
Author: Alexey Kuznetsov 
Date:   2016-11-21T10:28:56Z

Merged ignite-1.7.3 into ignite-1.7.4.

commit 0234f67390c88dceefd6e62de98adb922b4ba9ac
Author: Alexey Kuznetsov 
Date:   2016-11-21T10:40:50Z

IGNITE-3443 Implemented metrics for queries monitoring.

commit a24a394bb66ba0237a9e9ef940707d422b2980f0
Author: Konstantin Dudkov 
Date:   2016-11-21T10:53:58Z

IGNITE-2523 "single put" NEAR update request

commit 88f38ac6305578946f2881b12d2d557bd561f67d
Author: Konstantin Dudkov 
Date:   2016-11-21T12:11:09Z

IGNITE-3074 Optimize DHT atomic update future

commit 51ca24f2db32dff9c0034603ea3abfe5ef5cd846
Author: Konstantin Dudkov 
Date:   2016-11-21T13:48:44Z

IGNITE-3075 Implement single key-value pair DHT request/response for ATOMIC 
cache.

commit 6e4a279e34584881469a7d841432e6c38db2f06f
Author: tledkov-gridgain 
Date:   2016-11-21T14:15:17Z

IGNITE-2355: fix test - clear client connections before and after a test.

commit 551f90dbeebcad35a0e3aac07229fb67578f2ab7
Author: tledkov-gridgain 
Date:   2016-11-21T14:16:49Z

Merge remote-tracking branch 'community/ignite-1.7.4' into ignite-1.7.4

commit f2dc1d71705b86428a04a69c4f2d4ee3a82ed1bd
Author: sboikov 
Date:   2016-11-21T15:12:27Z

Merged ignite-1.6.11 into ignite-1.7.4.

commit d32fa21b673814b060d2362f06ff44838e9c2cdc
Author: sboikov 
Date:   2016-11-22T08:33:55Z

IGNITE-3075 Fixed condition for 'single' request creation

commit d15eba4becf7515b512c1032b193ce75e1589177
Author: Anton Vinogradov 
Date:   2016-11-22T08:56:20Z

IGNITE-4225 DataStreamer can hang on changing topology

commit f80bfbd19e7870554bf3abd13bde89b0f39aaee1
Author: Anton Vinogradov 
Date:   2016-11-22T09:02:57Z

IGNITE-3748 Data rebalancing of large cache can hang out.

commit bc695f8e3306c6d74d4fe53d9a98adedd43ad8f0
Author: Igor Sapego 
Date:   2016-11-22T09:05:15Z

IGNITE-4227: ODBC: Implemented SQLError. This closes #1237.

commit fc9ee6a74fe0bf413ab0643d2776a1a43e6dd5d2
Author: devozerov 
Date:   2016-11-22T09:05:32Z

Merge remote-tracking branch 'upstream/ignite-1.7.4' into ignite-1.7.4

commit 861fab9d0598ca2f06c4a6f293bf2866af31967c
Author: tledkov-gridgain 
Date:   2016-11-22T09:52:03Z

IGNITE-4239: add GridInternal annotaion for tasks instead of jobs. This 
closes #1250.

commit ba99df1554fbd1de2b2367b6ce011a024cd199bd
Author: tledkov-gridgain 
Date:   2016-11-22T10:07:20Z

IGNITE-4239: test cleanup

commit c34d27423a0c45c61341c1fcb3f56727fb91498f
Author: Igor Sapego 
Date:   2016-11-22T11:13:28Z

IGNITE-4100: Fix for DEVNOTES paths.

commit 9d82f2ca06fa6069c1976cc75814874256b24f8c
Author: devozerov 
Date:   2016-11-22T12:05:29Z

IGNITE-4259: Fixed a problem with geospatial indexes and BinaryMarshaller.

commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov

[GitHub] ignite pull request #3053: IGNITE-6869 Added new JMX metric: Total jobs exec...

2017-11-16 Thread alex-plekhanov

GitHub user alex-plekhanov opened a pull request:

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

IGNITE-6869 Added new JMX metric: Total jobs execution time. 

Added new JMX metric: Total jobs execution time. 
Added MBean to monitor aggregated cluster metrics.

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

$ git pull https://github.com/alex-plekhanov/ignite ignite-6869

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

https://github.com/apache/ignite/pull/3053.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 #3053


commit 46384430e99135ba3aeba5a64d43c0c8c097ad8b
Author: Aleksey Plekhanov 
Date:   2017-11-16T16:31:16Z

IGNITE-6869 Added new JMX metric: Total jobs execution time. Added MBean to 
monitor aggregated cluster metrics.




---

[jira] [Created] (IGNITE-6941) Add JDBC Thin Client security support.

2017-11-16 Thread Andrew Mashenkov (JIRA)

Andrew Mashenkov created IGNITE-6941:


 Summary: Add JDBC Thin Client security support.
 Key: IGNITE-6941
 URL: https://issues.apache.org/jira/browse/IGNITE-6941
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: jdbc
Reporter: Andrew Mashenkov


For now JDBC thin client doesn't supports username\password to be passed to 
security plugin.
We should fixed this together with IGNITE-6856

http://apache-ignite-users.70518.x6.nabble.com/How-can-I-get-Ignite-security-plugin-to-work-with-JDBC-thin-client-tt17740.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Confusing slf4j error messages

2017-11-16 Thread Alexey Popov

It will utilize commons-logging (it is in dependency tree) according to
https://spring.io/blog/2009/12/04/logging-dependencies-in-spring/

"The nice thing about commons-logging is that you don’t need anything else
to make your application work. It has a runtime discovery algorithm that
looks for other logging frameworks in well known places on the classpath and
uses one that it thinks is appropriate (or you can tell it which one if you
need to). If nothing else is available you get pretty nice looking logs just
from the JDK (java.util.logging or JUL for short). You should find that your
Spring application works and logs happily to the console out of the box in
most situations, and that’s important."

Thanks,
Alexey





--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-6940) Provide metric to monitor Thread Starvation

2017-11-16 Thread Andrey Kuznetsov (JIRA)

Andrey Kuznetsov created IGNITE-6940:


 Summary: Provide metric to monitor Thread Starvation
 Key: IGNITE-6940
 URL: https://issues.apache.org/jira/browse/IGNITE-6940
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Reporter: Andrey Kuznetsov


There is an existing code in {{IgniteKernal.start()}} that logs warnings when 
detects starvation. It should be improved to support more thread pools and 
update some metrics.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3052: IGNITE-6931

2017-11-16 Thread gvvinblade

GitHub user gvvinblade opened a pull request:

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

IGNITE-6931



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

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

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

https://github.com/apache/ignite/pull/3052.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 #3052


commit f6caa5695c1bd87b30dc442f641d81dca3df9a42
Author: Igor Seliverstov 
Date:   2017-11-16T16:14:15Z

IGNITE-6931 Simplify index rebuild




---

[GitHub] ignite pull request #3051: IGNITE-6870 Added new JMX metric for cache topolo...

2017-11-16 Thread alex-plekhanov

GitHub user alex-plekhanov opened a pull request:

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

IGNITE-6870 Added new JMX metric for cache topology validation monitoring



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

$ git pull https://github.com/alex-plekhanov/ignite ignite-6870

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

https://github.com/apache/ignite/pull/3051.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 #3051


commit 2f18a7283898e1b78bae7b1b182cb5892fe20c82
Author: Aleksey Plekhanov 
Date:   2017-11-16T16:03:06Z

IGNITE-6870 Added new JMX metric for cache topology validation monitoring.




---

[GitHub] ignite pull request #3050: Ignite-gg-12939

GitHub user AMashenkov opened a pull request:

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

Ignite-gg-12939



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

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

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

https://github.com/apache/ignite/pull/3050.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 #3050


commit c3e8a832098887a0fd09b6e8f63d6a8cbaa20eb9
Author: Pavel Tupitsyn 
Date:   2016-11-11T15:00:36Z

.NET: Fix DataStreamerTestTopologyChange tests

commit a2a3bedce1a232c0c1db6f5e2b737ab47be250b0
Author: sboikov 
Date:   2016-11-14T06:44:48Z

Fixed IgniteStartFromStreamConfigurationTest to stop started node.

commit 85a4b966fdfb7018d1c91b73df1659082128f786
Author: Pavel Tupitsyn 
Date:   2016-11-14T10:38:33Z

IGNITE-4216 .NET: Fix PlatformAffinityFunction to inject resource into 
baseFunc

commit 6e36a7950db84913ddfd0d98f5a0b50923d2a29c
Author: tledkov-gridgain 
Date:   2016-11-15T09:42:29Z

IGNITE-3191: Fields are now sorted for binary objects which don't implement 
Binarylizable interface. This closes #1197.

commit e39888a08da313bec4d30f96488eccb36b4abacc
Author: Vasiliy Sisko 
Date:   2016-11-17T04:41:05Z

IGNITE-4163 Fixed load range queries.

commit 3eacc0b59c27be6b4b3aaa09f84b867ba42b449f
Author: Alexey Kuznetsov 
Date:   2016-11-21T10:28:56Z

Merged ignite-1.7.3 into ignite-1.7.4.

commit 0234f67390c88dceefd6e62de98adb922b4ba9ac
Author: Alexey Kuznetsov 
Date:   2016-11-21T10:40:50Z

IGNITE-3443 Implemented metrics for queries monitoring.

commit a24a394bb66ba0237a9e9ef940707d422b2980f0
Author: Konstantin Dudkov 
Date:   2016-11-21T10:53:58Z

IGNITE-2523 "single put" NEAR update request

commit 88f38ac6305578946f2881b12d2d557bd561f67d
Author: Konstantin Dudkov 
Date:   2016-11-21T12:11:09Z

IGNITE-3074 Optimize DHT atomic update future

commit 51ca24f2db32dff9c0034603ea3abfe5ef5cd846
Author: Konstantin Dudkov 
Date:   2016-11-21T13:48:44Z

IGNITE-3075 Implement single key-value pair DHT request/response for ATOMIC 
cache.

commit 6e4a279e34584881469a7d841432e6c38db2f06f
Author: tledkov-gridgain 
Date:   2016-11-21T14:15:17Z

IGNITE-2355: fix test - clear client connections before and after a test.

commit 551f90dbeebcad35a0e3aac07229fb67578f2ab7
Author: tledkov-gridgain 
Date:   2016-11-21T14:16:49Z

Merge remote-tracking branch 'community/ignite-1.7.4' into ignite-1.7.4

commit f2dc1d71705b86428a04a69c4f2d4ee3a82ed1bd
Author: sboikov 
Date:   2016-11-21T15:12:27Z

Merged ignite-1.6.11 into ignite-1.7.4.

commit d32fa21b673814b060d2362f06ff44838e9c2cdc
Author: sboikov 
Date:   2016-11-22T08:33:55Z

IGNITE-3075 Fixed condition for 'single' request creation

commit d15eba4becf7515b512c1032b193ce75e1589177
Author: Anton Vinogradov 
Date:   2016-11-22T08:56:20Z

IGNITE-4225 DataStreamer can hang on changing topology

commit f80bfbd19e7870554bf3abd13bde89b0f39aaee1
Author: Anton Vinogradov 
Date:   2016-11-22T09:02:57Z

IGNITE-3748 Data rebalancing of large cache can hang out.

commit bc695f8e3306c6d74d4fe53d9a98adedd43ad8f0
Author: Igor Sapego 
Date:   2016-11-22T09:05:15Z

IGNITE-4227: ODBC: Implemented SQLError. This closes #1237.

commit fc9ee6a74fe0bf413ab0643d2776a1a43e6dd5d2
Author: devozerov 
Date:   2016-11-22T09:05:32Z

Merge remote-tracking branch 'upstream/ignite-1.7.4' into ignite-1.7.4

commit 861fab9d0598ca2f06c4a6f293bf2866af31967c
Author: tledkov-gridgain 
Date:   2016-11-22T09:52:03Z

IGNITE-4239: add GridInternal annotaion for tasks instead of jobs. This 
closes #1250.

commit ba99df1554fbd1de2b2367b6ce011a024cd199bd
Author: tledkov-gridgain 
Date:   2016-11-22T10:07:20Z

IGNITE-4239: test cleanup

commit c34d27423a0c45c61341c1fcb3f56727fb91498f
Author: Igor Sapego 
Date:   2016-11-22T11:13:28Z

IGNITE-4100: Fix for DEVNOTES paths.

commit 9d82f2ca06fa6069c1976cc75814874256b24f8c
Author: devozerov 
Date:   2016-11-22T12:05:29Z

IGNITE-4259: Fixed a problem with geospatial indexes and BinaryMarshaller.

commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov

[jira] [Created] (IGNITE-6939) Exclude false owners from the execution plan based on query response

2017-11-16 Thread Alexey Goncharuk (JIRA)

Alexey Goncharuk created IGNITE-6939:


 Summary: Exclude false owners from the execution plan based on 
query response
 Key: IGNITE-6939
 URL: https://issues.apache.org/jira/browse/IGNITE-6939
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
Reporter: Alexey Goncharuk


This is related to IGNITE-6858, the fix in the ticket can be improved.

The scenario leading to the issue is as follows:
1) Node A has partition 1 as owning
2) Node B has local partition map which has partition 1 on node A as owning
3) Topology change is triggered which would move partition 1 from A to another 
node, topology version is X
4) A transaction is started on node B on topology X
5) Partition is rebalanced and node A moves partition 1 to RENTING and then to 
EVICTED state, node A updates it's local partition map.
6) A new topology change is triggered
7) Node A sends partition map (transitively) to the node B, but since there is 
a pending exchange, node B ignores the updated map and still thinks that A owns 
partition 1 [1]
8) transaction attempts to execute an SQL query against partition 1 on node A 
and retries infinitely

[1] The related code is in 
GridDhtPartitionTopologyImpl#update(AffinityTopologyVersion, 
GridDhtPartitionFullMap, CachePartitionFullCountersMap, Set, 
AffinityTopologyVersion)
{code}
if (stopping || !lastTopChangeVer.initialized() ||
// Ignore message not-related to exchange if exchange is in progress.
(exchangeVer == null && !lastTopChangeVer.equals(readyTopVer)))
return false;
{code}

There are two possibilities to fix this:
1) Make all updates to partition map in a single thread, then we will not need 
update sequences and then we can update local partition map even when there is 
a pending exchange (this is a relatively big, but useful change)
2) Make a change in SQL query execution so that if a node cannot reserve a 
partition, do not map the partition to this node on the same topology version 
anymore (a quick fix)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3049: IGNITE-6907 Check LINQ join tests for errors

2017-11-16 Thread apopovgg

GitHub user apopovgg opened a pull request:

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

IGNITE-6907 Check LINQ join tests for errors



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

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

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

https://github.com/apache/ignite/pull/3049.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 #3049


commit f09b03788611cd17570dfd1f240e2ffbbb5f3b06
Author: apopov 
Date:   2017-11-16T15:44:56Z

IGNITE-6907Check LINQ join tests for errors




---

Adding Persistent Memory Support for Ignite

2017-11-16 Thread Mammo, Mulugeta

Hi all,

Ignite, when persistence mode is enabled, stores data and indexes on disk. To
minimize the latency of disks, several tuning options can be applied. Setting
the page size of a memory region to match the page size of the underlying
storage, using a separate disk for the WAL, and using production-level SSDs are
just a few of them [
https://apacheignite.readme.io/docs/durable-memory-tuning#section-native-persistence-related-tuning
].

A persistent memory store with low latency and high capacity offers a viable
alternative to disks. In light of this, we are proposing to make use of our Low
Level Persistent Library (LLPL), https://github.com/pmem/pcj/tree/master/LLPL,
to offer a persistent memory storage for Ignite.

At this point, we envision two distinct implementation options:

1. Data and indexes will continue to be stored in the off-heap memory but
the disk will be replaced by a persistent memory. Since persistence memory in
this option is not a file system, the logic currently offered by WAL file and
the partition files would have to be implemented from scratch.

2. In this option, we eliminate the current check-point process and the
WAL file. We will use a memory region defined by LLPL to store data and
indexes. There will be no off-heap memory. DRAM will be exclusively used to
store hot cache entries just like the on-heap cache is in the current
implementation.

In both cases, there are more details and subtleties that have to handled -
e.g. the atomic and transactional guarantees offered. More clarifications will
be given as we go along. And, feel free to provide your thoughts.

Thanks,
Mulugeta

[jira] [Created] (IGNITE-6938) SQL TX: Reads should see own's previous writes

Vladimir Ozerov created IGNITE-6938:
---

 Summary: SQL TX: Reads should see own's previous writes
 Key: IGNITE-6938
 URL: https://issues.apache.org/jira/browse/IGNITE-6938
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: cache, sql
Reporter: Vladimir Ozerov
 Fix For: 2.4


If transaction modified a row, subsequent {{SELECT}} statements in the same TX 
must return latest pending update instead of last matching committed version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6937) SQL TX: Support SELECT FOR UPDATE

Vladimir Ozerov created IGNITE-6937:
---

 Summary: SQL TX: Support SELECT FOR UPDATE
 Key: IGNITE-6937
 URL: https://issues.apache.org/jira/browse/IGNITE-6937
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
Reporter: Vladimir Ozerov
 Fix For: 2.4


Normally in SQL world readers do not block writers. This is how our SELECT 
operations should work by default. But we need to add a support for {{SELECT 
... FOR UPDATE}} read mode, when reader obtains exclusive lock on read. 

In this mode we lock entries as usual, but then send data back to the caller. 
First page can be returned directly in our {{LockResponse}}. Next pages should 
be requested in separate requests. With this approach {{SELECT ,,, FOR UPDATE}} 
will require only single round-trip to both lock and read data in case of small 
updates.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6936) SQL TX: Implement commit protocol

Vladimir Ozerov created IGNITE-6936:
---

 Summary: SQL TX: Implement commit protocol
 Key: IGNITE-6936
 URL: https://issues.apache.org/jira/browse/IGNITE-6936
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: cache, sql
Reporter: Vladimir Ozerov
 Fix For: 2.4


Once we are able to lock entries [1], next step is to implement 2PC commit 
protocol. Cache protocol could be used as a template. The main difference is 
that near (client) node will not store entries. 

[1] IGNITE-6935



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6935) SQL TX: Locking protocol for simple queries

Vladimir Ozerov created IGNITE-6935:
---

 Summary: SQL TX: Locking protocol for simple queries
 Key: IGNITE-6935
 URL: https://issues.apache.org/jira/browse/IGNITE-6935
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: cache, sql
Reporter: Vladimir Ozerov
 Fix For: 2.4


We need to develop locking protocol for SQL queries. Design considerations:
1) Use {{GridNeaLockRequest|Response}} as a template for new messages
2) Cover only queries which doesn't require reduce stage (see server-side DML 
optimization code, e.g. {{GridH2DmlRequest}}).
3) When next entry is found, try locking it. If it is already locked, then 
register current TX as candidate in MVCC manager and go to the next row. Other 
TXes will notify use when entries are released. Send a response when all 
entries are locked.
4) Read entry version before locking and after. If they doesn't match (i.e. 
concurrent modification occurred), then throw an exception.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6934) SQL: evaluate performance of onheap row caching

Vladimir Ozerov created IGNITE-6934:
---

 Summary: SQL: evaluate performance of onheap row caching
 Key: IGNITE-6934
 URL: https://issues.apache.org/jira/browse/IGNITE-6934
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Taras Ledkov
 Fix For: 2.4


Ignite has so-called "on heap cache" feature. When cache entry is accessed, we 
copy it from offheap to heap and put it into a temporal concurrent hash map 
[1], [2], where it resides during usage. When operation is finished, entry is 
evicted. This is default behavior which keeps GC pressure low even for large 
in-memory data sets.

The downside is that we loose time on copying from offheap to heap. To mitigate 
this problem user can enable on-heap cache through 
{{IgniteCache.onheapCacheEnabled}}. In this mode entry will not be evicted from 
on-heap map, so it can be reused between different operations without 
additional copying. Eviction rules are managed through eviction policy. 

Unfortunately, SQL cannot use this optimization. As a result if key or value is 
large enough, we loose a lot of time on memory copying. And we cannot use 
current on-heap cache directly, we in SQL operate on row links, rather than on 
keys. So to apply this optimization to SQL we should either create additional 
row cache, or hack existing cache somehow.

As a first step I propose to evaluate the impact with quick and dirty solution:
1) Just add another map from link to K-V pair in the same cache, putting all 
concurrency issues aside.
2) Use this cache from SQL engine.
3) Measure the impact. 

[1] org.apache.ignite.internal.processors.cache.GridCacheConcurrentMapImpl
[2] 
org.apache.ignite.internal.processors.cache.GridCacheConcurrentMap.CacheMapHolder



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3048: IGNITE-6932 GridQueryProcessor.querySqlFieldsNoCa...

2017-11-16 Thread tledkov-gridgain

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-6932 GridQueryProcessor.querySqlFieldsNoCache should check forâ¦

â¦ cluster active/inactive state

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

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

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

https://github.com/apache/ignite/pull/3048.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 #3048


commit 0601c1ba628556c4f5be82063dae111658f57a46
Author: tledkov-gridgain 
Date:   2017-11-16T14:18:03Z

IGNITE-6932 GridQueryProcessor.querySqlFieldsNoCache should check for 
cluster active/inactive state




---

Meetup tonight in Santa Clara CA: "In-Memory Computing Essentials for Java Developers"

2017-11-16 Thread Tom Diederich

Igniters, those of you in the San Francisco Bay Area are invited to tonight's 
meetup in Santa Clara. It features Ignite PMC Chair Denis Magda who will 
deliver a 90-minute  hands-on workshop titled : "In-Memory Computing Essentials 
for Java Developers "

More info and RSVP here : 
Tom

Add support of distributed matrices for OLS regression. (PR #3030 / IGNITE-5846)

2017-11-16 Thread Alexey Zinoviev

Hello,

I've added support of distributed OLS regression per
IGNITE-5846 [1] and would want to push these to master.

Changes impact "ml" module, more details of portion of code can be
found in PR #3030 [2]. Yury Babak [3], Oleg Ignatenko[4] did review and
sanity
check.

The main idea was to keep OLS Regression as algorithm and add support of
many operations on SparseDistributedMatrix and SparseBlockDistributedMatrix.

To implement this functionality I added SparseBlockDistributedVector and
SparseDistributedVector classes. Also a few operations on distributed
vectors and matrices were implemented using power of affinity.

The successful build could be found here [5]


[1]  https://issues.apache.org/jira/browse/IGNITE-5846
[2]  https://github.com/apache/ignite/pull/3030
[3] https://github.com/ybabak
[4] https://github.com/oignatenko
[5]
https://ci.ignite.apache.org/viewLog.html?buildId=945536=Ignite20Tests_IgniteMl=buildResultsDiv

Sincerely yours,
Alex

[GitHub] ignite pull request #3047: Ignite-gg-12943-1.9

GitHub user AMashenkov opened a pull request:

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

Ignite-gg-12943-1.9



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

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

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

https://github.com/apache/ignite/pull/3047.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 #3047


commit f8224d13cf9a6432ba65e0016370ba51bbb544e9
Author: Alexey Goncharuk 
Date:   2017-06-15T19:49:45Z

GG-12299: Make sure concurrent type registrations do not trigger multiple 
cache updates.

commit 4ffc3acfa1bc43bea8c79bfd1864787c15cfc4de
Author: Alexey Goncharuk 
Date:   2017-06-20T04:59:09Z

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store 
exception.

commit 8cd9e829380f4c91cc9bb126169863286d1cb323
Author: Andrey V. Mashenkov 
Date:   2017-06-21T12:40:14Z

GG-12353: Added local binary context flag.

Backport of IGNITE-5223 with fixes.

commit 9036ad239d68eff663bc73a81baab2826b054d9a
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:25:31Z

Added MBean for system cache executors.

commit ed34a5dc681ea8f284f4d25c5575ad46569cc600
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:33:55Z

Partial fix of IGNITE-5562.

commit d427021f329292fb69d348ba949ad1f8f1e9089e
Author: Andrey V. Mashenkov 
Date:   2017-06-21T16:30:27Z

IGNITE-5552: ServiceProcessor recalculates all service assignments even if 
there is a pending topology change.

commit f1b9cdc0716a1b23f54d68ce0fe19eb85107567d
Author: Alexey Goncharuk 
Date:   2017-06-14T18:37:54Z

GG-12354: Partial fix of IGNITE-5473: Introduce troubleshooting logger.

commit beb2409cfe2045789443d47de735d879961d371e
Author: Andrey V. Mashenkov 
Date:   2017-06-23T09:26:06Z

GG-12352: Forcible node drop makes cluster instable in some cases.
Disable forcible node drop by default.

commit 802f18fc250cbae8959192c78bb28dc525ed3cf7
Author: AMRepo 
Date:   2017-06-22T21:24:57Z

Fix compilation

commit 39d2dec85a3c571dfdb1cd6189b53ae2413a5d22
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:41:30Z

Merge branch 'ignite-1.7.12-b2' into ignite-1.8.8

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/internal/GridTopic.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/IgniteIoTestMessage.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/service/GridServiceProcessor.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/task/GridTaskThreadContextKey.java
#   
modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite5.java

commit 96445156143b46b664f785b353463dd435ac342d
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:42:44Z

Merge remote-tracking branch 'origin/ignite-1.8.8' into ignite-1.8.8

# Conflicts:
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite5.java

commit 7c569f15a80ab9301c21011d2c9159e311e46cef
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:48:10Z

Merge remote-tracking branch 'origin/ignite-1.8.7.p1' into ignite-1.8.8

commit a64339449be8fa602cab3f2868c5f74004a7b747
Author: Igor Sapego 
Date:   2017-06-23T13:57:49Z

IGNITE-4370: Implemented writing of batch of parameters for ODBC.

(cherry picked from commit c10be5780589cc84e7929e234e4411d515166e0b)
(cherry picked from commit d268b32cb252a5f06887d2b803d27ddc20ded95f)

commit cbe5df51c423568782e31245c7f1aa06c9ba3be1
Author: Igor Sapego 
Date:   2017-06-13T16:47:00Z

IGNITE-5478: ODBC: SQLNumParams now returns number of required parameters.

(cherry picked from commit b1c56a1)

(cherry picked from commit 4a8f295)

commit 9ad513e68b89e907f7db36a3f3f0daca0e5986e6
Author: Igor Sapego 
Date:   2017-06-23T14:06:40Z

IGNITE-5478: Fix for cherry

request for contributors permissions

2017-11-16 Thread Zetsubou Toshio

Hello!

I need permissions to assign jira task to me
My account: vv.timoshenko

Thanks!

[GitHub] ignite pull request #3046: IGNITE-6612: Wrap ack methods in their own class

2017-11-16 Thread 1vanan

GitHub user 1vanan opened a pull request:

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

IGNITE-6612: Wrap ack methods in their own class



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

$ git pull https://github.com/1vanan/ignite ignite-6612

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

https://github.com/apache/ignite/pull/3046.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 #3046


commit 645f7c03d7f4b4e75cebaabb13796b9cf28196a2
Author: Ivan 
Date:   2017-11-08T11:18:28Z

initial refactoring

commit 2a9a031feeb069c80fe5bba4771e12800097bdb8
Author: Ivan 
Date:   2017-11-16T09:09:50Z

tests was added

commit 534cf85f96ffed76250406953b27fb785cac049b
Author: Ivan 
Date:   2017-11-16T09:58:06Z

remove garbage




---

[GitHub] ignite pull request #3045: IGN-8915

2017-11-16 Thread vldpyatkov

GitHub user vldpyatkov opened a pull request:

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

IGN-8915

[IGNITE-6922] Class can not undeploy from grid in some specific cases

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

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

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

https://github.com/apache/ignite/pull/3045.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 #3045


commit c128364a43ed78683642914fd2533facac6e922a
Author: vd-pyatkov 
Date:   2017-11-16T12:15:21Z

IGN-8915
[IGNITE-6922] Class can not undeploy from grid in some specific cases




---

[GitHub] ignite pull request #3044: IGNITE-5755 change calculation of memory policy s...

2017-11-16 Thread sergvolkov

GitHub user sergvolkov opened a pull request:

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

IGNITE-5755 change calculation of memory policy size



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

$ git pull https://github.com/sergvolkov/ignite ignite-2.1

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

https://github.com/apache/ignite/pull/3044.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 #3044


commit e593c768aa7dcbfed30f2592e5ea1e1ad35ded77
Author: SA.Volkov 
Date:   2017-11-16T12:10:22Z

IGNITE-5755 change calculation of memory policy size




---

Re: Confusing slf4j error messages

2017-11-16 Thread Nikolai Tikhonov

Hello Alexey!

If we exclude this dependency, which logger will be used by spring
framework?

On Thu, Nov 16, 2017 at 2:35 PM, Alexey Popov  wrote:

> Hi Igniters,
>
> Ignite examples and Ignite itself with some configurations prints out
> annoying messages related to slf4j:
>
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
>
> The reason for these messages is inside
> org.springframework.data:spring-data-commons. It adds a dependency to
> jcl-over-slf4j that "activates" slf4j. slf4j then tries to find
> slf4j-TO-SOMELOGGER to forward all messages to SOMELOGGER. Actually, it
> does
> not result in any issues with Ignite logging itself, it just confusing
> Ignite users.
>
> So, there are two options here to avoid these annoying messages:
> 1. exclude jcl-over-slf4j dependency from spring-data-commons in Ignite
> .pom
> files
> 2. add slf4j-TO-SOMELOGGER (for instance, slf4j-log4j12 for log4j, or
> slf4j-simple) dependency
>
> Please advice on a better solution here.
>
> Thank you,
> Alexey
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-6933) Consider executing updates in-place when SQL indexes are present or object size is smaller than the old object size

2017-11-16 Thread Alexey Goncharuk (JIRA)

Alexey Goncharuk created IGNITE-6933:


 Summary: Consider executing updates in-place when SQL indexes are 
present or object size is smaller than the old object size
 Key: IGNITE-6933
 URL: https://issues.apache.org/jira/browse/IGNITE-6933
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
Reporter: Alexey Goncharuk


Currently, we are able to execute in-place updates when the new object size 
exactly matches the old object size and SQL indexes are absent. This leads to a 
significant performance cost because of extra FreeList updates and extra 
indexes updates when only one field has changed.

A few possibilities which should be carefully examined:
1) Allow in-place updates if a new object size is smaller than the old object 
size (allow some space leak into the data page) and defer FreeList update to 
some later time (introduce a threshold?)
2) Examine (or propagate) the list of changed fields and allow in-place updates 
if indexed fields did not change
3) Investigate if we can implement an in-place update even with indexed fields 
- first, remove the value from indexes, then update, then insert value to 
indexes (note that there is a window when the value is not accessible via 
indexes in this case, so this is not a safe option). Also, do not update 
indexes if the indexed value did not change



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Confusing slf4j error messages

2017-11-16 Thread Alexey Popov

Hi Igniters,

Ignite examples and Ignite itself with some configurations prints out
annoying messages related to slf4j:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.

The reason for these messages is inside
org.springframework.data:spring-data-commons. It adds a dependency to
jcl-over-slf4j that "activates" slf4j. slf4j then tries to find
slf4j-TO-SOMELOGGER to forward all messages to SOMELOGGER. Actually, it does
not result in any issues with Ignite logging itself, it just confusing
Ignite users.

So, there are two options here to avoid these annoying messages:
1. exclude jcl-over-slf4j dependency from spring-data-commons in Ignite .pom
files
2. add slf4j-TO-SOMELOGGER (for instance, slf4j-log4j12 for log4j, or
slf4j-simple) dependency

Please advice on a better solution here.

Thank you,
Alexey




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-6932) GridQueryProcessorюquerySqlFieldsNoCache should check for cluster active/inactive state

Vladimir Ozerov created IGNITE-6932:
---

 Summary: GridQueryProcessorюquerySqlFieldsNoCache should check for 
cluster active/inactive state
 Key: IGNITE-6932
 URL: https://issues.apache.org/jira/browse/IGNITE-6932
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Taras Ledkov
 Fix For: 2.4


Currently we do not check for this, so operation may hang silently. Let's add a 
check for this before starting query execution. See 
{{IgniteKernal.checkClusterState}} and it's usages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6931) Avoid extra deserialization on index rebuild

2017-11-16 Thread Igor Seliverstov (JIRA)

Igor Seliverstov created IGNITE-6931:


 Summary: Avoid extra deserialization on index rebuild
 Key: IGNITE-6931
 URL: https://issues.apache.org/jira/browse/IGNITE-6931
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: cache, sql
Affects Versions: 2.3
Reporter: Igor Seliverstov
Assignee: Igor Seliverstov
 Fix For: 2.4


Currently on index rebuild we open a cursor over cache keys and for each key 
get a full row instead of using already extracted one. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6930) Non-persistent free lists