Alexander Belyak created IGNITE-7995:
Summary: Assertion on GridGhtPartitionDemandMessage
Key: IGNITE-7995
URL: https://issues.apache.org/jira/browse/IGNITE-7995
Project: Ignite
Issue Typ
Github user dmekhanikov closed the pull request at:
https://github.com/apache/ignite/pull/3641
---
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
Issue
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 https://github.com/grid
Ilya Kasnacheev created IGNITE-7997:
---
Summary: Ability to use different SSL trust store password and
private key password
Key: IGNITE-7997
URL: https://issues.apache.org/jira/browse/IGNITE-7997
Proj
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 г. в 15:13, Maxim Muzafa
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" <
> dpavlov@g
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 wrote:
>
> Prepared
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3650
---
Github user akalash closed the pull request at:
https://github.com/apache/ignite/pull/3597
---
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 user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3657
---
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
> * hadoop binary
> *
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 r
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/3655
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3629
---
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] https://ignite.
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 sys
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
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 T
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
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 https://github.com/gridgain/apache-ignite
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
Project
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 wrote:
> >
> > Please create a t
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
SIncerely
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
> https://cwiki.apache.org/confluence/display/IGNITE
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
S
*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 w
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
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
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
Pro
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
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 Mark
Does docusaurus work with GitHub only, or with Git in general? In Apache
GitHub is used as a mirror of an internal Git repo, which is the primary
source of data.
D.
Igniters,
I prepared rather important patch [1] related to grid stability and need a
review and some help to finish it.
Semyon Boikov, could you please take a look on patch code ? [2]
Pavel Tupitsyn, could you lend a hand to help completing .NET part (two new
public API methods are added as a pa
35 matches
Mail list logo
