GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3280
IGNITE-7135 IgniteCluster.startNodes() returns successful
ClusterStartNodeResult even though the remote process fails.
Fix windows startup scripts.
Add startNodes() Windows support
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/3178
---
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3201
IGNITE-7160 Ignore messages from not alive and failed nodes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3178
IGNITE-7135 IgniteCluster.startNodes() returns successful
ClusterStartNodeResult even though the remote process fails.
Fix windows startup scripts. Add startNodes() Windows support through
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3166
IGNITE-7134 Never-ending timeout in
IgniteSpiOperationTimeoutHelper.nextTimeoutChunk().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3155
Ignite-6700
TCP discovery update: failing nodes and messaging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3094
IGNITE-6827 Configurable rollback for long running transactions before
partition exchange
Add property TransactionConfiguration.rollbackOnTopologyChangeTimeout.
Check
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2984
IGNITE-6700 Node considered as failed can cause failure of others nodes
Independent asynchronous connection checkers for the previous and the next
nodes.
TcpDiscoveryHandshakeResponse
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/2942
---
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2942
disco update
Added TcpDiscoverySplitTest, updated IgniteCacheTopologySplitAbstractTest
Early previous node fail with more reliable connection check (keep-alive)
algorithm
Fast node
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/2928
---
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/2654
---
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2928
IGNITE-6700 Node considered as failed can cause failure of others nodes
Added TcpDiscoverySplitTest, updated IgniteCacheTopologySplitAbstractTest
Early previous node fail with more
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2890
IGNITE-6519 Race in SplitAwareTopologyValidator on activator and server
node join
Using a bigger topology
TestRecordingCommunicationSpi fix (future timeout instead
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/2845
---
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2858
IGNITE-6521 Update JVM options (default and recommendations) for better
performance
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2845
IGNITE-6519 Race in SplitAwareTopologyValidator on activator and server
node join
TestRecordingCommunicationSpi fix
references IGNITE-6507 Commit can be lost in network split scenario
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/2767
---
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2767
IGNITE-6519 Race in SplitAwareTopologyValidator on activator and server
node join
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2005
ignite-4496-1
IGNITE-4496 Review all logging for sensitive data leak
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1675
IGNITE-4865 Verbose logging, informative messages
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4865
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/1395
---
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 akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1666
Ignite-4496
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4496
Alternatively you can review and apply
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1599
ignite-4767
Suppressing or logging rollback exceptions instead of hiding the origin
exception
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1588
ignite-4767
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4767
Alternatively you can review and apply
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1470
ignite-4538
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4538
Alternatively you can review and apply
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1395
ignite-4496
Review all logging for sensitive data leak
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4496
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1357
ignite-4293
storeVal fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4293
Alternatively you can review
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1308
IGNITE-4167
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4167
Alternatively you can review and apply
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/1259
---
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 akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1259
ignite-4111
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4111
Alternatively you can review and apply
Github user akuramshingg closed the pull request at:
https://github.com/apache/ignite/pull/1219
---
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 akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1219
ignite-3812
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3812
Alternatively you can review and apply
33 matches
Mail list logo
