[jira] [Created] (IGNITE-10791) Avoid unusable network during discovery

David Harvey created IGNITE-10791: - Summary: Avoid unusable network during discovery Key: IGNITE-10791 URL: https://issues.apache.org/jira/browse/IGNITE-10791 Project: Ignite Issue Type:

[jira] [Commented] (IGNITE-10791) Avoid unusable network during discovery

[ https://issues.apache.org/jira/browse/IGNITE-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726837#comment-16726837 ] David Harvey commented on IGNITE-10791: --- Proposed solution is to allow configuration of

[jira] [Updated] (IGNITE-10791) Avoid unusable network during discovery

[ https://issues.apache.org/jira/browse/IGNITE-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-10791: -- Description: Problem:  In some deployments, there are multiple IP addresses,  and  S3

[jira] [Comment Edited] (IGNITE-10244) Peer classloading creates a new class on each call for nested compute tasks

[ https://issues.apache.org/jira/browse/IGNITE-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687091#comment-16687091 ] David Harvey edited comment on IGNITE-10244 at 11/14/18 8:45 PM: - We

[jira] [Commented] (IGNITE-10244) Peer classloading creates a new class on each call for nested compute tasks

[ https://issues.apache.org/jira/browse/IGNITE-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687091#comment-16687091 ] David Harvey commented on IGNITE-10244: --- We found IGNITE-9026 (CONTIGUOUS mode) after giving up

[jira] [Commented] (IGNITE-10135) Documentation link to ClusterNodeAttributeAffinityBackupFilter

[ https://issues.apache.org/jira/browse/IGNITE-10135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676682#comment-16676682 ] David Harvey commented on IGNITE-10135: --- It's in the class definition

[jira] [Commented] (IGNITE-10135) Documentation link to ClusterNodeAttributeAffinityBackupFilter

[ https://issues.apache.org/jira/browse/IGNITE-10135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676009#comment-16676009 ] David Harvey commented on IGNITE-10135: --- 2.7 and later. The constructor, eg., In spring,

[jira] [Created] (IGNITE-10135) Documentation link to ClusterNodeAttributeAffinityBackupFilter

David Harvey created IGNITE-10135: - Summary: Documentation link to ClusterNodeAttributeAffinityBackupFilter Key: IGNITE-10135 URL: https://issues.apache.org/jira/browse/IGNITE-10135 Project: Ignite

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669419#comment-16669419 ] David Harvey commented on IGNITE-9365: -- Clearly an oversight on my part.  [~vkulichenko] can you

[jira] [Commented] (IGNITE-9964) SQL: query by affinity key fails when a table is created from a custom template

[ https://issues.apache.org/jira/browse/IGNITE-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659372#comment-16659372 ] David Harvey commented on IGNITE-9964: -- Related to this?  

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637028#comment-16637028 ] David Harvey commented on IGNITE-7616: -- The purpose of this change, as I understand it,  to

[jira] [Updated] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-7616: - Attachment: image-2018-10-03-10-24-12-459.png > GridDataStreamExecutor and GridCallbackExecutor

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637024#comment-16637024 ] David Harvey commented on IGNITE-7616: -- !image-2018-10-03-10-24-12-459.png! >

[jira] [Updated] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-7616: - Attachment: image-2018-10-03-10-23-24-676.png > GridDataStreamExecutor and GridCallbackExecutor

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637023#comment-16637023 ] David Harvey commented on IGNITE-7616: -- !image-2018-10-03-10-23-24-676.png! >

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625347#comment-16625347 ] David Harvey commented on IGNITE-7616: -- Moved to latest, fixed merge issues, kicked off team-city

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622061#comment-16622061 ] David Harvey commented on IGNITE-9365: -- [~vkulichenko] I pushed a change which implements your very

[jira] [Comment Edited] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620072#comment-16620072 ] David Harvey edited comment on IGNITE-9365 at 9/19/18 11:54 AM:

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620072#comment-16620072 ] David Harvey commented on IGNITE-9365: -- [~vkulichenko], the use case I thinking about is we have a

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619011#comment-16619011 ] David Harvey commented on IGNITE-9365: -- The misspelling of the attribute name would seem to be the

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618388#comment-16618388 ] David Harvey commented on IGNITE-9365: -- Hi [~vkulichenko].   The null case is a configuration

[jira] [Commented] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16612962#comment-16612962 ] David Harvey commented on IGNITE-9026: -- The pull request identifies the production code change we

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611509#comment-16611509 ] David Harvey commented on IGNITE-7616: -- Created a pull request with the work I've already done on

[jira] [Commented] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611324#comment-16611324 ] David Harvey commented on IGNITE-9026: -- We had a related issue that currently appears like separate

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610712#comment-16610712 ] David Harvey commented on IGNITE-9365: -- [~dpavlov] as I read the output, this submission caused no

[jira] [Commented] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609846#comment-16609846 ] David Harvey commented on IGNITE-9026: -- On the test front, it looks like there are no tests at all

[jira] [Assigned] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey reassigned IGNITE-9026: Assignee: David Harvey > Two levels of Peer class loading fails in CONTINUOUS mode >

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609824#comment-16609824 ] David Harvey commented on IGNITE-9365: -- [~sboikov] could you review my changes?  (Note: this is my

[jira] [Comment Edited] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609820#comment-16609820 ] David Harvey edited comment on IGNITE-9365 at 9/10/18 9:33 PM: --- (Note: 

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609820#comment-16609820 ] David Harvey commented on IGNITE-9365: -- (Note:  this is my first submission) I also created Pull

[jira] [Updated] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-9365: - Attachment: master_947962f785_availability_zones_via_spring.patch > Force backups to different

[jira] [Commented] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609705#comment-16609705 ] David Harvey commented on IGNITE-9026: -- I'm finishing my first submission now, and will move to

[jira] [Created] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

David Harvey created IGNITE-9365: Summary: Force backups to different AWS availability zones using only Spring XML Key: IGNITE-9365 URL: https://issues.apache.org/jira/browse/IGNITE-9365 Project:

[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML

[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590829#comment-16590829 ] David Harvey commented on IGNITE-9365: -- I was thinking of adding new class along these lines, where

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575640#comment-16575640 ] David Harvey commented on IGNITE-7616: -- The other  issue is we need a 

[jira] [Comment Edited] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575631#comment-16575631 ] David Harvey edited comment on IGNITE-7616 at 8/10/18 1:09 AM: --- I have a

[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575631#comment-16575631 ] David Harvey commented on IGNITE-7616: -- I have a solution coded and running against 2.5. The main

[jira] [Assigned] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey reassigned IGNITE-7616: Assignee: David Harvey > GridDataStreamExecutor and GridCallbackExecutor JMX beans

[jira] [Updated] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-9026: - I've written a fix, but not the simple unit test that proves the bug & fix. The fix has addressed

[jira] [Created] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

David Harvey created IGNITE-9026: Summary: Two levels of Peer class loading fails in CONTINUOUS mode Key: IGNITE-9026 URL: https://issues.apache.org/jira/browse/IGNITE-9026 Project: Ignite

[jira] [Commented] (IGNITE-8728) Nodes down after other nodes reboot in the cluster

[ https://issues.apache.org/jira/browse/IGNITE-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506080#comment-16506080 ] David Harvey commented on IGNITE-8728: -- Have you validated that you are configured to write through

[jira] [Comment Edited] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc

[ https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456493#comment-16456493 ] David Harvey edited comment on IGNITE-8406 at 4/27/18 2:06 PM: --- I think we

[jira] [Commented] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc

[ https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456493#comment-16456493 ] David Harvey commented on IGNITE-8406: -- The current post condition on flush() is that all futures

[jira] [Comment Edited] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc

[ https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454795#comment-16454795 ] David Harvey edited comment on IGNITE-8406 at 4/26/18 8:15 PM: --- I believe

[jira] [Commented] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc

[ https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454795#comment-16454795 ] David Harvey commented on IGNITE-8406: -- I believe that the code will throw a throw {{CacheException

[jira] [Created] (IGNITE-7905) Setting userVersion in ignite.xml causes ignite.active(true) to fail

David Harvey created IGNITE-7905: Summary: Setting userVersion in ignite.xml causes ignite.active(true) to fail Key: IGNITE-7905 URL: https://issues.apache.org/jira/browse/IGNITE-7905 Project: Ignite

[jira] [Created] (IGNITE-6344) AWS AMI startup.sh gets spurious error on export statment

David Harvey created IGNITE-6344: Summary: AWS AMI startup.sh gets spurious error on export statment Key: IGNITE-6344 URL: https://issues.apache.org/jira/browse/IGNITE-6344 Project: Ignite