Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2775
---
I do not think that bigger B+Tree matter much. I was talking only about
data blocks. When you have a lot of logical caches, all of them are mixed
in the same data blocks. As a result you typically have to perform more IO
operations to read the same amount of data, as data block content becomes
more
Vladimir,
Thanks for the explanation and see inline
> On Oct 3, 2017, at 12:57 PM, Vladimir Ozerov wrote:
>
> Denis,
>
> This is not a "must have", neither I can name it a "feature". We have
> internal partition state metadata. When there is a lot of caches, there is
> a lot of metadata. It c
Denis,
This is not a "must have", neither I can name it a "feature". We have
internal partition state metadata. When there is a lot of caches, there is
a lot of metadata. It consumes local Java heap, causes high network traffic
on rebalance, and require Ignite to create a lot of files when persist
+1 to Vladimir. I think it is better to keep this feature disabled by
default. And enable cache groups only in case this feature is required by
user needs.
Enabling this will cause all caches will be placed into one tree.
After collapsing all B+-trees into one we will get log(N1+N2+N3) instead of
Vladimir,
Please share more details that I can put on the paper. Presently the feature is
described as a must have and I struggled finding any negative impact related
info.
—
Denis
> On Oct 3, 2017, at 12:46 PM, Vladimir Ozerov wrote:
>
> Denis,
>
> This feature should not be enabled by def
Denis,
This feature should not be enabled by default as it negatively affects read
performance.
On Tue, Oct 3, 2017 at 10:31 PM, Denis Magda wrote:
> Sam,
>
> Is there any technical limitation that prevents us from assigning caches
> with similar parameters to relevant groups on-the-fly?
>
> Af
Sam,
Is there any technical limitation that prevents us from assigning caches with
similar parameters to relevant groups on-the-fly?
After finishing the doc, I’m convinced the feature should be enabled by default
unless there are some pitfalls not known by me.
BTW, decided to avoid logical cac
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2798
IGNITE-6554: Atomic cache remove operations are logged in WAL as update
records
Probably fix for atomic cache remove operations
You can merge this pull request into a Git repository by running:
Github user dspavlov closed the pull request at:
https://github.com/apache/ignite/pull/2602
---
Dmitriy Pavlov created IGNITE-6554:
--
Summary: Atomic cache remove operations are logged in WAL as
update records
Key: IGNITE-6554
URL: https://issues.apache.org/jira/browse/IGNITE-6554
Project: Ignit
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2797
IGNITE-6553: Standalone WAL iterator fails to handle delete WAL data records
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-i
Dmitriy Pavlov created IGNITE-6553:
--
Summary: Standalone WAL iterator fails for delete WAL data records
Key: IGNITE-6553
URL: https://issues.apache.org/jira/browse/IGNITE-6553
Project: Ignite
Hi!
I need advice about the task:
https://issues.apache.org/jira/browse/IGNITE-4908
Better to read about the problem in Jira because it needs a context (2 last
messages).
The question in the last message. Please take a look.
Vladislav Pyatkov created IGNITE-6552:
-
Summary: The ability to set WAL history size in time units
Key: IGNITE-6552
URL: https://issues.apache.org/jira/browse/IGNITE-6552
Project: Ignite
Folks,
I created the branch *ignite-2.3* to finalize release scope. Please make
sure that only tickets targeted for 2.3 release are merged to this branch.
Let's take a week for finalization and stabilization, and then start
testing.
On Thu, Sep 28, 2017 at 10:16 AM, Vladimir Ozerov
wrote:
> Ign
Pavel Tupitsyn created IGNITE-6551:
--
Summary: .NET: NPE in PlatformDotNetCacheStore on Java-only nodes
Key: IGNITE-6551
URL: https://issues.apache.org/jira/browse/IGNITE-6551
Project: Ignite
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/2796
IGNITE-5504: Fluky test fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-5504
Alternatively you can review a
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2795
IGNITE-6550 Add new snapshot record type (SnapshotRecord)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
Dmitriy Govorukhin created IGNITE-6550:
--
Summary: Add new snapshot record type (SnapshotRecord)
Key: IGNITE-6550
URL: https://issues.apache.org/jira/browse/IGNITE-6550
Project: Ignite
I
Vladislav Pyatkov created IGNITE-6549:
-
Summary: Web agent: Able to start web agent internal of grid node
Key: IGNITE-6549
URL: https://issues.apache.org/jira/browse/IGNITE-6549
Project: Ignite
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2794
IGNITE-6539: Human readable WAL parser fails if empty log files existâ¦
â¦s in directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/grid
Denis Mekhanikov created IGNITE-6548:
Summary: Improve service grid documentation
Key: IGNITE-6548
URL: https://issues.apache.org/jira/browse/IGNITE-6548
Project: Ignite
Issue Type: Impro
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2793
IGNITE-6529: JDBC support 'nullable' column property
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2792
IGNITE-6547 Added ability log timestamp for wal tx and data records
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-i
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2786
---
GitHub user skylark-nam opened a pull request:
https://github.com/apache/ignite/pull/2791
Ignite 6531 Need to add a 'required' method to the SpringResource Annotation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/skylark-nam/ig
Hi Guys,
I want to share the first experience of using the utility for compatibility
testing.
As part of the task to improve storage folders in PDS, I wrote 2 tests
(IGNITE 6285, FoldersReuseCompatibilityTest). These tests run versions 2.1
and 2.2, create storage, and then run the grid on new f
Dmitriy Govorukhin created IGNITE-6547:
--
Summary: Need to support ability log timestamp for wal tx and data
records
Key: IGNITE-6547
URL: https://issues.apache.org/jira/browse/IGNITE-6547
Project
Guys,
Let me remind you that services still don't support peer class loading:
https://issues.apache.org/jira/browse/IGNITE-975
I think, it should be fixed as well, because versioning is pretty useless
without ability to change implementation without downtime. Also I've seen a
lot of questions from
Alexey Kuznetsov created IGNITE-6546:
Summary: Update faveicon.ico in rest-htttp module
Key: IGNITE-6546
URL: https://issues.apache.org/jira/browse/IGNITE-6546
Project: Ignite
Issue Type:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2656
---
Hi,
Regarding question about default cache group: by default cache groups are
not enabled, each cache is started in separate group. Cache group is
enabled only if groupName is set in CacheConfiguration.
Thanks
On Sat, Sep 30, 2017 at 11:55 PM, wrote:
> Why not? Obviously compression would hav
33 matches
Mail list logo
