Alexey Goncharuk created IGNITE-8737:
Summary: Improve checkpoint logging information
Key: IGNITE-8737
URL: https://issues.apache.org/jira/browse/IGNITE-8737
Project: Ignite
Issue Type:
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/4147
IGNITE-8565 Client marshalling improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-8565
Alternatively
Hi Igniters!
I've prepared two scripts to benchmark the throughput of Node.JS thin
client using 'atomic-put' operations [1]. They work in the following way:
- Main script 'bench-starter.js' starts the given number of thin clients as
sub-processes. AFAIK, Node.JS is one-threaded so we should fork
Ivan Rakov created IGNITE-8735:
--
Summary: Metastorage creates its own index partition
Key: IGNITE-8735
URL: https://issues.apache.org/jira/browse/IGNITE-8735
Project: Ignite
Issue Type: Bug
Alexey Goncharuk created IGNITE-8736:
Summary: Add transaction label to CU.txString() method output
Key: IGNITE-8736
URL: https://issues.apache.org/jira/browse/IGNITE-8736
Project: Ignite
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4148
IGNITE-8739 cherry picked from GG-13874 Implement WA for TCP communicâ¦
â¦ation related to hanging on descriptor reservation.
(cherry picked from commit f2a6133)
You can merge this pull
Anton Kalashnikov created IGNITE-8739:
-
Summary: Implement WA for TCP communication related to hanging on
descriptor reservation
Key: IGNITE-8739
URL: https://issues.apache.org/jira/browse/IGNITE-8739
Hello!
I would agree to modifying some tests to check for this case in Java if you
prop up my Orphaned Tests PR :)
Regards,
--
Ilya Kasnacheev
2018-05-31 13:58 GMT+03:00 Dmitry Pavlov :
> Hi Pavel,
>
> Unfortunately the time that I now can dedicate to the community is very
> limited.
>
> I
Alexey Kuznetsov created IGNITE-8734:
Summary: Visor metrics don't include transactions started on
client node
Key: IGNITE-8734
URL: https://issues.apache.org/jira/browse/IGNITE-8734
Project:
Alexey Goncharuk created IGNITE-8738:
Summary: Improve coordinator change information
Key: IGNITE-8738
URL: https://issues.apache.org/jira/browse/IGNITE-8738
Project: Ignite
Issue Type:
Ilya Kasnacheev created IGNITE-8740:
---
Summary: Support reuse of already initialized Ignite in
IgniteSpringBean
Key: IGNITE-8740
URL: https://issues.apache.org/jira/browse/IGNITE-8740
Project:
Hi Ivan,
Thanks for taking care of this. I will give the scripts a try and get back
to you if any questions.
Could you please update the JIRA ticket [1] so that we keep it up-to-date.
Thanks!
p.
[1] https://issues.apache.org/jira/browse/IGNITE-8733
On Thu, Jun 7, 2018 at 4:47 AM, Иван
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4143
---
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/4149
IGNITE-8713 Spring Data dependencies upgraded
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-8713
Alternatively
Alexei Scherbakov created IGNITE-8743:
-
Summary: TcpCommunicationSpi hangs in rare circumstances on
outgoing descriptor reservation.
Key: IGNITE-8743
URL: https://issues.apache.org/jira/browse/IGNITE-8743
Hi Ilya, I appreciate you answer.
Sincerely,
чт, 7 июн. 2018 г. в 17:16, Ilya Kasnacheev :
> Hello!
>
> This module depends on a library which is under LGPL.
>
> This means you will have to build this module yourself, deploy to your
> local maven, to satisfly licences' terms. This is the reason
Hello!
Do we have an official subj list? Such as Wiki page or JIRA label?
Cause if we don't, we'll surely forget a lot of things and will have to
wait for 4.0.
We already did that with IGNITE_BINARY_SORT_OBJECT_FIELDS in 2.0 :(
I expect to have in this list breaking changes, and @Deprecated
Yury Babak created IGNITE-8741:
--
Summary: [ML] Make a tutorial for data preprocessing
Key: IGNITE-8741
URL: https://issues.apache.org/jira/browse/IGNITE-8741
Project: Ignite
Issue Type: Wish
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4150
IGNITE-8509 Fix cache 6 suite flaky tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8509
Dima,
See https://issues.apache.org/jira/browse/IGNITE-5565
On Thu, Jun 7, 2018 at 10:09 PM, Dmitry Pavlov
wrote:
> Hi Ilya, I appreciate you answer.
>
> Sincerely,
>
> чт, 7 июн. 2018 г. в 17:16, Ilya Kasnacheev :
>
> > Hello!
> >
> > This module depends on a library which is under LGPL.
> >
Dmitriy Pavlov created IGNITE-8742:
--
Summary: Direct IO 2 suite is timed out by out of disk space
failure emulation test: WAL manager failure does not stoped.
Key: IGNITE-8742
URL:
Hi,
I've looked to the problem and didn't see any problem with BeanUtils.
Only module that depends on BeanUtils is Cassandra cache store in
order to map POJO to CQL queries. Usages are only on Ignite side with
configured Cassandra cache store and can't exploit described
vulnerability from my
Hi Igniters, sorry for the delay in replying.
I going to finish the task [1] to the end of this month.
[1] https://issues.apache.org/jira/browse/IGNITE-8361
On Wed, May 16, 2018 at 10:57 PM, Vyacheslav Daradur
wrote:
> Hi, Igniters!
>
> I had a discussion about the scope of work of IEP-17 with
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4151
Ignite-8681: check if 8503 fix test issues.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8681-8503
Thank, Vladimir.
Denis, confirming, AI 2.5 is not supported.
However, all the tests and examples happily pass on the latest master (as
of today). So please use it for testing.
Thanks,
p.
On Thu, Jun 7, 2018 at 12:33 AM, Vladimir Ozerov
wrote:
> Denis,
>
> No, AI 2.5 is not supported.
>
>
> On 7 Jun 2018, at 23:04, Denis Magda wrote:
>
> I'm fine with the suggested approach.
With which one — current implementation in issue?
> However, not sure we need to update
> all the branches. Can't branch owners just pull the changes back from
> master if the plan to merge back later?
I'm fine with the suggested approach. However, not sure we need to update
all the branches. Can't branch owners just pull the changes back from
master if the plan to merge back later?
--
Denis
On Thu, Jun 7, 2018 at 12:57 PM, Petr Ivanov wrote:
> Denis,
>
>
> The most simple approach — repack
Second article in a multi-part series:
https://www.gridgain.com/resources/blog/using-linear-regression-apacher-ignitetm
Feedback welcome.
Thank you.
>
> With which one — current implementation in issue?
That's the answer to your question:
1. quickly fix all of them (can be solved by preliminary preparations —
searching for -fabric- usages in build configuration);
2. update all branches to master because otherwise old branch will stop
Petr,
Am I correct that all 3 points were tested for VirtualBox? I would
introduce a documentation sub-section for VirtualBox then.
As for the Windows WSL, did you have a change to look into it?
--
Denis
On Thu, Jun 7, 2018 at 2:42 AM, Petr Ivanov wrote:
> Here are the results of checks:
>
>
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4152
IGNITE-8736 Add transaction label to CU.txString() method output
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Pavel Konstantinov created IGNITE-8744:
--
Summary: Incorrect behavior of cluster activation control
Key: IGNITE-8744
URL: https://issues.apache.org/jira/browse/IGNITE-8744
Project: Ignite
On Fri, 8 Jun 2018 at 00:37, Denis Magda wrote:
> Petr,
>
> Am I correct that all 3 points were tested for VirtualBox?
No, it was tested for Windows 10 WSL.
I would
> introduce a documentation sub-section for VirtualBox then.
As I said previously — under “honest” virtual environments (i.
Ok, then I will update issue code and start preparation for build
configuration changes.
On Thu, 7 Jun 2018 at 23:41, Denis Magda wrote:
> >
> > With which one — current implementation in issue?
>
>
> That's the answer to your question:
>
> 1. quickly fix all of them (can be solved by
Mahesh Renduchintala created IGNITE-8728:
Summary: Nodes down after other nodes reboot in the cluster
Key: IGNITE-8728
URL: https://issues.apache.org/jira/browse/IGNITE-8728
Project: Ignite
Martin Askøe created IGNITE-8729:
Summary: Deadlock in DataStreamer using addData(..) concurrently
Key: IGNITE-8729
URL: https://issues.apache.org/jira/browse/IGNITE-8729
Project: Ignite
Denis,
No, AI 2.5 is not supported.
чт, 7 июня 2018 г. в 2:37, Denis Magda :
> Pavel,
>
> I'm tried to run an SQL example following the prepared documentation:
>
> https://apacheignite.readme.io/v2.5/docs/nodejs-thin-client#section-examples
>
> Getting an exception below when execute `node
Saurin created IGNITE-8730:
--
Summary: Class org.jsr166.ConcurrentHashMap8 does not implement
the requested interface java.util.concurrent.ConcurrentMap
Key: IGNITE-8730
URL:
Hi,
I have a Ignite server running with 3rd partyDB (MYSQL). I have the below
configuration in xml file:
* *
...
On the server the jar for mysql jdbc driver is present iand the servers are
coming up successfully.
I have placed the mysql jdbc driver in a seperate folder and
Vladimir Ozerov created IGNITE-8731:
---
Summary: .NET: intermittent failures in
DataStreamerTest.TestFinalizer test
Key: IGNITE-8731
URL: https://issues.apache.org/jira/browse/IGNITE-8731
Project:
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4142
---
Igniters,
Lets define once again what should be done in this [1] task?
If current implementation is good, than I’ll update it to master and pass for
review.
Yet, there is other part of the task which concerns our build server — I assume
that almost all our build configurations will fail due
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/4145
IGNITE-8724 U.warn mislead implementation fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8724
Alternatively
Vladimir,
Not sure I see the point of 2 release policy.
It is not very good both for users and developers.
* Developers still have the burden on maintaining multiple protocol versions
* Users are quite limited with version choices
We should either go with a full-blown versioning so any client
GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/4146
Ignite-8714
For [Ignite-8714](https://issues.apache.org/jira/browse/IGNITE-8714)
You can merge this pull request into a Git repository by running:
$ git pull
Here are the results of checks:
1. Ubuntu. Running Apache Ignite as a stand-alone application works fine, I
have successful connections to another Apache Ignite node running under
VirtualBox CentOS.
NOTE: connectivity started working only after creation of “allow all incoming
connections”
Vladimir Ozerov created IGNITE-8732:
---
Summary: SQL: REPLICATED cache cannot be left-joined to PARTITIONED
Key: IGNITE-8732
URL: https://issues.apache.org/jira/browse/IGNITE-8732
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3933
---
Ilya Suntsov created IGNITE-8733:
Summary: Add benchmarks for NodeJS thin client
Key: IGNITE-8733
URL: https://issues.apache.org/jira/browse/IGNITE-8733
Project: Ignite
Issue Type:
49 matches
Mail list logo
