Hi Denis!
>> If to assume that Ignite 2.7 gets released in September, what else would you
>> be able to complete by that time?
The following tasks will be completed by September:
https://issues.apache.org/jira/browse/IGNITE-8361 - Use discovery
messages for service deployment
https://issues.apac
Puviarasu created IGNITE-8825:
-
Summary: Ignite - Configuration for IGFS
Key: IGNITE-8825
URL: https://issues.apache.org/jira/browse/IGNITE-8825
Project: Ignite
Issue Type: Test
Repo
Yury Babak created IGNITE-8826:
--
Summary: Add missed licence to pom file
Key: IGNITE-8826
URL: https://issues.apache.org/jira/browse/IGNITE-8826
Project: Ignite
Issue Type: Bug
Compone
GitHub user ybabak opened a pull request:
https://github.com/apache/ignite/pull/4222
Ignite 8826: added missed licences
fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8826
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4222
---
Denis,
Yes, in principle we can extend it. We are going to implement it in
subsequent phases of this IEP.
On Tue, Jun 19, 2018 at 4:30 AM, Dmitriy Setrakyan
wrote:
> On Mon, Jun 18, 2018 at 11:07 AM, Denis Magda wrote:
>
> > Folks,
> >
> > Feel that this functionality can be extended to the au
Dmitriy Govorukhin created IGNITE-8827:
--
Summary: Disable WAL during apply updates on recovery
Key: IGNITE-8827
URL: https://issues.apache.org/jira/browse/IGNITE-8827
Project: Ignite
Iss
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4223
Ignite-gg-13938
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13938
Alternatively you can review
Github user x-kreator closed the pull request at:
https://github.com/apache/ignite/pull/4220
---
Github user x-kreator closed the pull request at:
https://github.com/apache/ignite/pull/4216
---
Hi, Igniters!
During test bug fixing [1], I stumbled on the following issue:
When we perform cache store loading and start several nodes
simulateneously, some entries might not be loaded into cache.
Entry is loaded in `GridDhtCacheAdapter#loadEntry`, but it fails on
`ctx.group().topology().localP
Hello, Aleksey.
By "cache store" you mean 3-d party cache store [1] ?
https://apacheignite.readme.io/docs/3rd-party-store
В Вт, 19/06/2018 в 13:10 +0300, Aleksey Kuznetsov пишет:
> Hi, Igniters!
>
> During test bug fixing [1], I stumbled on the following issue:
> When we perform cache store loa
Hi, Nikolay.
Yes.
вт, 19 июн. 2018 г. в 13:18, Nikolay Izhikov :
> Hello, Aleksey.
>
> By "cache store" you mean 3-d party cache store [1] ?
>
> https://apacheignite.readme.io/docs/3rd-party-store
>
> В Вт, 19/06/2018 в 13:10 +0300, Aleksey Kuznetsov пишет:
> > Hi, Igniters!
> >
> > During test
Sergey Chugunov created IGNITE-8828:
---
Summary: Detecting and stopping unresponsive nodes during
Partition Map Exchange
Key: IGNITE-8828
URL: https://issues.apache.org/jira/browse/IGNITE-8828
Project
Vladislav Pyatkov created IGNITE-8829:
-
Summary: Some configuration properties of TcpCommunicationSpi does
not annotated appropriately
Key: IGNITE-8829
URL: https://issues.apache.org/jira/browse/IGNITE-8829
Sergey Chugunov created IGNITE-8830:
---
Summary: Non-coordinator node unable to finish local exchange
should detect it and stop
Key: IGNITE-8830
URL: https://issues.apache.org/jira/browse/IGNITE-8830
Alexey Stelmak created IGNITE-8831:
--
Summary: MarshallerMappingFileStore: Incorrect locks on files
Key: IGNITE-8831
URL: https://issues.apache.org/jira/browse/IGNITE-8831
Project: Ignite
Iss
GitHub user SpiderRus opened a pull request:
https://github.com/apache/ignite/pull/4224
MarshallerMappingFileStore: Incorrect locks on files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8831
Alte
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4225
IGNITE-8827 disable WAL logging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8827
Alternatively you
Sergey Chugunov created IGNITE-8832:
---
Summary: Detecting hanging of coordinator during processing local
partition maps messages
Key: IGNITE-8832
URL: https://issues.apache.org/jira/browse/IGNITE-8832
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4206
---
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/4226
IGNITE-4939 Receive event before cache initialized fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4939
Alt
Andrey Aleksandrov created IGNITE-8833:
--
Summary: IgniteCache.isLocalLocked method has unexpected behivior
in case of several nodes started in one JVM in different threads
Key: IGNITE-8833
URL: https://issues
Anton Kurbanov created IGNITE-8834:
--
Summary: SqlQuery not throwing exception after partition loss
events
Key: IGNITE-8834
URL: https://issues.apache.org/jira/browse/IGNITE-8834
Project: Ignite
Pavel Kovalenko created IGNITE-8835:
---
Summary: Do not skip distributed phase of 2-phase partition
release if there are some caches to stop / modify
Key: IGNITE-8835
URL: https://issues.apache.org/jira/browse/IGN
Anton Kurbanov created IGNITE-8836:
--
Summary: NullPointerException during Ignition.start prevents JVM
shutdown
Key: IGNITE-8836
URL: https://issues.apache.org/jira/browse/IGNITE-8836
Project: Ignite
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4227
IGNITE-8768 Implemented eviction stopping to prevent possible JVM crush
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4094
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4209
---
Hi,
Two quick questions:
1. The design documentation here,
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood,
states that the default segment count is equal to the number of logical
cores available in the underlying machine. However, the segme
Hi Vyacheslav,
How about service redeployment in case if user wants to update the code? Is
this planned?
D.
On Tue, Jun 19, 2018 at 12:10 AM, Vyacheslav Daradur
wrote:
> Hi Denis!
>
> >> If to assume that Ignite 2.7 gets released in September, what else
> would you be able to complete by that
Hi,
1. It looks weird, yeah. Need to ask Sergey, who has changed it last time.
2. Because we could reuse memory. For example, after cache destroy or
something like that.
On Tue, Jun 19, 2018 at 9:58 PM, John Wilson
wrote:
> Hi,
>
> Two quick questions:
>
>
>1. The design documentation here
Hi Dmitriy,
Yes, the task [1] is planned to be implemented once the main tasks
will be completed.
[1] https://issues.apache.org/jira/browse/IGNITE-8367
On Tue, Jun 19, 2018 at 10:06 PM Dmitriy Setrakyan
wrote:
>
> Hi Vyacheslav,
>
> How about service redeployment in case if user wants to update
On Tue, Jun 19, 2018 at 1:50 PM, Vyacheslav Daradur
wrote:
> Hi Dmitriy,
>
> Yes, the task [1] is planned to be implemented once the main tasks
> will be completed.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8367
Awesome! This is a huge addition to the project.
>
>
> On Tue, Jun 19,
Hi,
1. An index page contains the hash value of key and a link; where a link
is page_id + offset. Question: what is this offset? Is it the offset to the
item in the data page? In other words, Ignite locates the page and the item
within the page and finally gets the key-value pair by f
Hello John,
1) Quote from the same article:
Values are inserted into data page from the end to beginning. Items
are filled from beginning to end.
To address particular Key-Value pair ignite uses Link = Page ID +
order in page.
Link allows to read K,V pair as N-th item in page.
Simply put,
Hi,
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document
I have read the how-to.
And my question is, is a JIRA ticket required for document-only fix? For
example, to fix a broken link.
https://apacheignite.readme.io/docs/memcached-support
Recently I just submitted a SUGGEST EDITS t
37 matches
Mail list logo
