GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5616
IGNITE-10537
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10537
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5569
IGNITE-10434
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10434
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5538
ignite-10457
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10457
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5497
IGNITE-10393
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10393
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5247
IGNITE-10109 MVCC TX: data become inconsistent after several updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5057
IGNITE-9928
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9928
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5035
IGNITE-9911
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9911
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4984
IGNITE-9292 MVCC SQL: Unexpected state exception when updating backup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4954
IGNITE-9749 MVCC: Assertion error in
JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite
hang
You can merge this pull request into a Git repository by running
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4727
MVCC branch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-mvcc-b3
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4705
Configuration compatibility fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gg-14183
Alternatively you can
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4696
IGNITE-9483 JDBC/ODBC thin drivers protocol versions compatibility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Nikita,
Yes, you're right. Maybe I wasn't clear enough.
Usually server nodes are placed in the same fast network segment (one
datacenter); in any case we need an ability to setup compression per
connection using some filter like useCompression(ClusterNode, ClusterNode)
to compress traffic only
Nikita,
I took a look at the changes and see two issues.
The first one is additional dependencies in core module. That means you
should whether make the filter plugable and provide some additional module
for it or put all the necessary classes to ignite-core.
The second is possible bottleneck
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3300
---
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3299
---
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3300
IGNITE-7321 mvcc enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-7321-mvcc-enabled
Alternatively
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3299
IGNITE-7321
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7321
Alternatively you can review and apply
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3285
---
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3284
---
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3285
IGNITE-7261 MVCC enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7261-mvcc-on
Alternatively you can
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3284
IGNITE-7261 MVCC disabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7261-mvcc-off
Alternatively you
GitHub user gvvinblade reopened a pull request:
https://github.com/apache/ignite/pull/3220
IGNITE-4191
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4191
Alternatively you can review and apply
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3220
---
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3220
IGNITE-4191
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4191
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3052
IGNITE-6931
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6931
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2960
IGNITE-6809
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6809
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2947
IGNITE-6787
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6787
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2946
IGNITE-6786
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6786
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2574
IGNITE-6182
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6182-master
Alternatively you can review
To be honnest we check heap memory which is used by all Ignite nodes on the
host:
org.apache.ignite.internal.IgniteKernal#checkPhysicalRam
Shouldn't we do the same for offheap?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1488
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1499
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2535
IGNITE-6182
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6182
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2479
IGNITE-6101
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6101
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2448
IGNITE-6050
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6050
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2447
IGNITE-6051
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6051
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2444
IGNITE-6063
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6063
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2401
ignite-2.1.3.b1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3.b1
Alternatively you can review
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2309
IGNITE-5761
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5761
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2267
IGNITE-5686
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5686
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2185
IGNITE-5581
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12168
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2181
IGNITE-5454
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5454
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2172
IGNITE-5548
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5548
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2147
IGNITE-5523
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5523
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2102
IGNITE-5196 Ignite JDBC Driver fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite jdbc-fix
Alternatively you can
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2083
IGNITE-5196
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5196
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2059
IGNITE-5075-pds
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5075-pds
Alternatively you can review
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1774
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1796
IGNITE-4694
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4694
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1790
IGNITE-3488
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3488
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1774
IGNITE-4946
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4946
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1756
IGNITE-4930
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-3477-thread-local-free-lists-cache
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1644
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1607
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1703
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1597
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1703
IGNITE-4888
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4888
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1644
IGNITE-4811
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4811
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1625
IGNITE-4712 (tests fix)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4712
Alternatively you can review
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1607
IGNITE-4803
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4803
Alternatively you can review and apply
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1597
IGNITE-4779 Missed discovery data snapshot during exchange processing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/1535
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1559
IGNITE-4712 Memory leaks in PageMemory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4712
Alternatively
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1535
IGNITE-4694 Add tests to check there are no memory leaks in PageMemory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1488
IGNITE-4645
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-4645
Alternatively you can review and apply
66 matches
Mail list logo
