Re: Apache Ignite RPM packaging (Stage II)

On Thu, 12 Apr 2018 at 20:04, Ilya Kasnacheev wrote: > Hello! I have tried your RPM scripts. > > First of all, I'm not sure that apache-ignite-core is a good name for > package which contains the actual server node kit, and that apache-ignite > is a good name for a

[GitHub] ignite pull request #3813: IGNITE-8242: Remove method GAGridUtils.getGenesFo...

GitHub user techbysample opened a pull request: https://github.com/apache/ignite/pull/3813 IGNITE-8242: Remove method GAGridUtils.getGenesForChromosome() as pro… Remove method GAGridUtils.getGenesForChromosome() as problematic when Chromosome contains duplicate genes.

[jira] [Created] (IGNITE-8242) Remove method GAGridUtils.getGenesForChromosome() as problematic when Chromosome contains duplicate genes.

Turik Campbell created IGNITE-8242: -- Summary: Remove method GAGridUtils.getGenesForChromosome() as problematic when Chromosome contains duplicate genes. Key: IGNITE-8242 URL:

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

On Thu, Apr 12, 2018 at 9:45 AM, Ivan Rakov wrote: > Dmitriy, > > fsync() is really slow operation - it's the main reason why FSYNC mode is > way slower than LOG_ONLY. > Fix includes extra fsyncs in necessary parts of code and nothing more. > Every part is important - at

Re: Apache Ignite RPM packaging (Stage II)

I am not sure that an email thread of over 20 messages is a good medium to discuss proposals. In Ignite, we create IEPs. Can you please summarize your proposal there and send a link there? Please explain not only the change itself, but the reason why we need it. D. On Thu, Apr 12, 2018 at 4:00

Re: Node.js client update: rev. 2

Hi Denis, Thank you for looking at the proposal and raising these questions! We'll take them to discuss offline and will address your recommendations in the next revision. I will let Vladimir comment on the QueryEntity here though to make sure we are on the same page. Thanks, P. On Thu, Apr

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Pavel, thanks for the suggestions. They would definitely work out. I would document the one with the event subscription: https://issues.apache.org/jira/browse/IGNITE-8241 Could you help preparing a sample code snippet with such a listener that will be added to the doc? I know that there are some

[jira] [Created] (IGNITE-8241) Docs: Triggering automatic rebalancing if the whole baseline topology is not recovered

Denis Magda created IGNITE-8241: --- Summary: Docs: Triggering automatic rebalancing if the whole baseline topology is not recovered Key: IGNITE-8241 URL: https://issues.apache.org/jira/browse/IGNITE-8241

Re: Apache Ignite RPM packaging (Stage II)

Petr, I wouldn't postpone this until 2.6 that will be out nor earlier than 3 months from now. *Anton V.*, could review and sign off the changes? Not sure we have a better person in the community who can do that. -- Denis On Thu, Apr 12, 2018 at 9:10 AM, Petr Ivanov wrote:

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

Ivan, Could we run Yardstick or YCSB benchmarks to see how the fixed LOG_ONLY affected the performance under the operational load (after the preloading part you're referring to is over)? -- Denis On Thu, Apr 12, 2018 at 9:45 AM, Ivan Rakov wrote: > Dmitriy, > > fsync()

Re: Memory usage per cache

Alex, Dmitriy, Please clarify/consider the following: - Can we get the size of a particular secondary index with a method like getIndexSize(indexName)? Vladimir Ozerov , it should be feasible, right? - The new

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

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3812 IGNITE-8240 .NET: Use default scheduler when starting Tasks You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-8240

Re: Node.js client update: rev. 2

Hello Pavel, Thanks for the update. Haven't heard from you guys for a while but seems you were too busy polishing the client. Looks great! Please consider several questions/notes: - Do we really want to migrate QueryEntity API [1] to Node.JS client? I heard we planned to deprecate it in

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Guys, I also heard complaints about absence of option to automatically change baseline topology. They absolutely make sense. What Pavel suggested will work as a workaround. I think, in future releases we should give user an option to enable a similar behavior via Ignite Configuration. It may

[jira] [Created] (IGNITE-8240) .NET: Use default scheduler when starting Tasks

Pavel Tupitsyn created IGNITE-8240: -- Summary: .NET: Use default scheduler when starting Tasks Key: IGNITE-8240 URL: https://issues.apache.org/jira/browse/IGNITE-8240 Project: Ignite Issue

[jira] [Created] (IGNITE-8239) SQL TX: Do not use skipReducer flag for MVCC DML requests

Igor Seliverstov created IGNITE-8239: Summary: SQL TX: Do not use skipReducer flag for MVCC DML requests Key: IGNITE-8239 URL: https://issues.apache.org/jira/browse/IGNITE-8239 Project: Ignite

[GitHub] ignite pull request #3675: IGNITE-7983: NPE fix.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3675 ---

Re: Apache Ignite 2.5 release

Anton, all is under control. Branches will be compared and changes that should be included to AI 2.5 will be identified. On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov wrote: > Possibly it is Andrey Gura — he initiated this thread and created > corresponding branch. > > >>

[GitHub] ignite pull request #3742: IGNITE-8110

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

[GitHub] ignite pull request #3727: Improve OS config suggestions

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

Re: Apache Ignite RPM packaging (Stage II)

Hello! I have tried your RPM scripts. First of all, I'm not sure that apache-ignite-core is a good name for package which contains the actual server node kit, and that apache-ignite is a good name for a package that will install everything (including cpp bindings). How does other packages solve

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

Dmitriy, fsync() is really slow operation - it's the main reason why FSYNC mode is way slower than LOG_ONLY. Fix includes extra fsyncs in necessary parts of code and nothing more. Every part is important - at the beginning of the thread I described why. 20% slow in benchmark doesn't mean

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, It's just one of the ways to implement it. We also can subscribe on node join / fail events to properly track downtime of a node. 2018-04-12 19:38 GMT+03:00 Pavel Kovalenko : > Denis, > > Using our API we can implement this task as follows: > Do each minute: > 1) Get

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, Using our API we can implement this task as follows: Do each minute: 1) Get all alive server nodes consistent ids => ignite().context().discovery().aliveServerNodes() => mapToConsistentIds(). 2) Get current baseline topology => ignite().cluster().currentBaselineTopology() 3) For each node

[jira] [Created] (IGNITE-8238) Operation can fails with unexpected RuntimeException when node is stopping.

Andrew Mashenkov created IGNITE-8238: Summary: Operation can fails with unexpected RuntimeException when node is stopping. Key: IGNITE-8238 URL: https://issues.apache.org/jira/browse/IGNITE-8238

Re: Apache Ignite RPM packaging (Stage II)

If someone from PMCы or Committers still sees necessity about including these tasks into Apache Ignite 2.5 release, this is the last chance to do so. Otherwise this task will be moved to at 2.6 release at least, or even moved to backlog indefinitely. > On 9 Apr 2018, at 19:08, Petr Ivanov

[GitHub] ignite pull request #3811: IGNITE-8166 PME hangs when error occurs during ch...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3811 IGNITE-8166 PME hangs when error occurs during checkpoint You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite

[GitHub] ignite pull request #3658: ignite-7978 don't check tag on restore in GridCac...

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

[GitHub] ignite pull request #3678: Ignite 2.4.4.b1 build

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

[GitHub] ignite pull request #3784: ignite-8058 fix flaky GridMarshallerMappingConsis...

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

Re: Memory usage per cache

Sounds good to me. Folks, any other feedback on metrics API in IGNITE-8078? 2018-04-06 21:36 GMT+03:00 Denis Magda : > Alex, > > Why not return cache group metrics from this method by default and properly > > document it? > > > What do you think about Dmitry's suggestion? It

Re: Apache Ignite 2.5 release

Possibly it is Andrey Gura — he initiated this thread and created corresponding branch. > On 12 Apr 2018, at 17:39, Anton Vinogradov wrote: > > Release manager is responsible for this change. > Do we have release manager for 2.5? > > 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov

Re: Apache Ignite 2.5 release

Release manager is responsible for this change. Do we have release manager for 2.5? 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov : > I've changed my ticket version assignment, and a lot of Igniters changed. > > Filter for double-check tickets related to you >

Re: Apache Ignite 2.5 release

I've changed my ticket version assignment, and a lot of Igniters changed. Filter for double-check tickets related to you

[GitHub] ignite pull request #3810: IGNITE-7972: Fixed NPE in TTL manager on unwindEv...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3810 IGNITE-7972: Fixed NPE in TTL manager on unwindEvicts. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7972

[GitHub] ignite pull request #3809: IGNTIE-7972: Fixed NPE in TTL manager on unwindEv...

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

[GitHub] ignite pull request #3809: IGNTIE-7972: Fixed NPE in TTL manager on unwindEv...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3809 IGNTIE-7972: Fixed NPE in TTL manager on unwindEvicts. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7972

Re: Apache Ignite 2.5 release

Folks, I see a lot of issues resolved as 2.5 but not merged to ignite-2.5 branch. Who is in charge of release 2.5, why (first time in history) nobody changes all 2.5 to 2.6? 2018-04-06 10:19 GMT+03:00 Petr Ivanov : > Added corresponding triggers for ignite-2.5 in Ignite

[GitHub] ignite pull request #3808: ignite-8205 make services be redeployed when clus...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/3808 ignite-8205 make services be redeployed when cluster is getting activated You can merge this pull request into a Git repository by running: $ git pull

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

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3807 IGNITE-8233 KNN and SVM algorithms don't work when partition doesn't contain data. You can merge this pull request into a Git repository by running: $ git pull

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

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3806 IGNITE-8232 ML package cleanup for 2.5 release. 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-8237) Ignite blocks on SecurityException in exchange-worker due to unauthorised off-heap cache configuration

Alexey Kukushkin created IGNITE-8237: Summary: Ignite blocks on SecurityException in exchange-worker due to unauthorised off-heap cache configuration Key: IGNITE-8237 URL:

[jira] [Created] (IGNITE-8236) Sporadic NPE in IgniteAtomicSequenceExample

Ivan Artukhov created IGNITE-8236: - Summary: Sporadic NPE in IgniteAtomicSequenceExample Key: IGNITE-8236 URL: https://issues.apache.org/jira/browse/IGNITE-8236 Project: Ignite Issue Type:

[GitHub] ignite pull request #3803: IGNITE-8230

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

[GitHub] ignite pull request #3804: IGNITE-7871 Fixed condition for cache partitions ...

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

[GitHub] ignite pull request #3801: IGNITE-8135

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

[GitHub] ignite pull request #3805: Ignite 1.8.19

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

[GitHub] ignite pull request #3804: IGNITE-7871 Fixed condition for cache partitions ...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3804 IGNITE-7871 Fixed condition for cache partitions validation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8235) Implement execution of selected part of SQL query

Alexander Kalinin created IGNITE-8235: - Summary: Implement execution of selected part of SQL query Key: IGNITE-8235 URL: https://issues.apache.org/jira/browse/IGNITE-8235 Project: Ignite

Some troubles using CacheMode.REPLICATED

Hi All! I have few troubles using Cache in CacheMode.REPLICATED (Ignite 2.4.0). Problem One: 1. Start Ignite N1 with default storage configuration with persistence enabled set to true; 2. Create cache C1 with cache mode = CacheMode.REPLICATED; 3. Create cache C2 with cache mode =

[GitHub] ignite pull request #3788: IGNITE-7824

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

[GitHub] ignite pull request #3803: IGNITE-8230

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

[jira] [Created] (IGNITE-8234) Web console: refactor inputs

Ilya Borisov created IGNITE-8234: Summary: Web console: refactor inputs Key: IGNITE-8234 URL: https://issues.apache.org/jira/browse/IGNITE-8234 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-8233) KNN and SVM algorithms don't work when partition doesn't contain data

Anton Dmitriev created IGNITE-8233: -- Summary: KNN and SVM algorithms don't work when partition doesn't contain data Key: IGNITE-8233 URL: https://issues.apache.org/jira/browse/IGNITE-8233 Project:

[jira] [Created] (IGNITE-8232) ML package cleanup for 2.5 release

Anton Dmitriev created IGNITE-8232: -- Summary: ML package cleanup for 2.5 release Key: IGNITE-8232 URL: https://issues.apache.org/jira/browse/IGNITE-8232 Project: Ignite Issue Type:

[GitHub] ignite pull request #3802: IGNITE-8231 Added timeout to waiting WAL segment ...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/3802 IGNITE-8231 Added timeout to waiting WAL segment archivation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8231) Waiting to WAL segment archivation without timeout

Anton Kalashnikov created IGNITE-8231: - Summary: Waiting to WAL segment archivation without timeout Key: IGNITE-8231 URL: https://issues.apache.org/jira/browse/IGNITE-8231 Project: Ignite

[GitHub] ignite pull request #3801: IGNITE-8135

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

[GitHub] ignite pull request #3800: Mmuzaf ignite 7791

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3800 Mmuzaf ignite 7791 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite mmuzaf-ignite-7791 Alternatively you can review and apply

[GitHub] ignite pull request #3787: IGNITE-8176 Integrate gradient descent linear reg...

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

[GitHub] ignite pull request #3790: IGNITE-8042

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