[jira] [Created] (IGNITE-7995) Assertion on GridGhtPartitionDemandMessage

Alexander Belyak created IGNITE-7995: Summary: Assertion on GridGhtPartitionDemandMessage Key: IGNITE-7995 URL: https://issues.apache.org/jira/browse/IGNITE-7995 Project: Ignite Issue

[jira] [Created] (IGNITE-7996) Web console: move cluster configuration form templates

Ilya Borisov created IGNITE-7996: Summary: Web console: move cluster configuration form templates Key: IGNITE-7996 URL: https://issues.apache.org/jira/browse/IGNITE-7996 Project: Ignite

[GitHub] ignite pull request #3641: Keep marshaller mappings in consistent state: bac...

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

[GitHub] ignite pull request #3650: IGNITE-7976 Normalize query entites when dynamic ...

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

[GitHub] ignite pull request #3629: IGNITE-7887: MultiSVM - added Model, Trainer and ...

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

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Val, If a storage is in corrupted state, does it mean that it needs to be completely removed and cluster needs to be restarted without data? Yes, there's a chance that in LOG_ONLY all local data will be lost, but only in *power loss**/ OS crash* case. kill -9, JVM crash, death of critical

Re: Apache Ignite nightly release builds

Not yet. Project is still under development, I will pass build to community after settling corresponding permissions and receiving QA report. Also — it is time to rise a matter about adding nightly build link to out documentation (somewhere here [1]). Pavel, could you help? [1]

[jira] [Created] (IGNITE-7998) SQL: Improve MVCC vacuum performance by iterating over data pages instead of cache tree.

Roman Kondakov created IGNITE-7998: -- Summary: SQL: Improve MVCC vacuum performance by iterating over data pages instead of cache tree. Key: IGNITE-7998 URL: https://issues.apache.org/jira/browse/IGNITE-7998

[GitHub] ignite pull request #3662: IGNITE-6113 Backport to 2.4.3.b1

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3662 IGNITE-6113 Backport to 2.4.3.b1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13616 Alternatively you can

[GitHub] ignite pull request #3655: IGNITE-7984

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

Re: Stop nodes after test by default - IGNITE-6842

Dmitriy, thank you for review. This fix should do our tests more stable. Nikolay, could you please merge? вт, 20 мар. 2018 г. в 11:49, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: > Looks good for me, please merge. > > 19 мар. 2018 г. 3:22 ПП пользователь "Dmitry Pavlov" < >

Re: Apache Ignite nightly release builds

Prepared prototype build, passed for some preliminary testing. Currently it will provide the following artifacts: * sources * fabric binary * hadoop binary * maven staging * nuget staging Will keep community informed about progress. > On 14 Mar 2018, at 13:13, vveider

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

If java runs oome then you cannot guarantee anything. Including calling runtime.halt(). My point is about consistent approach throughout the project. I think developing new mechanism with separate interface is incorrect. Yakov

[GitHub] ignite pull request #3657: IGNITE-7888: Added support for SQL_ATTR_LOGIN_TIM...

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

[GitHub] ignite pull request #3661: IGNITE-7993 Striped pool can't be disabled

GitHub user gromtech opened a pull request: https://github.com/apache/ignite/pull/3661 IGNITE-7993 Striped pool can't be disabled Restored the capability to disable striped pool You can merge this pull request into a Git repository by running: $ git pull

Re: Stop nodes after test by default - IGNITE-6842

Looks good for me, please merge. 19 мар. 2018 г. 3:22 ПП пользователь "Dmitry Pavlov" написал: > I agree it is important, I'm going to do a review, but do not have time > slot to do. > > Who could pick up this review? > > Dmitriy G., could I ask you? > > пн, 19 мар. 2018

Re: Apache Ignite nightly release builds

Thank you, Petr, could you share link to run config? Sincerely, Dmitriy Pavlov вт, 20 мар. 2018 г. в 12:17, Petr Ivanov : > Prepared prototype build, passed for some preliminary testing. > Currently it will provide the following artifacts: > * sources > * fabric binary >

[GitHub] ignite pull request #3597: IGNITE-7869 Dynamic start cache by stored cache d...

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

Re: 2 phase waiting for partitions release

Hi Igniters, I prefer option 1 because throwing any exceptions is bad for product usability. I think we should do this way only if it is unavoidable. In the same time it would be good if we could provide so reliable but optimized (from the point of view of messages count) solution. Please share

[jira] [Created] (IGNITE-7999) Enhance performance of the thin JDBC streaming mode

Taras Ledkov created IGNITE-7999: Summary: Enhance performance of the thin JDBC streaming mode Key: IGNITE-7999 URL: https://issues.apache.org/jira/browse/IGNITE-7999 Project: Ignite Issue

RE: Ignite Direct I/O plugin description added to wiki

Denis, Thanks for the clarification on read-intensive workloads not being suitable for Direct IO. As a counterpoint to that, I would have thought the working set represented by the in-memory data held by the Ignite node would be significantly larger than the OS page cache which should mean the

Re: Ignite Direct I/O plugin description added to wiki

*Dmitriy*, thanks. Astonishing job! We'll add a section to the durable memory tuning page and refer to the wiki for more details: https://issues.apache.org/jira/browse/IGNITE-7466 Please clarify the following: > Direct I/O mode can't be enabled for Write Ahead Log files. However, when > working

Ignite Direct I/O plugin description added to wiki

Hi Igniters, I've added description of new plugin for Direct I/O for native persistence ( https://issues.apache.org/jira/browse/IGNITE-6341) to wiki https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-DirectI/O

Re: Ignite Direct I/O plugin description added to wiki

Thanks Dmitry, awesome work! On Wed, Mar 21, 2018 at 12:21 AM, Dmitry Pavlov wrote: > Hi Igniters, > > I've added description of new plugin for Direct I/O for native persistence > ( > https://issues.apache.org/jira/browse/IGNITE-6341) to wiki >

Re: Move documentation from readme.io to GitHub pages

I looked into Docusaurus and GitBook. I liked Docusaurus better because it allows publishing to github pages or other static files hosts, and various other features. My findings are mentioned in the ticket - https://issues.apache.org/jira/browse/IGNITE-7595 . On Fri, Feb 2, 2018 at 2:42 PM, Denis

RE: Ignite Direct I/O plugin description added to wiki

Looks good! Is there any reason why this should not be a default setting if it gracefully downgrades to non-Direct IO if not supported by the OS? Thanks, Raymond. -Original Message- From: Dmitriy Setrakyan [mailto:dsetrak...@apache.org] Sent: Wednesday, March 21, 2018 10:23 AM To: dev

[jira] [Created] (IGNITE-8002) Authentication: add to REST support of new authentication

Alexey Kuznetsov created IGNITE-8002: Summary: Authentication: add to REST support of new authentication Key: IGNITE-8002 URL: https://issues.apache.org/jira/browse/IGNITE-8002 Project: Ignite

Re: Move documentation from readme.io to GitHub pages

Copied from the ticket. *Feature* *Docusaurus* *GitBook* *Free* Yes (FaceBook open source project) Yes (Free version only allows 5 contributors) *Setup and Installation* Easy installation and configuration steps. Initial setup is easy; Need to look around for customization. *Standard

[jira] [Created] (IGNITE-8001) Web console: show more userfriendly error instead of 'Internal error'

Pavel Konstantinov created IGNITE-8001: -- Summary: Web console: show more userfriendly error instead of 'Internal error' Key: IGNITE-8001 URL: https://issues.apache.org/jira/browse/IGNITE-8001

Re: readme.io weird interface element

Hi Petr, Denis, Sorry missed the message. Petr, please feel free to create a ticket. Thanks, -Prachi On Mon, Mar 19, 2018 at 8:24 PM, Petr Ivanov wrote: > Prachi, has you filed the ticket or should I create one? > > > > > On 15 Mar 2018, at 23:07, Denis Magda

[jira] [Created] (IGNITE-8000) Implicit transactions may not finish properly on unstable topology.

Alexei Scherbakov created IGNITE-8000: - Summary: Implicit transactions may not finish properly on unstable topology. Key: IGNITE-8000 URL: https://issues.apache.org/jira/browse/IGNITE-8000

[GitHub] ignite pull request #3663: ignite-7989 returned ConcurrentHashMap8 for backw...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/3663 ignite-7989 returned ConcurrentHashMap8 for backward compatibi… …lity You can merge this pull request into a Git repository by running: $ git pull