Denis Magda created IGNITE-6953:
---
Summary: OOM on the client node freezes the whole cluster
Key: IGNITE-6953
URL: https://issues.apache.org/jira/browse/IGNITE-6953
Project: Ignite
Issue Type:
Denis Magda created IGNITE-6952:
---
Summary: Deserialization failures on AIX
Key: IGNITE-6952
URL: https://issues.apache.org/jira/browse/IGNITE-6952
Project: Ignite
Issue Type: Bug
Affects
Igniters,
I’ve been talking to many Ignite users here and there who are already on Ignite
persistence or consider to turn it on. The majority of them are more than
satisfied with its current state and provided capabilities. That’s is really
good news for us.
However, I tend to come across the
Igniters,
Who is going to take a lead of Java 9 support and can do thorough review of all
the related changes? Here is a set of the tickets and Cergey solved one of them:
https://issues.apache.org/jira/browse/IGNITE-6728
—
Denis
> On Nov 16, 2017, at 3:12 PM, Cergey
Andrey,
This ticket seems to be about the same issue:
https://issues.apache.org/jira/browse/IGNITE-6944
Can you please take a look and provide your thoughts?
-Val
On Tue, Nov 7, 2017 at 4:02 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> *cross-posting to dev*
>
> Hi Chris,
The concern has been solved after I had a swift private conversation with
Vladimir Ozerov.
We just need to document how to write and read all the types supported by
binary format. That’s more than enough for the beginning.
—
Denis
> On Nov 17, 2017, at 10:40 AM, Denis Magda
Igniters,
Let me reiterate on the protocol details until it becomes publicly available.
If I’m not mistaken one of the reasons we got down to this task was to give an
efficient low-level protocol that will simplify and boost Ignite
clients/connectors development for various programming
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/3066
IGNITE-5938 Try to enable v2 serializer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite master-v2ser
Alternatively you
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/3065
Ignite 5938 noarch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5938-noarch
Alternatively you can review and
Vyacheslav,
CacheStore design assumes that the underlying storage is shared by all the
nodes in topology. Even if you delay rebalancing on node stop (which is
possible via CacheConfiguration#rebalanceDelay), I doubt it will solve all
your consistency issues.
Why don't you use Ignite persistence
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/3064
Ignite 1.9.9
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sk0x50/ignite ignite-1.9.9
Alternatively you can review and apply these changes
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/3063
IGNITE-6949: Add support of distributed matrices for OLS regression
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3062
Backport IGNITE-6818, fix test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13069
Alternatively you can
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/2894
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/3040
---
Pavel Tupitsyn created IGNITE-6951:
--
Summary: .NET: BinaryWriter should throw exception on pointer
fields
Key: IGNITE-6951
URL: https://issues.apache.org/jira/browse/IGNITE-6951
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2832
---
Alexander Paschenko created IGNITE-6950:
---
Summary: Update documentation for user facing CREATE TABLE params
Key: IGNITE-6950
URL: https://issues.apache.org/jira/browse/IGNITE-6950
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2831
---
Yury Babak created IGNITE-6949:
--
Summary: Cleanup OLS code
Key: IGNITE-6949
URL: https://issues.apache.org/jira/browse/IGNITE-6949
Project: Ignite
Issue Type: Bug
Security Level: Public
Dmitriy,
I added comments to the upsource review, please take a look.
2017-11-17 15:57 GMT+03:00 Дмитрий Рябов :
> Hello, Igniters! Please review.
>
> JIRA: https://issues.apache.org/jira/browse/IGNITE-6802
> PR: https://github.com/apache/ignite/pull/3021/files
>
Kirill Shirokov created IGNITE-6948:
---
Summary: SQL: Document new INLINE_SIZE option in CREATE INDEX
command
Key: IGNITE-6948
URL: https://issues.apache.org/jira/browse/IGNITE-6948
Project: Ignite
Hi,
You can implement your own no-op discovery and communication SPIs and plug
them in IgniteConfiguration, then no network ports will be opened.
--AG
2017-11-17 16:05 GMT+03:00 karthik :
> In our Project we are not allowed to open any port. Is it possible to
>
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/3061
IGNITE-2662 .NET Core support (run on Linux)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2662
Alternatively you
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3060
Ignite 2.1.7.b3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.7.b3
Alternatively you can review and
In our Project we are not allowed to open any port. Is it possible to disable
TcpDiscoveySpi and TcpCommunicationSpi . I use Ignite only on single node in
sever mode.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hello!
I want to resolve bugs.
My GutHub account: Denis-Log
My Jira account: da.loginov
Please, provide me with necessary permissions.
Thanks in advance.
Best regards,
Denis
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3013
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3059
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3030
---
Hi, Igniters!
This discussion thread related to
https://issues.apache.org/jira/browse/IGNITE-6171.
Currently there are no JVM performance monitoring tools in AI, for example
the impact of GC (eg STW) on the operation of the node. I think we should
add this functionality.
1) It is useful to know
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3048
---
Hello, Igniters! Please review.
JIRA: https://issues.apache.org/jira/browse/IGNITE-6802
PR: https://github.com/apache/ignite/pull/3021/files
Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-396
CI tests:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2981
---
Alexey Goncharuk created IGNITE-6947:
Summary: Near optimistic prepare future should abandon remap after
failed map attempt
Key: IGNITE-6947
URL: https://issues.apache.org/jira/browse/IGNITE-6947
Hi Andrey! Thank you for answering.
>> Key to partition mapping shouldn't depends on topology, and shouldn't
>> changed unstable topology.
Key to partition mapping doesn't depend on topology in my test
affinity function. It only depends on partitions number.
But partition to node mapping depends
GitHub user kdudkov opened a pull request:
https://github.com/apache/ignite/pull/3059
IGNITE-358 add InputSplit to HadoopV1Reporter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-358
Alternatively
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/3058
Ignite 6927
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6927
Alternatively you can review and apply
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3057
Ignite gg 13072
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13072
Alternatively you can review and
Github user dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/3056
---
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3056
Ignite gg 13072
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13072
Alternatively you can review and
Alexey Popov created IGNITE-6946:
Summary: Change Ignite Logger configuration on the fly
Key: IGNITE-6946
URL: https://issues.apache.org/jira/browse/IGNITE-6946
Project: Ignite
Issue Type:
Vladimir Ozerov created IGNITE-6945:
---
Summary: SQL: optionally do not copy offheap rows for local
SqlQuery
Key: IGNITE-6945
URL: https://issues.apache.org/jira/browse/IGNITE-6945
Project: Ignite
GitHub user Denis-Log opened a pull request:
https://github.com/apache/ignite/pull/3055
IGNITE-5731: curWaitingJobs and avgJobWaitTime calculation fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Denis-Log/ignite
44 matches
Mail list logo