Re: Resurrect FairAffinityFunction

On Tue, Aug 15, 2017 at 10:35 PM, Vladimir Ozerov wrote: > Valya, > > And this is the problem! ) We have another implementation which minimizes > movements - rendezvous. Fair affinity should not bother about partition > migration. This is not a feature, but a bug in implementation of > FairAffini

[jira] [Created] (IGNITE-6072) SQL: client node should not hold the whole data set in-memory when possible when merge table is there

Vladimir Ozerov created IGNITE-6072: --- Summary: SQL: client node should not hold the whole data set in-memory when possible when merge table is there Key: IGNITE-6072 URL: https://issues.apache.org/jira/browse/IG

[GitHub] ignite pull request #2430: IGNITE-6019

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2430 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

Re: Ignite not friendly for Monitoring

Denis, IGNITE-5620 is completely different thing. Let's do not mix cluster monitoring and parser errors. ср, 16 авг. 2017 г. в 2:57, Denis Magda : > Alexey, > > Didn’t know that such an improvement as consistent IDs for errors and > events can be used as an integration point with the DevOps tool

Re: Resurrect FairAffinityFunction

Dima, It is not hard to implement. It is hard to reason on whether your query will fail or not. Moreover, cache groups is an antipattern for SQL, personally I do not want users to use it unless absolutely needed (large topologies, large number of caches). Also take in count that the same problem w

Re: Resurrect FairAffinityFunction

Valya, And this is the problem! ) We have another implementation which minimizes movements - rendezvous. Fair affinity should not bother about partition migration. This is not a feature, but a bug in implementation of FairAffinityFunction. Let's fix that and forget about topology versions. ср, 16

Re: Default page size must be changed to 4k. Should it be backwards compatible?

#1 option looks more predictable. But it's possible to add a message "for better IO performance please migrate to 4K-pages". BR, Serge On Wed, 16 Aug 2017 at 03:46, Dmitriy Setrakyan wrote: > I like #1 if possible. Of course, if the LFS is empty, then the new default > should be 4k. > > On Tue

Re: Ignite: configuration changes at runtime

Yakov, I don't like the idea of intermixing changeable properties with constant ones in the configuration. Moreover, the standard configuration class is local to the node, while changing the config properties at runtime may be a distributed operation that needs to be propagated across the cluster.

Request for contributor permission

Dear Ignite Team, I would like to work on this issue: https://issues.apache.org/jira/browse/IGNITE-5994 Please add me in Jira and my Jira id is shia. Zhang Yuan

Re: Default page size must be changed to 4k. Should it be backwards compatible?

I like #1 if possible. Of course, if the LFS is empty, then the new default should be 4k. On Tue, Aug 15, 2017 at 12:01 PM, Ivan Rakov wrote: > Guys, > > We have benchmarked how checkpoint write speed on SSD disk depends on > various parameters. It became absolutely obvious that using 4K pages i

Re: Resurrect FairAffinityFunction

On Tue, Aug 15, 2017 at 1:12 PM, Vladimir Ozerov wrote: > I do not like the idea as it would make it very hard to reason about > whether your SQL will fail or not. Let's looks at the problem from the > different angle. I have this question for years - why in the world *fair* > affinity function,

Re: Resurrect FairAffinityFunction

Vladimir, I would let other guys confirm, but I believe the reason is that if it recalculates distribution every time from scratch, it would trigger too much redundant data movement during rebalancing. Fair function not only tries to provide best possible distribution, but also minimizes this data

Re: Ignite not friendly for Monitoring

Alexey, Didn’t know that such an improvement as consistent IDs for errors and events can be used as an integration point with the DevOps tools. Thanks for sharing your experience with us. Would you step in as a architect for this task and make out a JIRA ticket with all the required informatio

Re: Service versioning

Ilya, Every Service Grid user will welcome this feature. Fully for it. Mentioned in the ticket that it has to be documented before the ticket is closed. — Denis > On Aug 15, 2017, at 8:18 AM, Ilya Lantukh wrote: > > Igniters, > > Our current ServiceGrid implementation lacks several importan

Re: Asking to become a contributor: ilyak

Ilya, Welcome! Added you to the list. — Denis > On Aug 15, 2017, at 7:31 AM, Ilya Kasnacheev > wrote: > > Hello, Apache Ignite community. > > Can you please enable contributor rights on IGNITE for my JIRA Username > ilyak. > > I have already familiarized myself with development and contribu

Re: Control.sh script and cluster activation

Add a documentation requirement. Ping me when the ticket is about to be closed. In the meanwhile, I’ll try to document the existing behavior. — Denis > On Aug 15, 2017, at 1:45 AM, Dmitriy Govorukhin > wrote: > > Folks, > > I created jira issue for the current discussion IGNITE-6064 >

Re: [Webinar] Apache Process Overview, Aug 10, 2017 9.00 AM - 10.00 AM PT

Igniters, Those who missed the webinar can watch the recoding: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ApacheWay Cos, thanks a lot for presentation! — D

Re: Resurrect FairAffinityFunction

I do not like the idea as it would make it very hard to reason about whether your SQL will fail or not. Let's looks at the problem from the different angle. I have this question for years - why in the world *fair* affinity function, whose only ultimate goal is to provide equal partition distributio

Default page size must be changed to 4k. Should it be backwards compatible?

Guys, We have benchmarked how checkpoint write speed on SSD disk depends on various parameters. It became absolutely obvious that using 4K pages in durable memory instead of 2K brings considerable, significant speed-up. I think, we must set 4K as default page size. Ticket with detailed explana

[GitHub] ignite pull request #2449: fair-aff-fix

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/2449 fair-aff-fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite fair-aff-fix Alternatively you can review and apply these ch

Re: Ignite not friendly for Monitoring

Hi Alexey, A nice thing about delegating alerting to 3rd party enterprise systems is that those systems already deal with lots of things including distributed apps. What is needed from Ignite is to consistently write to log files (again that means stable event IDs, proper event granularity, no re

[jira] [Created] (IGNITE-6071) Client may detect necessity for reconnect for too long

Yakov Zhdanov created IGNITE-6071: - Summary: Client may detect necessity for reconnect for too long Key: IGNITE-6071 URL: https://issues.apache.org/jira/browse/IGNITE-6071 Project: Ignite Iss

[jira] [Created] (IGNITE-6070) Infinite redirects at Spring Security Web Session Clustering with Tomcat

Ilya Kasnacheev created IGNITE-6070: --- Summary: Infinite redirects at Spring Security Web Session Clustering with Tomcat Key: IGNITE-6070 URL: https://issues.apache.org/jira/browse/IGNITE-6070 Projec

How to add new build-plan in the TeamCity?

Hi Igniters! I am working on new test module in the Ignite project [1]. I need check than it will work in the TeamCity [2]. I have no permissions to create new configuration. How to add new build-plan in the TeamCity according to test-suite within new module? [1] https://issues.apache.org/jira

Re: Multi-Version Concurrency Control

Serge, Cool feature! I have following questions: 1) MVCC will be a kind of "cache mode"? And we can have caches with old behavior and caches with MVCC? 2) " Garbage collection" - may be we should give another name to not intersect with JVM GC? Thanks! On Tue, Aug 15, 2017 at 8:11 PM, Serge Puch

Service versioning

Igniters, Our current ServiceGrid implementation lacks several important features, one of which is ability to upgrade Service without downtime. I've created ticket to add this feature: https://issues.apache.org/jira/browse/IGNITE-6069. To implement it, the following problems must be solved: - cu

Re: Ignite not friendly for Monitoring

Alexey, How you are going to deal with distributed nature of Ignite cluster? And how do you propose handle nodes restart / stop? On Tue, Aug 15, 2017 at 9:12 PM, Alexey Kukushkin < alexeykukush...@yahoo.com.invalid> wrote: > Hi Denis, > Monitoring tools simply watch event logs for patterns (rege

[jira] [Created] (IGNITE-6069) Service versioning

Ilya Lantukh created IGNITE-6069: Summary: Service versioning Key: IGNITE-6069 URL: https://issues.apache.org/jira/browse/IGNITE-6069 Project: Ignite Issue Type: New Feature Compone

Asking to become a contributor: ilyak

Hello, Apache Ignite community. Can you please enable contributor rights on IGNITE for my JIRA Username ilyak. I have already familiarized myself with development and contribution process. Thanks in advance.

Re: Ignite not friendly for Monitoring

Hi Denis, Monitoring tools simply watch event logs for patterns (regex in case of unstructured logs like text files). A stable (not changing in new releases) event ID identifying specific issue would be such a pattern.  We need to introduce such event IDs according to the principles I described i

[GitHub] ignite pull request #2431: IGNITE-6032 ODBC: Added SQL_SCROLL_OPTIONS suppor...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2431 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is en

[GitHub] ignite pull request #2448: IGNITE-6050

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

[GitHub] ignite pull request #2445: IGNITE-6067 move initialize() to GridCacheUtils

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2445 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[jira] [Created] (IGNITE-6068) We try to add entry to partition which was concurrently evicted

Eduard Shangareev created IGNITE-6068: - Summary: We try to add entry to partition which was concurrently evicted Key: IGNITE-6068 URL: https://issues.apache.org/jira/browse/IGNITE-6068 Project: Ig

[GitHub] ignite pull request #2447: IGNITE-6051

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

[GitHub] ignite pull request #2446: IGNITE-4642 Support enforceJoinOrder flag for JDB...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2446 IGNITE-4642 Support enforceJoinOrder flag for JDBC driver You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignit

[GitHub] ignite pull request #2444: IGNITE-6063

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2444 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[GitHub] ignite pull request #2445: IGNITE-6067 move initialize() to GridCacheUtils

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/2445 IGNITE-6067 move initialize() to GridCacheUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6067 Alternative

Re: Ignite: configuration changes at runtime

> I like the idea, but I am not sure how we will separate properties that are >dynamically changeable from the constant ones. Why do you want the separation? I thought having some annotation like @RuntimeChangeSupported will be sufficient for documentation >Also, what is the API for updating thes

[jira] [Created] (IGNITE-6067) Refactor cache configuration initialization with proper defaults

Konstantin Dudkov created IGNITE-6067: - Summary: Refactor cache configuration initialization with proper defaults Key: IGNITE-6067 URL: https://issues.apache.org/jira/browse/IGNITE-6067 Project: I

Re: Ignite: configuration changes at runtime

>I would also add to CacheConfiguration: > StatisticsEnabled: on / off > QueryDetailMetricsSize: change size Alex, feel free to put your suggestions to the page. >Please also implement an API that could be used from UI tools (Web Console > and Visor Cmd). Of course we will implement API and init

[jira] [Created] (IGNITE-6066) Grid hangs on partition map exhcange during failover test with 30 physical caches and PDS

Ksenia Rybakova created IGNITE-6066: --- Summary: Grid hangs on partition map exhcange during failover test with 30 physical caches and PDS Key: IGNITE-6066 URL: https://issues.apache.org/jira/browse/IGNITE-6066

[jira] [Created] (IGNITE-6065) Quick way to find broken documentation links

Ilya Borisov created IGNITE-6065: Summary: Quick way to find broken documentation links Key: IGNITE-6065 URL: https://issues.apache.org/jira/browse/IGNITE-6065 Project: Ignite Issue Type: Tes

Re: Control.sh script and cluster activation

Folks, I created jira issue for the current discussion IGNITE-6064 , leave you comment please. On Tue, Aug 15, 2017 at 11:32 AM, Dmitriy Setrakyan wrote: > Added one more suggestion below. BTW, if there is no ticket, let's create > one and copy

Re: Batch service deployment

Denis, I don't think we need a king deployment result. The "deployAllAsync" method should never throw an exception, it should always return the future. However, the IgniteFuture.get(...) method does throw an exception, and in this exception you should provide the info about the failures. D. On

[jira] [Created] (IGNITE-6064) Rework control.sh script.

Dmitriy Govorukhin created IGNITE-6064: -- Summary: Rework control.sh script. Key: IGNITE-6064 URL: https://issues.apache.org/jira/browse/IGNITE-6064 Project: Ignite Issue Type: Improvemen

Re: Control.sh script and cluster activation

Added one more suggestion below. BTW, if there is no ticket, let's create one and copy all the suggestions there. On Tue, Aug 15, 2017 at 1:13 AM, Dmitriy Setrakyan wrote: > Guys, > > Where is the ticket for adding control.[sh|bat] script to the bin folder? > I cannot find any mention of it. Was

Re: Batch service deployment

Dmitriy, thank you for your reply! I see a possibility of a bad scenario here. If we use deployAllAsync method and it throws an exception, then the constructed future won't be returned and we won't have a way to wait for the rest of the services to deploy. Maybe we should return some king of deplo

[GitHub] ignite pull request #2420: IGNITE-6004 SQL: add "inlineSize" to QuerySqlFiel...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2420 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

Re: Control.sh script and cluster activation

Guys, Where is the ticket for adding control.[sh|bat] script to the bin folder? I cannot find any mention of it. Was there a discussion on the dev list? Here are the issues I am seeing with the script: 1. It could be named better. Perhaps the name "cluster-ops" or "cluster-switch" would be

Re: Control.sh script and cluster activation

Valentin, We have jira issue for this IGNITE-5586 On Tue, Aug 15, 2017 at 10:56 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > > Denis, > > 1. control.sh have help parameter. If you try enter ./control.sh --help, > result is an

Re: Control.sh script and cluster activation

Denis, 1. control.sh have help parameter. If you try enter ./control.sh --help, result is an example of how to use it, "Example: --host {ip} --port {port} --{activate/deactivate} or without command --host {ip} --port {port} then will print status" 2. Visorcmd will start daemon node and join in to

[GitHub] ignite pull request #2444: IGNITE-6063

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

[jira] [Created] (IGNITE-6063) InlineIdexHelperTest fails

Igor Seliverstov created IGNITE-6063: Summary: InlineIdexHelperTest fails Key: IGNITE-6063 URL: https://issues.apache.org/jira/browse/IGNITE-6063 Project: Ignite Issue Type: Test

[jira] [Created] (IGNITE-6062) IllegalArgumentException thrown while getHeapMemoryUsage()

Alexander Belyak created IGNITE-6062: Summary: IllegalArgumentException thrown while getHeapMemoryUsage() Key: IGNITE-6062 URL: https://issues.apache.org/jira/browse/IGNITE-6062 Project: Ignite