Re: Apache Ignite RPM packaging (Stage II)

Current packages design (after installation) does not differ from binary archive - everything works (except necessity to run service instead ignite.sh) just the same way, including libs/optional. Also, there can be issues with system JDK version by default, but every problem will be in journalctl

Re: Service grid redesign

It sounds like it's not a trivial thing to support the automatic services redeployment after a restart. Let's postpone it for now, guys concentrating on more urgent things related to the services. Alex, Vladimir, Could you have a look at Denis question about the discovery-based deployment? Guess

[GitHub] ignite pull request #3417: IGNITE-2766 Opportunistically reopen cache after ...

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

Re: Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Hey Dmitry, Loving the name of the endeavour [make TC green again] ;-) Feel free to do that for now. I'll take a look as soon as I have some spare cycles. Cheers! On Fri, Apr 13, 2018 at 3:24 PM, Dmitry Pavlov wrote: > Hi Igniters, > > I've created

Re: Apache Ignite RPM packaging (Stage II)

Ilya, Thanks for your inputs. The reason why we decided to split Ignite into several packages mimics the reason why Java community introduced modular subsystem for JDK. That's all about size. Ignite distribution is too big, and we're trying to separate it into several components so that people

[jira] [Created] (IGNITE-8265) TDE - MEK replacement

Nikolay Izhikov created IGNITE-8265: --- Summary: TDE - MEK replacement Key: IGNITE-8265 URL: https://issues.apache.org/jira/browse/IGNITE-8265 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-8264) TDE - Node join enhanecements

Nikolay Izhikov created IGNITE-8264: --- Summary: TDE - Node join enhanecements Key: IGNITE-8264 URL: https://issues.apache.org/jira/browse/IGNITE-8264 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-8263) TDE - Encryption/Decription of pages

Nikolay Izhikov created IGNITE-8263: --- Summary: TDE - Encryption/Decription of pages Key: IGNITE-8263 URL: https://issues.apache.org/jira/browse/IGNITE-8263 Project: Ignite Issue Type:

[GitHub] ignite pull request #3823: IGNITE-8232 ML package cleanup for 2.5 release.

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

[jira] [Created] (IGNITE-8262) TDE - MEK and CEK processing

Nikolay Izhikov created IGNITE-8262: --- Summary: TDE - MEK and CEK processing Key: IGNITE-8262 URL: https://issues.apache.org/jira/browse/IGNITE-8262 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-8261) TDE - Configuration

Nikolay Izhikov created IGNITE-8261: --- Summary: TDE - Configuration Key: IGNITE-8261 URL: https://issues.apache.org/jira/browse/IGNITE-8261 Project: Ignite Issue Type: Sub-task Affects

[jira] [Created] (IGNITE-8260) Transparend data encryption

Nikolay Izhikov created IGNITE-8260: --- Summary: Transparend data encryption Key: IGNITE-8260 URL: https://issues.apache.org/jira/browse/IGNITE-8260 Project: Ignite Issue Type: New Feature

Re: Move documentation from readme.io to GitHub pages

I did a very shallow research on Jekyll. Work flow seemed similar to Docusaurus but more flexible in terms of directory structure- how docs can be placed in the repo (Docusaurus requires docs to be stored in a particular directory structure), as well as sidebar menu ( Docusaurus does not allow

[GitHub] ignite pull request #3823: IGNITE-8232 ML package cleanup for 2.5 release.

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/3823 IGNITE-8232 ML package cleanup for 2.5 release. fixed javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8232

[jira] [Created] (IGNITE-8259) Node join should be failed if it has cache not contained in cluster

Anton Kalashnikov created IGNITE-8259: - Summary: Node join should be failed if it has cache not contained in cluster Key: IGNITE-8259 URL: https://issues.apache.org/jira/browse/IGNITE-8259

[GitHub] ignite pull request #3822: IGNITE-8097 Java thin client: throw handshake exc...

GitHub user kukushal opened a pull request: https://github.com/apache/ignite/pull/3822 IGNITE-8097 Java thin client: throw handshake exception on connect phase You can merge this pull request into a Git repository by running: $ git pull

Re: Memory usage per cache

Vladimir, For now I would > only show total size of all indexes, and add something like > "indexSize(String indexName)" method later Is there any technical or architectural limitation that prevents us from adding this method right now? I thought that if we could show the size of a PK, then we

[GitHub] ignite pull request #3821: IGNITE-8258 Fixed page acquire/write unlock order...

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3821 IGNITE-8258 Fixed page acquire/write unlock order during checkpoint You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: [ML] Remove Old FuzzyCMeans Implementation

Hi Alexey, Thats sounds reasonable for me especially if we have bugs in current implementation. So I agree to remove for FCM for now and return it in further release. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[ML] Remove Old FuzzyCMeans Implementation

Hi Igniters, Currently, I'm working on adoption of clustering algorithms (KMeans/FuzzyCMeans) to the new Partitioned Dataset. KMeans was adopted without any troubles, but FuzzyCMeans couldn't be adopted so easy 1. It uses local data structures to collect indices of rows presented in dataset. It

[jira] [Created] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

Dmitriy Pavlov created IGNITE-8258: -- Summary: Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started) Key: IGNITE-8258 URL:

[GitHub] ignite pull request #3820: IGNITE-8257: GridFutureAdapterSelfTest#testChaini...

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/3820 IGNITE-8257: GridFutureAdapterSelfTest#testChaining fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-8257

[GitHub] ignite pull request #3806: IGNITE-8232 ML package cleanup for 2.5 release.

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

[GitHub] ignite pull request #3807: IGNITE-8233 KNN and SVM algorithms don't work whe...

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

[jira] [Created] (IGNITE-8257) GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)

Vitaliy Biryukov created IGNITE-8257: Summary: GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely) Key: IGNITE-8257 URL: https://issues.apache.org/jira/browse/IGNITE-8257 Project:

[jira] [Created] (IGNITE-8256) TxRecoveryStoreEnabledTest.testPessimistic fails on TC

Alexey Goncharuk created IGNITE-8256: Summary: TxRecoveryStoreEnabledTest.testPessimistic fails on TC Key: IGNITE-8256 URL: https://issues.apache.org/jira/browse/IGNITE-8256 Project: Ignite

Re: Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Hi, I've spent some time to research the issue. The main problem is wrong dependencies on artifacts which absent in "ignite-osgi-karaf" repo: https://repository.apache.org/content/groups/snapshots-group/org/apache/ignite/ignite-osgi-karaf/ There are not needed artifacts since Apache Ignite

[GitHub] ignite pull request #3819: IGNITE-8255: Possible name collisions in WorkersR...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3819 IGNITE-8255: Possible name collisions in WorkersRegistry. You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-8255

Re: Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Hello! I have tried this test and everything is very bad with it. As in, one slew of errors when running with mvn, different one when running from Idea, ungooglable errors as a result. I suggest remove this build for now. Wait if everybody with background in this technology cares enough to help

[jira] [Created] (IGNITE-8255) Possible name collisions in WorkersRegistry

Dmitriy Sorokin created IGNITE-8255: --- Summary: Possible name collisions in WorkersRegistry Key: IGNITE-8255 URL: https://issues.apache.org/jira/browse/IGNITE-8255 Project: Ignite Issue

[GitHub] ignite pull request #3818: IGNITE-8237 Ignite blocks on SecurityException in...

GitHub user kukushal opened a pull request: https://github.com/apache/ignite/pull/3818 IGNITE-8237 Ignite blocks on SecurityException in exchange-worker due to unauthorised on-heap cache configuration You can merge this pull request into a Git repository by running: $ git

Re: Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Hi Igniters, I've created https://issues.apache.org/jira/browse/IGNITE-8254 and muted test. Second test in OSGI suite is also flaky, and probably we should remove OSGI build from Run-All at all. What do you think? Sincerely, Dmitriy Pavlov вт, 10 апр. 2018 г. в 19:54, Dmitry Pavlov

[jira] [Created] (IGNITE-8254) OSGI test is failed almost everytime IgniteOsgiTestSuite: IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled failed

Dmitriy Pavlov created IGNITE-8254: -- Summary: OSGI test is failed almost everytime IgniteOsgiTestSuite: IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled failed Key: IGNITE-8254 URL:

[jira] [Created] (IGNITE-8253) CacheConfiguration.keyConfiguration is never documented

Ilya Kasnacheev created IGNITE-8253: --- Summary: CacheConfiguration.keyConfiguration is never documented Key: IGNITE-8253 URL: https://issues.apache.org/jira/browse/IGNITE-8253 Project: Ignite

Re: Apache Ignite RPM packaging (Stage II)

2018-04-13 7:42 GMT+03:00 Peter Ivanov : > On Thu, 12 Apr 2018 at 20:04, Ilya Kasnacheev > wrote: > > > > > Moreover I did not find a way to start service if default installed JVM > is > > Java 7 :( I understand it's EOL, still this is something

[GitHub] ignite pull request #3817: IGNITE-8169: Adopt KMeans and remove FuzzyCMeans

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3817 IGNITE-8169: Adopt KMeans and remove FuzzyCMeans You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8169

[jira] [Created] (IGNITE-8252) NullPointerException is thrown during parallel massive start of nodes

Sergey Chugunov created IGNITE-8252: --- Summary: NullPointerException is thrown during parallel massive start of nodes Key: IGNITE-8252 URL: https://issues.apache.org/jira/browse/IGNITE-8252 Project:

[jira] [Created] (IGNITE-8251) Reduce testPageEviction run time

Dmitriy Pavlov created IGNITE-8251: -- Summary: Reduce testPageEviction run time Key: IGNITE-8251 URL: https://issues.apache.org/jira/browse/IGNITE-8251 Project: Ignite Issue Type: Test

Re: Service grid redesign

Vladimir, Currently we don't save binary metadata to disk, when persistence is disabled. But we still persist marshaller mappings for some reason, and I personally believe, that we shouldn't. But I agree, that we should separate data and service persistence configuration. Right now persistence

[jira] [Created] (IGNITE-8250) Adopt Fuzzy CMeans to PartitionedDatasets

Aleksey Zinoviev created IGNITE-8250: Summary: Adopt Fuzzy CMeans to PartitionedDatasets Key: IGNITE-8250 URL: https://issues.apache.org/jira/browse/IGNITE-8250 Project: Ignite Issue

[jira] [Created] (IGNITE-8249) Web Console: Convert first letter case for all the inputs

Vica Abramova created IGNITE-8249: - Summary: Web Console: Convert first letter case for all the inputs Key: IGNITE-8249 URL: https://issues.apache.org/jira/browse/IGNITE-8249 Project: Ignite

Re: Service grid redesign

Alex, I would say that we've already had this behavior for years - marshaller cache. I think it is time to agree that "in-memory" != stateless. Instead "in-memory" means "data is not stored on disk". May be we can have a flag which will wipe out all metadata on node restart (e.g. it could make

[jira] [Created] (IGNITE-8248) Web Console: NullPointException in agent in case of self-signed certificates.

Andrey Novikov created IGNITE-8248: -- Summary: Web Console: NullPointException in agent in case of self-signed certificates. Key: IGNITE-8248 URL: https://issues.apache.org/jira/browse/IGNITE-8248

[jira] [Created] (IGNITE-8247) .NET: ICacheLock.TryEnter() returns false if client is disconnected

Roman Guseinov created IGNITE-8247: -- Summary: .NET: ICacheLock.TryEnter() returns false if client is disconnected Key: IGNITE-8247 URL: https://issues.apache.org/jira/browse/IGNITE-8247 Project:

[GitHub] ignite pull request #3816: IGNITE-8246: update print errors

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3816 IGNITE-8246: update print errors Fix print error You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-8246 Alternatively you

[jira] [Created] (IGNITE-8246) Cast exception when using printPartitionState method

Maxim Muzafarov created IGNITE-8246: --- Summary: Cast exception when using printPartitionState method Key: IGNITE-8246 URL: https://issues.apache.org/jira/browse/IGNITE-8246 Project: Ignite

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

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/3815 IGNITE-7024 You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-7024 Alternatively you can review and apply these

[jira] [Created] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.

Andrey Novikov created IGNITE-8245: -- Summary: Web console: "Warning" icon is displayed above "secured key" icon. Key: IGNITE-8245 URL: https://issues.apache.org/jira/browse/IGNITE-8245 Project:

[GitHub] ignite pull request #3798: IGNITE-7829

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

Re: Memory usage per cache

Igniters, I have several questions regarding overall metrics design: 1) Why we split PK and non-PK indexes? This is merely implementation detail and It is not clear why we want to pin it on public API forever. Other database vendors allow users to get size of specific index. For now I would only

Re: Service grid redesign

Denis, This is a subtle question. It looks like we have now a number of use-cases when persistent storage is required even for a pure in-memory mode. One of the use-cases is thin client authentication, the other is service grid configuration persistence. Generally, I would agree that this is an

[GitHub] ignite pull request #3812: IGNITE-8240 .NET: Use default scheduler when star...

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

[GitHub] ignite pull request #3814: Fixed skipping of affinity calculation in case wh...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3814 Fixed skipping of affinity calculation in case when eventNode is not affinityNode You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3691: IGNITE-7691: Provide info about DECIMAL column sc...

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

[jira] [Created] (IGNITE-8244) Sporadic ClusterTopologyCheckedException for the example run

Sergey Kozlov created IGNITE-8244: - Summary: Sporadic ClusterTopologyCheckedException for the example run Key: IGNITE-8244 URL: https://issues.apache.org/jira/browse/IGNITE-8244 Project: Ignite

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Agree with Alex. Now we perform extra WAL fsync() at the beginning of checkpoint. We *have* to wait for call completion before starting to write checkpoint pages - otherwise both physical records in WAL and partition files in storage will be in a mess in case of power loss. User threads

Re: Apache Ignite 2.5 release

Andrey, thanks for control :) So, You'll fix broken versions eventually? BTW, I don't think it's a good idea to merge issues with fix version 2.5 to ignite-2.5. Good way is to fix version to 2.6 instead. 2018-04-12 21:34 GMT+03:00 Andrey Gura : > Anton, > > all is under

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Dmitriy, The point of this fsync is to order FS disk writes to prevent data corruption, so this fsync has to be synchronous and cannot be asynchronous or delayed. Given that we fix correctness, I believe that current results are acceptable. 2018-04-13 2:48 GMT+03:00 Dmitriy Setrakyan

[jira] [Created] (IGNITE-8243) Possible memory leak at ExchangeLatchManager during dynamic creating/removing of the local caches

Andrey Aleksandrov created IGNITE-8243: -- Summary: Possible memory leak at ExchangeLatchManager during dynamic creating/removing of the local caches Key: IGNITE-8243 URL: