[jira] [Created] (IGNITE-7746) Failed to put data into cache if IndexedTypes configured.

Alexey Kuznetsov created IGNITE-7746: Summary: Failed to put data into cache if IndexedTypes configured. Key: IGNITE-7746 URL: https://issues.apache.org/jira/browse/IGNITE-7746 Project: Ignite

Re: Semaphore Stuck when no acquirers to assign permit

Hi Alexey, I already reviewed it, but wanted to see the resolution of IGNITE-6454 first before I merge. Thanks, Vladisav On Fri, Feb 16, 2018 at 12:39 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Hi Vladislav, > > Can you please finalize the review? I would like to include the f

[GitHub] ignite pull request #3374: Ignite-7409 exception handling reworked for resum...

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

[jira] [Created] (IGNITE-7747) WAL manage getAndReserveWalFiles should not throw exception if segments not found

Dmitriy Govorukhin created IGNITE-7747: -- Summary: WAL manage getAndReserveWalFiles should not throw exception if segments not found Key: IGNITE-7747 URL: https://issues.apache.org/jira/browse/IGNITE-7747

[jira] [Created] (IGNITE-7748) MVCC TX Implement TxLog related stuctures

Igor Seliverstov created IGNITE-7748: Summary: MVCC TX Implement TxLog related stuctures Key: IGNITE-7748 URL: https://issues.apache.org/jira/browse/IGNITE-7748 Project: Ignite Issue Type

[GitHub] ignite pull request #3539: IGNITE-7747 An exception should not be throw if s...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3539 IGNITE-7747 An exception should not be throw if segments not found An exception should not be throw if segments not found for getAndReserveWalFiles. Stopped iteration if next segment not

[jira] [Created] (IGNITE-7749) testDiscoCacheReuseOnNodeJoin fails on TC

Pavel Kovalenko created IGNITE-7749: --- Summary: testDiscoCacheReuseOnNodeJoin fails on TC Key: IGNITE-7749 URL: https://issues.apache.org/jira/browse/IGNITE-7749 Project: Ignite Issue Type:

[GitHub] ignite pull request #3540: IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin t...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3540 IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7749 Altern

[jira] [Created] (IGNITE-7750) testMultiThreadStatisticsEnable is flaky on TC

Pavel Kovalenko created IGNITE-7750: --- Summary: testMultiThreadStatisticsEnable is flaky on TC Key: IGNITE-7750 URL: https://issues.apache.org/jira/browse/IGNITE-7750 Project: Ignite Issue T

[GitHub] ignite pull request #3541: IGNITE-7750 Fixed testMultiThreadStatisticsEnable...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3541 IGNITE-7750 Fixed testMultiThreadStatisticsEnable test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7750 Alte

[GitHub] ignite pull request #3499: IGNITE-7253

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

[jira] [Created] (IGNITE-7751) Pages Write Throttle mode doesn't protect from checkpoint buffer overflow

Ivan Rakov created IGNITE-7751: -- Summary: Pages Write Throttle mode doesn't protect from checkpoint buffer overflow Key: IGNITE-7751 URL: https://issues.apache.org/jira/browse/IGNITE-7751 Project: Ignite

[jira] [Created] (IGNITE-7752) Update Ignite KafkaStreamer to use new KafkaConsmer configuration.

Andrew Mashenkov created IGNITE-7752: Summary: Update Ignite KafkaStreamer to use new KafkaConsmer configuration. Key: IGNITE-7752 URL: https://issues.apache.org/jira/browse/IGNITE-7752 Project: I

Ignite Teamcity - actual failing tests (master)

Hi Igniters, I've done experiment on past two weekends to find out which test are currently failing using mass 'RunAll' execution. I created my utility for the analysis of TeamCity DB, which allowed to connect together many results from multiple runs of the same tests. Please find attached summa

Re: Ignite Teamcity - actual failing tests (master)

Hello, Dmitriy Seems like apache mail doesn't allow attachments. Can you enlist failing tests in github gist or some similar service? В Пн, 19/02/2018 в 14:18 +, Dmitry Pavlov пишет: > Hi Igniters, > > I've done experiment on past two weekends to find out which test are > currently failing

Re: Ignite Teamcity - actual failing tests (master)

Hi, Yes, it seems dev list restrics attachment, attached to https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again Direct link: https://cwiki.apache.org/confluence/download/attachments/73631266/Ignite%20Teamcity%20-%20current%20failures.pdf?api=v2 Sincerely, Dmitriy Pavlov

[jira] [Created] (IGNITE-7753) Processors are incorrectly initialized if a node joins during cluster activation

Stanislav Lukyanov created IGNITE-7753: -- Summary: Processors are incorrectly initialized if a node joins during cluster activation Key: IGNITE-7753 URL: https://issues.apache.org/jira/browse/IGNITE-7753

[GitHub] ignite pull request #3521: ignite-7594

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

[GitHub] ignite pull request #3530: IGNITE-7042: Trying to configure scala-test plugi...

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

[jira] [Created] (IGNITE-7754) WAL in LOG_ONLY mode doesn't execute fsync on checkpoint begin

Ilya Lantukh created IGNITE-7754: Summary: WAL in LOG_ONLY mode doesn't execute fsync on checkpoint begin Key: IGNITE-7754 URL: https://issues.apache.org/jira/browse/IGNITE-7754 Project: Ignite

[jira] [Created] (IGNITE-7755) Potentially crash during write cp-***-start.bin can lead to the impossibility of recovering

Dmitriy Govorukhin created IGNITE-7755: -- Summary: Potentially crash during write cp-***-start.bin can lead to the impossibility of recovering Key: IGNITE-7755 URL: https://issues.apache.org/jira/browse/IGNITE

Re: Apache Ignite 2.4 release

Alex, please clarify some of the points data loss because the disk content was shuffled due to an incomplete page > write are you talking about some phase of the checkpointing process? Do you mean that the process just passed over changes to the file but didn't call fsync, thus, offloading this

Re: Apache Ignite 2.4 release

> > Neither Cassandra, nor Mongo or any others claim themselves > to be ACID, so it is not valid to refer to their defaults. This is why I referred to VoltDB as to an example. It supports ACID transactions and persists changes to disk in a mode similar to LOG_ONLY. -- Denis On Sun, Feb 18, 2018

Re: Apache Ignite 2.4 release

On Mon, Feb 19, 2018 at 1:37 AM, Vladimir Ozerov wrote: > Alex, > > You get me right. DEFAULT -> LOG_ONLY doesn't introduce any dramatic > changes when comparing 2.3 to 2.4 - Ignite was unsafe out of the box in > 2.3, and it is unsafe in 2.4 as well. > > The very problem is that we claim ourselve

IgniteDataStreamer silently fails on a server node

Hello, Igniters. While working on IGNITE-7727 I found strange behavior of IgniteDataStreamer: If we have IgniteUuid as an indexed type update silently brokes on a server node. Client doesn't have any notification about fails. All calls of `addData`, `close`, etc. succeed on a client side but fai

[GitHub] ignite pull request #3542: IGNITE-6842

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3542 IGNITE-6842 Test PR for learning contributing processes. - Remove duplicated code stopGrid methods; - Add stopAllGridsSilently method throwing exception in case stop grids fails; - Make

[jira] [Created] (IGNITE-7756) Streamer fails if IgniteUuid is indexed

Nikolay Izhikov created IGNITE-7756: --- Summary: Streamer fails if IgniteUuid is indexed Key: IGNITE-7756 URL: https://issues.apache.org/jira/browse/IGNITE-7756 Project: Ignite Issue Type: Bu

Ignite Thin clients for Node.js, Python, PHP

Hi All! Let us join the party, please ;) As we see, there is Binary Client Protocol to communicate with Ignite cluster and a concept of Thin (lightweight) client. If there are no objections or duplicated plans, we would like to develop Thin Client libs for: - Node.js - Python - PHP Please

[Webinar] Caching technologies evolution

Igniters, Curious to see how the caching technologies evolved over the time? Where Ignite, Redis or Memcached fits? Join my tomorrow webinar at 11.00 PT or bookmark and get a recording later: Redis Replaced: Why Companies Now Choose Apache® Ignite™ to Improve Application Speed and Scale

Re: Ignite Thin clients for Node.js, Python, PHP

Hi Alexey and welcome to all of you! Look forward to seeing the clients in Ignite codebase ;) Granted contributors access to all of you in JIRA. Feel free to assign existing tickets to yourself or create new ones. However, before you're getting down to the implementation, please share the design

Re: Ignite Thin clients for Node.js, Python, PHP

Alexey, Ekaterina, Pavel, These resources will be useful for you: - Thin client protocol spec - .NET thin client code

Re: Ignite Thin clients for Node.js, Python, PHP

Also, we could have a Hangouts call or something to share thin client development experience. You can reach me at kukushkinale...@gmail.com.

Apply for a Loan Access Fund

Constant Contact Do you need a loan,You want to pay off bills, Expand your business? Look no further we offer all kinds of loans both long and short term loan. Multi-component loans: We specialize in investments in private sectors within our financial Investment services are M&A development and

[jira] [Created] (IGNITE-7757) Unable to create a new cache via REST

Pavel Konstantinov created IGNITE-7757: -- Summary: Unable to create a new cache via REST Key: IGNITE-7757 URL: https://issues.apache.org/jira/browse/IGNITE-7757 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7758) Update REST documentation

Alexey Kuznetsov created IGNITE-7758: Summary: Update REST documentation Key: IGNITE-7758 URL: https://issues.apache.org/jira/browse/IGNITE-7758 Project: Ignite Issue Type: Task

Re: IgniteDataStreamer silently fails on a server node

Nikolay, Does this exception happen because IgniteUuid class is not correctly handled? If that's the case, we should fix it. Would be great if you could do it. As far as propagating exceptions, addData(...) is asynchronous operation and returns IgniteFuture. The exception should be propagated to

[jira] [Created] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi

Roman Guseinov created IGNITE-7759: -- Summary: Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi Key: IGNITE-7759 URL: https://issues.apache.org/jira/browse/IGNITE-7759

[jira] [Created] (IGNITE-7760) Handle FS hangs

Alexander Belyak created IGNITE-7760: Summary: Handle FS hangs Key: IGNITE-7760 URL: https://issues.apache.org/jira/browse/IGNITE-7760 Project: Ignite Issue Type: Improvement Co