[jira] [Created] (IGNITE-7911) TX SQL: restrict usages of unsupported APIs and configuration parameters

Vladimir Ozerov created IGNITE-7911: --- Summary: TX SQL: restrict usages of unsupported APIs and configuration parameters Key: IGNITE-7911 URL: https://issues.apache.org/jira/browse/IGNITE-7911

Re: Data eviction/expiration from Ignite persistence

Hi Denis, yes, this is about PDS + entry expiration (TTL). Please note there is second issue, than is visible by user https://issues.apache.org/jira/browse/IGNITE-6964 'transfer of old entries to new storage' means DB entries migration from old format to new. We defenetely should have PDS

Re: checksum file Release Distribution Policy

Should we manually delete MD5 hash sums from current release (2.4) or release procedure modification in 2.5 will be enough? > On 7 Mar 2018, at 21:29, Dmitriy Setrakyan wrote: > > On Tue, Mar 6, 2018 at 8:52 PM, Petr Ivanov wrote: > >>

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Correction: " Apache Ignite *2.4.0* release (RC1) has been accepted." On Mon, Mar 12, 2018 at 10:51 AM, Vladimir Ozerov wrote: > Igniters, > > Apache Ignite 2.3.0 release (RC1) has been accepted. > > 5 "+1" binding votes received: > - Alexey Goncharuk > - Alexey Kuznetsov

Re: Fwd: [jira] [Created] (IGNITE-7909) Java code examples are needed for Spark Data Frames.

I see now. Thank you for clarification. пн, 12 мар. 2018 г., 13:12 Nikolay Izhikov : > Hello, Dmitry. > > Examples I create written in scala [1]. > > The goal of task is to rewrite these examples in java. > > [1] >

[jira] [Created] (IGNITE-7912) control.sh script should show used WAL-segments

Sergey Filatov created IGNITE-7912: -- Summary: control.sh script should show used WAL-segments Key: IGNITE-7912 URL: https://issues.apache.org/jira/browse/IGNITE-7912 Project: Ignite Issue

Re: Fwd: [jira] [Created] (IGNITE-7909) Java code examples are needed for Spark Data Frames.

Hello, Dmitry. Examples I create written in scala [1]. The goal of task is to rewrite these examples in java. [1] https://github.com/apache/ignite/blob/master/examples/src/main/spark/org/apache/ignite/examples/spark/IgniteDataFrameExample.scala В Пн, 12/03/2018 в 10:07 +, Dmitry Pavlov

IEP-14: Ignite failures handling (Discussion)

Igniters! We are working on proposal described in IEP-14 Ignite failures handling [1] and it's time to discuss it with community (although it was necessary to do this before). Most important question: what should be default behaviour in case of failure? There are 4 actions: 1. Restart JVM

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

Igniters, Apache Ignite 2.3.0 release (RC1) has been accepted. 5 "+1" binding votes received: - Alexey Goncharuk - Alexey Kuznetsov - Anton Vinogradov - Denis Magda - Pavel Tupitsyn Vote thread: *http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html

Fwd: [jira] [Created] (IGNITE-7909) Java code examples are needed for Spark Data Frames.

Hi Nikolay, Сan your examples, that you have done recently, come up as a solution to this ticket? Sincerely, Dmitriy Pavlov -- Forwarded message - From: Akmal Chaudhri (JIRA) Date: вс, 11 мар. 2018 г. в 2:24 Subject: [jira] [Created] (IGNITE-7909) Java code

[GitHub] ignite pull request #3620: Keep marshaller mappings in consistent state

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/3620 Keep marshaller mappings in consistent state You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7794

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hello, Denis. Did you give me the permissions? Seems, I still can't create IEP on the IGNITE Wiki. https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals В Вт, 06/03/2018 в 08:55 +0300, Nikolay Izhikov пишет: > Thank you, it's - nizhikov > > В Пн, 05/03/2018 в 15:09 -0800, Denis

Re: IEP-14: Ignite failures handling (Discussion)

To my mind, the default action should be as severe as possible, since we deal with critical errors, that is, entire JVM termination. In the case of some custom setup (e.g. different cluster nodes in one JVM) failure response action should be configured explicitly. 2018-03-12 12:32 GMT+03:00

Re: IEP-14: Ignite failures handling (Discussion)

Hi Andrey, Igniters, Thank you for starting this topic, because this is really important decision. JVM termination in case Ignite is started within application server with other application will kill all services started. So I suggest this option is not default. We can add this option

Re: Partition recovery issue on partition loss.

Hi Andrey, I remember some issue was also found in tests: https://issues.apache.org/jira/browse/IGNITE-5302 Is this a consequence of the same problem? Sincerely, Dmitriy Pavlov пн, 12 мар. 2018 г. в 13:34, Andrey Mashenkov : > Hi Igniters, > > I've found we no

[jira] [Created] (IGNITE-7915) Add transaction debugging support in JMX

Alexei Scherbakov created IGNITE-7915: - Summary: Add transaction debugging support in JMX Key: IGNITE-7915 URL: https://issues.apache.org/jira/browse/IGNITE-7915 Project: Ignite Issue

[GitHub] ignite pull request #3607: IGNITE-7876: Adopt SVM Binary Classification to t...

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

Partition recovery issue on partition loss.

Hi Igniters, I've found we no documentation how user can recover cache from cacheStore in case of partition loss. Ignite provides some instruments (methods and events) that should help user to solve this problem, but looks like these instruments have an architecture lack. The first one is an

[jira] [Created] (IGNITE-7918) Huge memory leak when data streamer used together with local cache

Zbyszek B created IGNITE-7918: - Summary: Huge memory leak when data streamer used together with local cache Key: IGNITE-7918 URL: https://issues.apache.org/jira/browse/IGNITE-7918 Project: Ignite

Re: Code inspection

Hi Dmitriy, would you pick up this activity? Sincerely, Dmitriy Pavlov вт, 6 мар. 2018 г. в 14:09, Dmitry Pavlov : > What I can suggest now it is to take XML file with existing as is from > previous topic (I remember someone in community already prepared settings) > and

Re: SQL docs: Update query with order by clause

ORDER BY is ignored at the moment. It will work are some point in future. On Thu, Mar 8, 2018 at 10:17 PM, Denis Magda wrote: > Hi Sergey, > > I’ll let our SQL experts to step in and clarify. > > Vladimir, Alex Paschenko, please chime in. > > Denis > > > On Sunday, March 4,

Re: .NET Long Running Test execution timeout

Hi Pavel, Thanks to Vitaliy Osipov multicast is prohibited on TeamCity agents, there should no interference anymore. Could you please return test to code (18c6b4a5d079874e9c156fa39564970ad3c31914) ? I'll check if issue https://issues.apache.org/jira/browse/IGNITE-7878 is reproducible and close

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Hi Vladimir, I see the link for 2.4.0 on https://ignite.apache.org/download.cgi#binaries, but it does not work. On Mon, Mar 12, 2018 at 10:55 AM, Vladimir Ozerov wrote: > Correction: " Apache Ignite *2.4.0* release (RC1) has been accepted." > > On Mon, Mar 12, 2018 at

[jira] [Created] (IGNITE-7916) GA Grid examples should be ready for auto run on TeamCity

Yury Babak created IGNITE-7916: -- Summary: GA Grid examples should be ready for auto run on TeamCity Key: IGNITE-7916 URL: https://issues.apache.org/jira/browse/IGNITE-7916 Project: Ignite Issue

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Correct, it is a matter of time. Download links already work on my side [1]. [1] http://mirror.linux-ia64.org/apache/ignite/2.4.0/ On Mon, Mar 12, 2018 at 1:29 PM, Petr Ivanov wrote: > Link to 2.4.0 is pointing to RBC mirror, not Apache Dist itself. > > I do not know how

[GitHub] ignite pull request #3621: Ignite-2.4.2-p5

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3621 Ignite-2.4.2-p5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.2-p5 Alternatively you can review and apply

[jira] [Created] (IGNITE-7913) Current implementation of Internal Diagnostics may cause OOM on server nodes.

Alexei Scherbakov created IGNITE-7913: - Summary: Current implementation of Internal Diagnostics may cause OOM on server nodes. Key: IGNITE-7913 URL: https://issues.apache.org/jira/browse/IGNITE-7913

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Link to 2.4.0 is pointing to RBC mirror, not Apache Dist itself. I do not know how often RBC updates its mirror, but I think we have to devise better solution for pointing to fresh release artifacts. > On 12 Mar 2018, at 13:24, Pavel Tupitsyn wrote: > > Hi Vladimir, >

[GitHub] ignite pull request #3613: IGNITE-7773 Add 'rebalanceClearingPartitionsLeft'...

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

2 Apache Ignite talks this week

Igniters, Thought I’d share a couple of Apache Ignite talks happening this week. Apache Ignite evangelist Akmal Chaudhri is in Portland, Oregon today for the OpenIoTSummit North America conference. The symposium, which runs through Wednesday, is designed for developers and architects working

MD5 sums in the releases

Please be aware about the changes in the Foundation's release policy [1] * SHOULD NOT supply a MD5 checksum file [1] https://www.apache.org/dev/release-distribution#sigs-and-sums -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer:

[GitHub] ignite pull request #3624: IGNITE-6827

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/3624 IGNITE-6827 IGNITE-6827 Configurable rollback for long running transactions before partition exchange. You can merge this pull request into a Git repository by running: $ git pull

Re: .NET Long Running Test execution timeout

Reverted that commit. On Mon, Mar 12, 2018 at 2:34 PM, Dmitry Pavlov wrote: > Hi Pavel, > > Thanks to Vitaliy Osipov multicast is prohibited on TeamCity agents, there > should no interference anymore. > > Could you please return test to code >

[GitHub] ignite pull request #3622: IGNITE-7770 For TC tests only

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3622 IGNITE-7770 For TC tests only You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-7770-0 Alternatively

Re: .NET Long Running Test execution timeout

Thank you! I'll start the builds later. пн, 12 мар. 2018 г. в 16:23, Pavel Tupitsyn : > Reverted that commit. > > On Mon, Mar 12, 2018 at 2:34 PM, Dmitry Pavlov > wrote: > >> Hi Pavel, >> >> Thanks to Vitaliy Osipov multicast is prohibited on

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

NuGet packages uploaded: https://www.nuget.org/packages?q=Apache.Ignite Thanks, Pavel On Mon, Mar 12, 2018 at 1:54 PM, Vladimir Ozerov wrote: > Correct, it is a matter of time. Download links already work on my side > [1]. > > [1]

Re: Transparent Data Encryption (TDE) in Apache Ignite

Nikolay, please try on more time. -- Denis On Sun, Mar 11, 2018 at 11:20 PM, Nikolay Izhikov wrote: > Hello, Denis. > > Did you give me the permissions? > Seems, I still can't create IEP on the IGNITE Wiki. > >

[jira] [Created] (IGNITE-7920) Research local crash recovery speed after stop in the middle of checkpoint

Dmitriy Pavlov created IGNITE-7920: -- Summary: Research local crash recovery speed after stop in the middle of checkpoint Key: IGNITE-7920 URL: https://issues.apache.org/jira/browse/IGNITE-7920

[jira] [Created] (IGNITE-7922) Rewrite LruEvictionPolicy and get rid of ConcurrentLinkedDeque8 usages

Andrey Gura created IGNITE-7922: --- Summary: Rewrite LruEvictionPolicy and get rid of ConcurrentLinkedDeque8 usages Key: IGNITE-7922 URL: https://issues.apache.org/jira/browse/IGNITE-7922 Project: Ignite

[jira] [Created] (IGNITE-7921) Rewrite FifoEvictionPolicy and get rid of ConcurrentLinkedDeque8 usages

Andrey Gura created IGNITE-7921: --- Summary: Rewrite FifoEvictionPolicy and get rid of ConcurrentLinkedDeque8 usages Key: IGNITE-7921 URL: https://issues.apache.org/jira/browse/IGNITE-7921 Project:

[jira] [Created] (IGNITE-7923) Rewrite IgfsPerBlockLruEvictionPolicy and get rid of ConcurrentLinkedDeque8 usage

Andrey Gura created IGNITE-7923: --- Summary: Rewrite IgfsPerBlockLruEvictionPolicy and get rid of ConcurrentLinkedDeque8 usage Key: IGNITE-7923 URL: https://issues.apache.org/jira/browse/IGNITE-7923

Re: IEP-14: Ignite failures handling (Discussion)

Guys, I would make a decision depending on a type of the problematic node: - If it's a *server node*, then let's kill the process simply because the node usually owns the whole process. Don't see a practical reason why a user wants to run 2 server nodes in a single process. - If it's

[jira] [Created] (IGNITE-7925) Rewrite MemoryEventStorageSpi and remove ConcurrentLinkedDeque8 usages

Andrey Gura created IGNITE-7925: --- Summary: Rewrite MemoryEventStorageSpi and remove ConcurrentLinkedDeque8 usages Key: IGNITE-7925 URL: https://issues.apache.org/jira/browse/IGNITE-7925 Project: Ignite

Re: Trimming exceptions in IgniteUtils::cast

Generally, I think we should not trim any exceptions, because this way we can unexpectedly remove useful information. Do we know what was the original reasoning behind this logic? -Val On Mon, Mar 12, 2018 at 3:57 AM, Stanislav Lukyanov wrote: > Hi, > >

[jira] [Created] (IGNITE-7924) Rewrite IgfsServer and remove ConcurrentLinkedDeque8 usages

Andrey Gura created IGNITE-7924: --- Summary: Rewrite IgfsServer and remove ConcurrentLinkedDeque8 usages Key: IGNITE-7924 URL: https://issues.apache.org/jira/browse/IGNITE-7924 Project: Ignite

Re: Data eviction/expiration from Ignite persistence

Val, Yes, the entries will be removed from both memory and persistence. 2018-03-12 19:20 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Alex, > > What is behavior going to be after IGNITE-5874 is fixed? Will expired entry > be removed from both memory and persistence? > >

Re: Data eviction/expiration from Ignite persistence

Alex, What is behavior going to be after IGNITE-5874 is fixed? Will expired entry be removed from both memory and persistence? -Val On Sat, Mar 10, 2018 at 12:06 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > The ticket [1] is in patch available state looks good, the only thing

[GitHub] ignite pull request #3623: IGNITE-7765 ensure that walSegmentSize doesn't ov...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3623 IGNITE-7765 ensure that walSegmentSize doesn't overflow You can merge this pull request into a Git repository by running: $ git pull https://github.com/ivandasch/ignite ignite-7765

[jira] [Created] (IGNITE-7914) Add transaction debugging support in control.sh

Alexei Scherbakov created IGNITE-7914: - Summary: Add transaction debugging support in control.sh Key: IGNITE-7914 URL: https://issues.apache.org/jira/browse/IGNITE-7914 Project: Ignite

Trimming exceptions in IgniteUtils::cast

Hi, IgniteUtils::cast method is used to cast an exception to IgniteCheckedException. It is done by trimming the top exceptions in the trace until we find IgniteCheckedException, or until we’ve found the last one. As a result, IgniteUtils::cast generally can trim the whole stack trace but the

[jira] [Created] (IGNITE-7917) Thin client: document missing data types

Vladimir Ozerov created IGNITE-7917: --- Summary: Thin client: document missing data types Key: IGNITE-7917 URL: https://issues.apache.org/jira/browse/IGNITE-7917 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7919) Handle IO errors while checkpointing, rework.

Stanilovsky Evgeny created IGNITE-7919: -- Summary: Handle IO errors while checkpointing, rework. Key: IGNITE-7919 URL: https://issues.apache.org/jira/browse/IGNITE-7919 Project: Ignite

Re: SQL docs: Update query with order by clause

Removed ORDER BY from the UPDATE syntax. Thanks for the clarification. -- Denis On Mon, Mar 12, 2018 at 4:57 AM, Vladimir Ozerov wrote: > ORDER BY is ignored at the moment. It will work are some point in future. > > On Thu, Mar 8, 2018 at 10:17 PM, Denis Magda

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Released RPM installation section on the downloads page: https://ignite.apache.org/download.cgi#rpm-package *Petr*, please double check that the section and the readme getting started look good: https://apacheignite.readme.io/docs/getting-started#section-rpm-package-installation *Mauricio*,

Re: Partition recovery issue on partition loss.

Just in case here is you can find the present documentation: https://apacheignite.readme.io/docs/cache-modes#partition-loss-policies Let us know what needs to be updated once the issues reported by you are addressed. -- Denis On Mon, Mar 12, 2018 at 3:33 AM, Andrey Mashenkov <

Re: Data eviction/expiration from Ignite persistence

Alexey, Dmitriy, What would be the configuration parameter that defines if the eviction should happen in the in-memory layer only or in both memory and disk? -- Denis On Mon, Mar 12, 2018 at 9:22 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Val, > > Yes, the entries will be

[jira] [Created] (IGNITE-7927) Web console: failed to execute query in demo

Pavel Konstantinov created IGNITE-7927: -- Summary: Web console: failed to execute query in demo Key: IGNITE-7927 URL: https://issues.apache.org/jira/browse/IGNITE-7927 Project: Ignite

Re: IEP-14: Ignite failures handling (Discussion)

On Tue, Mar 13, 2018 at 1:18 AM, Andrey Kornev wrote: > I believe the only reasonable way to handle a critical system failure (as > it is defined in the IEP) is a JVM halt (not a graceful exit/shutdown!). > The sooner - the better, lesser impact. There’s simply no way

Atomic sequence and topology exception

Igniters! I have a few questions related to a replicated atomic sequence and an topology exception. In my case after one server node has left cluster, on a client node the execution of the *IgniteAtomicSequence#incrementAndGet()* throws exception:

[jira] [Created] (IGNITE-7926) Web console: demo faled to start under java 9

Pavel Konstantinov created IGNITE-7926: -- Summary: Web console: demo faled to start under java 9 Key: IGNITE-7926 URL: https://issues.apache.org/jira/browse/IGNITE-7926 Project: Ignite

Re: Data eviction/expiration from Ignite persistence

To be honest, I am not clear how this would be implemented. Currently, we keep TTL map in memory and it fits in memory. However, if we start tracking entries on disk, the TTL map will grow too large and may not fit in memory any longer. Can someone explain how this will be handled? D. On Mon,

Re: SQL docs: Update query with order by clause

Can we at least print out a warning that the ORDER BY is being ignored? To avoid log flooding, we should only print it out the first time we encounter this situation. D. On Mon, Mar 12, 2018 at 1:10 PM, Denis Magda wrote: > Removed ORDER BY from the UPDATE syntax. Thanks for

Re: IEP-14: Ignite failures handling (Discussion)

Dmitriy, Ignite client node is usually used in the embedded mode. By killing the whole process, the node is running in, we're going to kill the entire application. That doesn't sound like a good plan. That's why my suggestion is to try to kill the node somehow instead rather than the whole

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

The latest 2.4 documentation is now available on readme.io - https://apacheignite.readme.io/docs/ -Prachi On Mon, Mar 12, 2018 at 7:36 AM, Pavel Tupitsyn wrote: > NuGet packages uploaded: https://www.nuget.org/packages?q=Apache.Ignite > > Thanks, > Pavel > > > On Mon,

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Thanks Mauricio, merged the patch! Overall, the docs were released. Vladimir, let me know when the rest of post-process steps are completed. I put together a short blog post and announce the release. -- Denis On Mon, Mar 12, 2018 at 2:25 PM, Mauricio Stekl wrote: > Hi

Re: IEP-14: Ignite failures handling (Discussion)

Denis, what is the difference between killing the process and killing the node and the process? D. On Mon, Mar 12, 2018 at 12:03 PM, Denis Magda wrote: > Guys, > > I would make a decision depending on a type of the problematic node: > >- If it's a *server node*, then

Re: IEP-14: Ignite failures handling (Discussion)

On Mon, Mar 12, 2018 at 5:12 PM, Denis Magda wrote: > Dmitriy, > > Ignite client node is usually used in the embedded mode. By killing the > whole process, the node is running in, we're going to kill the entire > application. That doesn't sound like a good plan. That's why my

Re: Data eviction/expiration from Ignite persistence

Denis, I suppose there is no configuration will be required. If TTL configured entry will be removed from disk & memory both. SIncerely, Dmitriy Pavlov пн, 12 мар. 2018 г. в 23:32, Denis Magda : > Alexey, Dmitriy, > > What would be the configuration parameter that defines

Re: checksum file Release Distribution Policy

If it's not late, I would remove it manually from 2.4 and alter the release procedures. See a respective message from Cos: http://apache-ignite-developers.2346864.n4.nabble.com/MD5-sums-in-the-releases-td27901.html -- Denis On Sun, Mar 11, 2018 at 11:00 PM, Petr Ivanov

Re: Data eviction/expiration from Ignite persistence

Dmitriy, It will break the current default behavior when data is evicted from the memory only, and I would disagree that it's a right decision overall. There are many scenarios when users need to have the eviction in the memory layer and preserve data on disk for later usage. So, can we keep