Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Yakov, what do you think? On Mon, Feb 27, 2017 at 4:17 PM, Denis Magda wrote: > Frankly, I decided to initiate this discussion after talking to many > Apache Ignite users who had initially thought that > TcpDiscoverySpi.heartbeatsFrequency > manages the heartbeats and they

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Frankly, I decided to initiate this discussion after talking to many Apache Ignite users who had initially thought that TcpDiscoverySpi.heartbeatsFrequency manages the heartbeats and they had tried to tweak it not getting a desired outcome. Even more, TcpDiscoverySpi.heartbeatsFrequenc’s

Re: Additional SQL metrics

BTW, What if we expose per-query metrics below as a part of EXPLAIN ANALYZE? Sergi, is this feasible? — Denis > On Feb 27, 2017, at 2:35 PM, Denis Magda wrote: > > Igniters, > > Let’s shed more light on SQL query execution internals introducing a set of > useful metrics

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

To me it sounds rather as an aesthetic change. Is it really worth breaking the API for this? On Mon, Feb 27, 2017 at 3:30 PM, Denis Magda wrote: > The heartbeats frequency has to be lower than the failure detection > timeout. This is why we decided to calculate the former

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Hi Max, In case we remove the CLOCK mode, I think we should remove the enum too, as well as configuration properties and other code using this enum. Having enum with one value doesn't make sense to me. -Val On Mon, Feb 27, 2017 at 5:09 AM, Kozlov Maxim wrote: > Hi

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

The heartbeats frequency has to be lower than the failure detection timeout. This is why we decided to calculate the former basing on a value set for the latter rather than making a user to adjust both properties properly. This is how both parameters became related some time ago :) Honestly, I

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Hm... I don't think that heartbeat frequency has to be associated with failure detection. What if we just update the javadoc for this parameter, stating that it has to do with metrics update only? On Mon, Feb 27, 2017 at 11:44 AM, Denis Magda wrote: > Igniters, > > Long time

Additional SQL metrics

Igniters, Let’s shed more light on SQL query execution internals introducing a set of useful metrics (https://issues.apache.org/jira/browse/IGNITE-4757). Per-query metrics. Total history size is defined by *CacheConfiguration.getQueryDetailMetricsSize*: * if a query was executed in the

[jira] [Created] (IGNITE-4757) SQL Joins Metrics

Denis Magda created IGNITE-4757: --- Summary: SQL Joins Metrics Key: IGNITE-4757 URL: https://issues.apache.org/jira/browse/IGNITE-4757 Project: Ignite Issue Type: Task Reporter:

Re: Apache Ignite 1.9 testing

Excellent, please let us know when all the tests have been passed so that we can initiate the voting. — Denis > On Feb 27, 2017, at 12:40 PM, Sergey Kozlov wrote: > > Hi Denis > > Update from my side: > > IGNITE-4754 SharedRDDExample missed in example JAR file >

Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Igniters, Long time ago we updated the logic in discovery SPI that issues heartbeats messages from one node to another. Presently, heartbeats frequency is calculated basing on IgniteConfiguration.failureDetectionTimeout meaning that TcpDiscoverySpi.heartbeatsFrequency has nothing to do with

Re: Inaccurate documentation about transactions

+1 to Alexander’s proposal. Alexander, could you wrap the discussion up creating a ticket with detailed explanation what to do? — Denis > On Feb 27, 2017, at 9:01 AM, Dmitriy Setrakyan wrote: > > I like the idea of fixing the exception inheritance. > > On Mon, Feb 27,

Re: Apache Ignite 1.9 testing

Igniters, Any update on this? Sergey, thanks for testing the release. Waiting for an approval from your side to start the voting. — Denis > On Feb 27, 2017, at 12:52 AM, Sergey Kozlov wrote: > > Hi > > I've found two issues amd it seems they related to Spark. > >

Re: [aether-users] Apache Ignite metrics are broken: Eclipse Aether behaves like a web crawler

Hi Herve, Thanks a lot for joining the conversation and providing your thoughts. Highly appreciate this. Let’s keep up the discussion in MVNCENTRAL-1563. — Denis > On Feb 25, 2017, at 12:05 AM, Hervé BOUTEMY wrote: > > Hi Dennis, > > I just added a note on

Re: Google Summer Of Code 2017

Igniters, Unfortunately, we have been rebuffed this year. Thank you for applying to be a Google Summer of Code 2017 mentor organization. Sadly, we were unable to accept Apache Ignite this year. We had many more applications than available slots. We hope you will apply again in the future! —

Re: Inaccurate documentation about transactions

I like the idea of fixing the exception inheritance. On Mon, Feb 27, 2017 at 1:40 AM, Alexandr Kuramshin wrote: > I think annotating the methods with @IgniteTransactional is redundant, > because they are already marked by "throws TransactionTimeoutException/ >

Re: IGNITE-2741 - spring session design

Hi Val, any update on session replication issue ? Thanks, Rishi On Thu, Feb 23, 2017 at 8:07 AM, Rishi Yagnik wrote: > Thanks Val for looking into it. > > On Wed, Feb 22, 2017 at 9:32 PM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > >> Hi Rishi, >> >>

Re: Same Affinity For Same Key On All Caches

Hi. As I investigated the issue occurs when different nodes creates the caches. Say I have 2 nodes node1 and node2 and 2 caches cache1 and cache2. If I create cache1 on node1 and create cache2 on node2 with same FairAffinityFunction with same partition size, keys can map different nodes on

[GitHub] ignite pull request #1579: Ignite 4755

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

[GitHub] ignite pull request #1578: Ignite 3386

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

[GitHub] ignite pull request #1577: ignite-4740 - Service could be deployed/undeploye...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1577 ignite-4740 - Service could be deployed/undeployed twice on concurrent cancel and discovery event You can merge this pull request into a Git repository by running: $ git pull

Remove CacheAtomicWriteOrderMode.CLOCK mode.

Hi Igniters, After remove CLOCK mode, CacheAtomicWriteOrderMode enum contains now only one value PRIMARY. Andrey Gura, proposition remove CacheAtomicWriteOrderMode enum. Will there be something special for this purpose is enum? jira: https://issues.apache.org/jira/browse/IGNITE-4587

[jira] [Created] (IGNITE-4756) Print info about partition distribution to log

Taras Ledkov created IGNITE-4756: Summary: Print info about partition distribution to log Key: IGNITE-4756 URL: https://issues.apache.org/jira/browse/IGNITE-4756 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4755) Print a warning when option 'ignite.job.shared.classloader' is on.

Ivan Veselovsky created IGNITE-4755: --- Summary: Print a warning when option 'ignite.job.shared.classloader' is on. Key: IGNITE-4755 URL: https://issues.apache.org/jira/browse/IGNITE-4755 Project:

[GitHub] ignite pull request #1576: IGNITE-4752 Hadoop examples fail for hadoop accel...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1576 IGNITE-4752 Hadoop examples fail for hadoop accelerator You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4752

[GitHub] ignite pull request #1562: IGNITE-4735: Excluded CPP sources.

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1562 --- 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

[GitHub] ignite pull request #1430: IGNITE-1680: Implemented basic API for user entry...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1430 --- 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

[GitHub] ignite pull request #1547: IGNITE-4670: Added LoadCache and LocalLoadCache m...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1547 --- 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

[GitHub] ignite pull request #819: IGNITE-3330: Cache::Invoke method implemented.

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/819 --- 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

[GitHub] ignite pull request #1570: IGNITE-4745: Removed unused targetver.h files

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1570 --- 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

[GitHub] ignite pull request #1575: IGNITE-3018: RendezvousAffinityFunction performan...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1575 IGNITE-3018: RendezvousAffinityFunction performance tuning You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #684: IGNITE-3018 Cache affinity calculation is slow wit...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/684 --- 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

Re: Inaccurate documentation about transactions

I think annotating the methods with @IgniteTransactional is redundant, because they are already marked by "throws TransactionTimeoutException/TransactionRollbackException/TransactionHeuristicException". For example, the same approach was used in JavaBeans 1.01 specs [1] with

Re: IGNITE-4404 long running test refactoring - how to refactor?

I think we can keep this numbers for atomic behavior and decrease for transactional. But which tests can be replaced with mocks if they all use node's cache? 2017-02-22 12:47 GMT+03:00 Константин Дудков : > Answered to ticket. It's more about testing process than real refactoring

Apache Ignite 1.9 testing

Hi I've found two issues amd it seems they related to Spark. IGNITE-4754 SharedRDDExample missed in example JAR file IGNITE-4752 Hadoop examples fail for hadoop accelerator Could someone

[GitHub] ignite pull request #1574: IGNITE-4754 SharedRDDExample missed in example JA...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1574 IGNITE-4754 SharedRDDExample missed in example JAR file You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4754

[GitHub] ignite pull request #1573: IGNITE-3487 Removed _key and _val from table colu...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1573 IGNITE-3487 Removed _key and _val from table column list You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-4754) SharedRDDExample missed in example JAR file

Sergey Kozlov created IGNITE-4754: - Summary: SharedRDDExample missed in example JAR file Key: IGNITE-4754 URL: https://issues.apache.org/jira/browse/IGNITE-4754 Project: Ignite Issue Type: