[jira] [Created] (IGNITE-8655) Web Console: Update to next version.

Alexey Kuznetsov created IGNITE-8655: Summary: Web Console: Update to next version. Key: IGNITE-8655 URL: https://issues.apache.org/jira/browse/IGNITE-8655 Project: Ignite Issue Type:

[GitHub] ignite pull request #4098: IGNITE-8502: Ignite client can hang during a rejo...

GitHub user Mikhail1988 opened a pull request: https://github.com/apache/ignite/pull/4098 IGNITE-8502: Ignite client can hang during a rejoin You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

OptimizedObjectInputStream#available() doesn't work as expected?

Hello Igniters! When deserializing Externalizable cache entry it's impossible to use ObjectInput#available method for checking is there anything left to read in buffer. This is because OptimizedObjectInputStream#available always returns -1 (hard-coded). Does anyone know the reasons why this

[jira] [Created] (IGNITE-8659) Wrong FreeList usage in PendingTree may lead to page corruption.

Andrew Mashenkov created IGNITE-8659: Summary: Wrong FreeList usage in PendingTree may lead to page corruption. Key: IGNITE-8659 URL: https://issues.apache.org/jira/browse/IGNITE-8659 Project:

[jira] [Created] (IGNITE-8656) GridServiceProcessor does re-assignment even if no assignment is changed

Mikhail Cherkasov created IGNITE-8656: - Summary: GridServiceProcessor does re-assignment even if no assignment is changed Key: IGNITE-8656 URL: https://issues.apache.org/jira/browse/IGNITE-8656

[jira] [Created] (IGNITE-8657) Simultaneous start of bunch of client nodes may lead to some clients hangs

Sergey Chugunov created IGNITE-8657: --- Summary: Simultaneous start of bunch of client nodes may lead to some clients hangs Key: IGNITE-8657 URL: https://issues.apache.org/jira/browse/IGNITE-8657

[GitHub] ignite pull request #4099: IGNITE-7165: check aff assignments

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/4099 IGNITE-7165: check aff assignments You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite mm-ignite_7165 Alternatively you can review

[GitHub] ignite pull request #3101: IGNITE-7024

Github user NSAmelchev closed the pull request at: https://github.com/apache/ignite/pull/3101 ---

[jira] [Created] (IGNITE-8658) Add info message for complete partition exchange

Mikhail Cherkasov created IGNITE-8658: - Summary: Add info message for complete partition exchange Key: IGNITE-8658 URL: https://issues.apache.org/jira/browse/IGNITE-8658 Project: Ignite

Re: Platform .NET add to RunAll Basic suite

Hi Pavel, Unfortunately the time that I now can dedicate to the community is very limited. I would be happy if Ilya K. agrees to make a separate test in Java. Best Regards, Pavlov Dmitry вт, 29 мая 2018 г. в 21:19, Pavel Tupitsyn : > Sorry for the late notice, but there are no tests in that

Re: Ability to check and completely fill transactions on creation

Anton, Why not just have one transaction event: EVT_TX_STATE_CHANGED? D. On Thu, May 31, 2018 at 9:10 AM, Anton Vinogradov wrote: > Dmitriy, > > Thanks for your comments! > > I've updated design to have > > public class TransactionStateChangedEvent extends EventAdapter { > private

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Unfortunately, it seems to be impossible (at least for now) — [1]. So we can say that current package design is for native Linux installation only.

[GitHub] ignite pull request #4100: IGNITE-8659: Wrong FreeList usage in PendingTree ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4100 ---

[GitHub] ignite pull request #4104: IGNITE-8673 Reconcile isClient* methods

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4104 IGNITE-8673 Reconcile isClient* methods You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8673 Alternatively

Re: Ability to check and completely fill transactions on creation

Dmitriy, Thanks for your comments! I've updated design to have public class TransactionStateChangedEvent extends EventAdapter { private Transaction tx; } also I specified following set of possible events public static final int[] EVTS_TX = { EVT_TX_STARTED, EVT_TX_COMMITTED,

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Petr, Why do we even suggest starting Ignite as a service? Why not just start Ignite instance as a stand-alone process? This should work, no? D. On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov wrote: > Unfortunately, it seems to be impossible (at least for now) — [1]. > So we can say that

[GitHub] ignite pull request #4103: Ignite 1.9.13

GitHub user antkr opened a pull request: https://github.com/apache/ignite/pull/4103 Ignite 1.9.13 CI You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.13 Alternatively you can review and apply

[GitHub] ignite pull request #4105: IGNITE-8675: Fixed flacky test PdsWithTtlCompatib...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/4105 IGNITE-8675: Fixed flacky test PdsWithTtlCompatibilityTest.testNodeS… …tartByOldVersionPersistenceData_2_1. You can merge this pull request into a Git repository by running: $ git

Re: OptimizedObjectInputStream#available() doesn't work as expected?

Folks, I checked and it's possible to use available() directly from stream encapsulated at GridDataInput, but I'm not sure it's a good idea to update almost obsolete classes. Catching EOFException hack looks as reasonable solution in current case. Thoughts? чт, 31 мая 2018 г. в 11:39, Pavel

[jira] [Created] (IGNITE-8675) Fix flacky test PdsWithTtlCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_1

Andrew Mashenkov created IGNITE-8675: Summary: Fix flacky test PdsWithTtlCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_1 Key: IGNITE-8675 URL: https://issues.apache.org/jira/browse/IGNITE-8675

[jira] [Created] (IGNITE-8672) Get rid of TcpDiscoverySpi#setForceServerMode

Eduard Shangareev created IGNITE-8672: - Summary: Get rid of TcpDiscoverySpi#setForceServerMode Key: IGNITE-8672 URL: https://issues.apache.org/jira/browse/IGNITE-8672 Project: Ignite

[jira] [Created] (IGNITE-8673) Reconcile isClient* methods

Eduard Shangareev created IGNITE-8673: - Summary: Reconcile isClient* methods Key: IGNITE-8673 URL: https://issues.apache.org/jira/browse/IGNITE-8673 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-8674) Ignite.NET LINQ exception with non-default entity sql schema

Victor created IGNITE-8674: -- Summary: Ignite.NET LINQ exception with non-default entity sql schema Key: IGNITE-8674 URL: https://issues.apache.org/jira/browse/IGNITE-8674 Project: Ignite Issue

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Dmitriy, Current packages design (both RPM and DEB) was reviewed and approved by community. I do not quite remember why service-based startup was chosen but it seems rather logical and Unix-compliant – under Linux almost every service software is packed this way, which gives some benefits like

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Dmitriy, SystemD supports running multiple instances of one service – this is done through @-like syntax: 'sudo systemctl start apache-ignite@', so that with every unique command string there will be started / stopped unique instance of Apache Ignite. And all instances can be restarted / stopped

[ANNOUNCE] Apache Ignite 2.5.0 Released

The Apache Ignite Community is pleased to announce the release of Apache Ignite 2.5.0. Apache Ignite [1] is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale With Ignite 2.5

REMINDER: Apache EU Roadshow 2018 in Berlin is less than 2 weeks away!

Hello Apache Supporters and Enthusiasts This is a reminder that our Apache EU Roadshow in Berlin is less than two weeks away and we need your help to spread the word. Please let your work colleagues, friends and anyone interested in any attending know about our Apache EU Roadshow event. We

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Petr, Most of the users will download and install Ignite so they can develop with it. This means that they will be starting more than one node, which is impossible if Ignite is a service. We should provide instructions to do both. D. On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov wrote: >

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Petr, I still get errors, see below... The worst part here is that I get an error message to look in the log, but I have no idea where the log file is located. > > > > > > > > > *d@DmitriyPC:~$ sudo service dbus start[sudo] password for d: * Starting > system message bus dbus > >

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

I’ll start the investigation. > On 31 May 2018, at 17:44, Dmitriy Setrakyan wrote: > > Petr, > > I still get errors, see below... The worst part here is that I get an error > message to look in the log, but I have no idea where the log file is > located. > > >> >> >> >> >> >> >> >>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov wrote: > I’ll start the investigation. > Can you please file a ticket so we can track it?

[GitHub] ignite pull request #4101: IGNITE-8666 Add ability of filtering data during ...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/4101 IGNITE-8666 Add ability of filtering data during datasets creation …asetBuilder. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8671) Provide instructions on running Apache Ignite as systemd service on Windows 10 WSL Ubuntu

Peter Ivanov created IGNITE-8671: Summary: Provide instructions on running Apache Ignite as systemd service on Windows 10 WSL Ubuntu Key: IGNITE-8671 URL: https://issues.apache.org/jira/browse/IGNITE-8671

Issues with forceServerMode on clients and unclear contract of isClient/isClientMode methods

Hi, guys! I just have found that we widely misuse org.apache.ignite.cluster.ClusterNode#isClient method. Now it returns how a node is connected to cluster (as part of the ring or not). So, it's not the same as IgniteConfiguration#isClientMode! But! Actually, we treat as the same thing. At

[jira] [Created] (IGNITE-8670) Umbrella: TensorFlow integration

Yury Babak created IGNITE-8670: -- Summary: Umbrella: TensorFlow integration Key: IGNITE-8670 URL: https://issues.apache.org/jira/browse/IGNITE-8670 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-8660) Under some circumstances server node can re-join back to the cluster with the same id

Mikhail Cherkasov created IGNITE-8660: - Summary: Under some circumstances server node can re-join back to the cluster with the same id Key: IGNITE-8660 URL: https://issues.apache.org/jira/browse/IGNITE-8660

[GitHub] ignite pull request #4086: IGNITE-8530 fixed onNodeLeft for InitNewCoordinat...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4086 ---

[jira] [Created] (IGNITE-8661) WALItreater is not stopped if can not deserialize record

Dmitriy Govorukhin created IGNITE-8661: -- Summary: WALItreater is not stopped if can not deserialize record Key: IGNITE-8661 URL: https://issues.apache.org/jira/browse/IGNITE-8661 Project: Ignite

[jira] [Created] (IGNITE-8663) L1,L2 normalization

Yury Babak created IGNITE-8663: -- Summary: L1,L2 normalization Key: IGNITE-8663 URL: https://issues.apache.org/jira/browse/IGNITE-8663 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-8664) Encoding categorical features

Yury Babak created IGNITE-8664: -- Summary: Encoding categorical features Key: IGNITE-8664 URL: https://issues.apache.org/jira/browse/IGNITE-8664 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #4096: VisorTxTask fails then printing transactions havi...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4096 ---

[jira] [Created] (IGNITE-8665) Umbrella: ML model validation for 2.6 release

Yury Babak created IGNITE-8665: -- Summary: Umbrella: ML model validation for 2.6 release Key: IGNITE-8665 URL: https://issues.apache.org/jira/browse/IGNITE-8665 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-8666) Add ability of filtering data during datasets creation

Yury Babak created IGNITE-8666: -- Summary: Add ability of filtering data during datasets creation Key: IGNITE-8666 URL: https://issues.apache.org/jira/browse/IGNITE-8666 Project: Ignite Issue

[jira] [Created] (IGNITE-8668) K-fold cross validation of models

Yury Babak created IGNITE-8668: -- Summary: K-fold cross validation of models Key: IGNITE-8668 URL: https://issues.apache.org/jira/browse/IGNITE-8668 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #4100: IGNITE-8659: Wrong FreeList usage in PendingTree ...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/4100 IGNITE-8659: Wrong FreeList usage in PendingTree may lead to page cor… …ruption. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8662) Umbrella: ML data preprocessing for 2.6 release

Yury Babak created IGNITE-8662: -- Summary: Umbrella: ML data preprocessing for 2.6 release Key: IGNITE-8662 URL: https://issues.apache.org/jira/browse/IGNITE-8662 Project: Ignite Issue Type: New

Re: WAL iterator unexpected behavior

Folks, I created the issue to solve this issue. IGNITE-8661 WALItreater is not stopped if can not deserialize record I suggest to make the following changes: 1. We should only stop iteration on known exceptions 2. Also, need to provide ability

[jira] [Created] (IGNITE-8667) Splitting of dataset to test and training sets

Yury Babak created IGNITE-8667: -- Summary: Splitting of dataset to test and training sets Key: IGNITE-8667 URL: https://issues.apache.org/jira/browse/IGNITE-8667 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-8669) Model estimation

Yury Babak created IGNITE-8669: -- Summary: Model estimation Key: IGNITE-8669 URL: https://issues.apache.org/jira/browse/IGNITE-8669 Project: Ignite Issue Type: New Feature Components:

[GitHub] ignite pull request #4085: Ignite 8476 no macs

Github user glukos closed the pull request at: https://github.com/apache/ignite/pull/4085 ---

[GitHub] ignite pull request #4083: IGNITE-8476 AssertionError exception occurs when ...

Github user glukos closed the pull request at: https://github.com/apache/ignite/pull/4083 ---

Re: Issues with forceServerMode on clients and unclear contract of isClient/isClientMode methods

Eduard, Sounds reasonable, agree with you. On Thu, May 31, 2018 at 5:10 PM, Eduard Shangareev < eduard.shangar...@gmail.com> wrote: > Hi, guys! > > I just have found that we widely > misuse org.apache.ignite.cluster.ClusterNode#isClient method. > > Now it returns how a node is connected to

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Filed https://issues.apache.org/jira/browse/IGNITE-8671 > On 31 May 2018, at 17:56, Dmitriy Setrakyan wrote: > > On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov wrote: > >> I’ll start the investigation. >> > > Can you please file a ticket

Re: IGNITE-8238 - Operation can fails with unexpected RuntimeException when node is stopping

Okay, I have changed the logging level to debug, updated master and rerun TC tests [1]. [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=pull%2F3993%2Fhead=buildTypeStatusDiv 2018-05-30 16:13 GMT+03:00 Andrey Mashenkov : > Hi, > > Yes, now

[GitHub] ignite pull request #4102: IGNITE-8657 client reconnect on exchange history ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4102 IGNITE-8657 client reconnect on exchange history exhausted implementation You can merge this pull request into a Git repository by running: $ git pull