[jira] [Commented] (IGNITE-13633) thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)

[ https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243913#comment-17243913 ] Vyacheslav Daradur commented on IGNITE-13633: - Merged to master. [~alex_pl], thank you for

[jira] [Commented] (IGNITE-13633) thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)

[ https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242669#comment-17242669 ] Vyacheslav Daradur commented on IGNITE-13633: - [~alex_pl], the changes lgtm. Let's getting

[jira] [Commented] (IGNITE-13633) thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)

[ https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227949#comment-17227949 ] Vyacheslav Daradur commented on IGNITE-13633: - I'll have a look next week. > thin clients

[jira] [Commented] (IGNITE-13312) Methods of interface Binarylizable should not get access to host resources.

[ https://issues.apache.org/jira/browse/IGNITE-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181850#comment-17181850 ] Vyacheslav Daradur commented on IGNITE-13312: - [~garus.d.g], lgtm, merged to master. Thank

[jira] [Commented] (IGNITE-10100) Add public Java API to call Ignite.NET services

[ https://issues.apache.org/jira/browse/IGNITE-10100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113800#comment-17113800 ] Vyacheslav Daradur commented on IGNITE-10100: - [~alex_pl], please go forward if you have

[jira] [Commented] (IGNITE-12490) Service proxy throws "Service not found" exception right after deploy

[ https://issues.apache.org/jira/browse/IGNITE-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108599#comment-17108599 ] Vyacheslav Daradur commented on IGNITE-12490: - Service deployment guarantees were improved

[jira] [Resolved] (IGNITE-12490) Service proxy throws "Service not found" exception right after deploy

[ https://issues.apache.org/jira/browse/IGNITE-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-12490. - Resolution: Fixed > Service proxy throws "Service not found" exception right

[jira] [Updated] (IGNITE-12490) Service proxy throws "Service not found" exception right after deploy

[ https://issues.apache.org/jira/browse/IGNITE-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-12490: Fix Version/s: 2.9 > Service proxy throws "Service not found" exception right

[jira] [Updated] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-12894: Fix Version/s: 2.9 > Cannot use IgniteAtomicSequence in Ignite services >

[jira] [Commented] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108597#comment-17108597 ] Vyacheslav Daradur commented on IGNITE-12894: - [~PetrovMikhail], merged to master. Thanks

[jira] [Commented] (IGNITE-10100) Add public Java API to call Ignite.NET services

[ https://issues.apache.org/jira/browse/IGNITE-10100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108037#comment-17108037 ] Vyacheslav Daradur commented on IGNITE-10100: - I'll take a look next week. > Add public

[jira] [Commented] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106192#comment-17106192 ] Vyacheslav Daradur commented on IGNITE-12894: - Hi, [~PetrovMikhail]. I can't find a link to

[jira] [Commented] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099326#comment-17099326 ] Vyacheslav Daradur commented on IGNITE-12894: - [~PetrovMikhail], the suggestion proposed by

[jira] [Comment Edited] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091560#comment-17091560 ] Vyacheslav Daradur edited comment on IGNITE-12894 at 4/24/20, 1:21 PM:

[jira] [Comment Edited] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091560#comment-17091560 ] Vyacheslav Daradur edited comment on IGNITE-12894 at 4/24/20, 1:16 PM:

[jira] [Issue Comment Deleted] (IGNITE-12490) Service proxy throws "Service not found" exception right after deploy

[ https://issues.apache.org/jira/browse/IGNITE-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-12490: Comment: was deleted (was: Both issues: this and IGNITE-12490 can be fixed by

[jira] [Commented] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

[ https://issues.apache.org/jira/browse/IGNITE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091560#comment-17091560 ] Vyacheslav Daradur commented on IGNITE-12894: - Both issues: this and IGNITE-12490 can be

[jira] [Commented] (IGNITE-12490) Service proxy throws "Service not found" exception right after deploy

[ https://issues.apache.org/jira/browse/IGNITE-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091558#comment-17091558 ] Vyacheslav Daradur commented on IGNITE-12490: - Both issues: this and IGNITE-12490 can be

[jira] [Commented] (IGNITE-11905) [IEP-35] Monitoring Phase 2

[ https://issues.apache.org/jira/browse/IGNITE-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926087#comment-16926087 ] Vyacheslav Daradur commented on IGNITE-11905: - [~NIzhikov], thank you for the patch, great

[jira] [Commented] (IGNITE-11848) [IEP-35] Monitoring Phase 1

[ https://issues.apache.org/jira/browse/IGNITE-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863454#comment-16863454 ] Vyacheslav Daradur commented on IGNITE-11848: - [~NIzhikov] Looks good to me. Please run

[jira] [Commented] (IGNITE-11277) Use maven plugin as default code style checker for project

[ https://issues.apache.org/jira/browse/IGNITE-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823474#comment-16823474 ] Vyacheslav Daradur commented on IGNITE-11277: - [~Mmuzaf], the changes merged to master.

[jira] [Commented] (IGNITE-11277) Use maven plugin as default code style checker for project

[ https://issues.apache.org/jira/browse/IGNITE-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16822749#comment-16822749 ] Vyacheslav Daradur commented on IGNITE-11277: - [~Mmuzaf], I looked through the PR and have

[jira] [Commented] (IGNITE-11127) GridDhtInvalidPartitionException not handled by GridCacheTtlManager

[ https://issues.apache.org/jira/browse/IGNITE-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804830#comment-16804830 ] Vyacheslav Daradur commented on IGNITE-11127: - [~roman_s], I'm a bit late :) The fix looks

[jira] [Updated] (IGNITE-11539) Document services hot redeployment via DeploymentSpi

[ https://issues.apache.org/jira/browse/IGNITE-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-11539: Labels: iep-17 (was: ) > Document services hot redeployment via DeploymentSpi >

[jira] [Created] (IGNITE-11539) Document services hot redeployment via DeploymentSpi

Vyacheslav Daradur created IGNITE-11539: --- Summary: Document services hot redeployment via DeploymentSpi Key: IGNITE-11539 URL: https://issues.apache.org/jira/browse/IGNITE-11539 Project: Ignite

[jira] [Updated] (IGNITE-11384) Introduce an ability of services hot redeployment via DeploymentSpi

[ https://issues.apache.org/jira/browse/IGNITE-11384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-11384: Labels: iep-17 (was: ) > Introduce an ability of services hot redeployment via

[jira] [Updated] (IGNITE-11384) Introduce an ability of services hot redeployment via DeploymentSpi

[ https://issues.apache.org/jira/browse/IGNITE-11384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-11384: Summary: Introduce an ability of services hot redeployment via DeploymentSpi

[jira] [Created] (IGNITE-11384) Introduce an opportunity of services hot redeployment via DeploymentSpi

Vyacheslav Daradur created IGNITE-11384: --- Summary: Introduce an opportunity of services hot redeployment via DeploymentSpi Key: IGNITE-11384 URL: https://issues.apache.org/jira/browse/IGNITE-11384

[jira] [Assigned] (IGNITE-6259) GridServiceProcessor may leave futures hanging on unstable topology

[ https://issues.apache.org/jira/browse/IGNITE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-6259: -- Assignee: (was: Vyacheslav Daradur) > GridServiceProcessor may leave

[jira] [Commented] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange

[ https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744807#comment-16744807 ] Vyacheslav Daradur commented on IGNITE-10021: - [~oignatenko], the issue is not actual for

[jira] [Updated] (IGNITE-6259) GridServiceProcessor may leave futures hanging on unstable topology

[ https://issues.apache.org/jira/browse/IGNITE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-6259: --- Fix Version/s: (was: 2.8) > GridServiceProcessor may leave futures hanging on

[jira] [Assigned] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange

[ https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-10021: --- Assignee: (was: Vyacheslav Daradur) >

[jira] [Updated] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange

[ https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10021: Fix Version/s: (was: 2.8) > IgniteInterruptedCheckedException: sleep

[jira] [Commented] (IGNITE-8656) GridServiceProcessor does re-assignment even if no assignment is changed

[ https://issues.apache.org/jira/browse/IGNITE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744797#comment-16744797 ] Vyacheslav Daradur commented on IGNITE-8656: [~mcherkasov], I'd suggest closing the issue

[jira] [Resolved] (IGNITE-8630) Node filter IgnitePredicate executes twice during deploying on one single node cluster

[ https://issues.apache.org/jira/browse/IGNITE-8630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-8630. Resolution: Won't Fix I closed the issue because it is not actual since 

[jira] [Assigned] (IGNITE-8630) Node filter IgnitePredicate executes twice during deploying on one single node cluster

[ https://issues.apache.org/jira/browse/IGNITE-8630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-8630: -- Assignee: Vyacheslav Daradur > Node filter IgnitePredicate executes twice

[jira] [Assigned] (IGNITE-2907) GridServiceNotFoundException is not descriptive

[ https://issues.apache.org/jira/browse/IGNITE-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-2907: -- Assignee: (was: Vyacheslav Daradur) > GridServiceNotFoundException is

[jira] [Resolved] (IGNITE-10116) Document implemented design of Service Grid (redesign phase 1)

[ https://issues.apache.org/jira/browse/IGNITE-10116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-10116. - Resolution: Done The article has been updated according to merged solution 

[jira] [Commented] (IGNITE-10899) Service Grid: disconnecting during node stop may lead to deadlock

[ https://issues.apache.org/jira/browse/IGNITE-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741384#comment-16741384 ] Vyacheslav Daradur commented on IGNITE-10899: - [~EdShangGG], could you review the solution,

[jira] [Commented] (IGNITE-10888) .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate

[ https://issues.apache.org/jira/browse/IGNITE-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741382#comment-16741382 ] Vyacheslav Daradur commented on IGNITE-10888: - [~avinogradov], could you help with review

[jira] [Created] (IGNITE-10910) GridTaskProcessor#onKernalStop may lead to a deadlock and execution timeout in "SPI" TC build-plan

Vyacheslav Daradur created IGNITE-10910: --- Summary: GridTaskProcessor#onKernalStop may lead to a deadlock and execution timeout in "SPI" TC build-plan Key: IGNITE-10910 URL:

[jira] [Updated] (IGNITE-10899) Service Grid: disconnecting during node stop may lead to deadlock

[ https://issues.apache.org/jira/browse/IGNITE-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10899: Description: In a rare case {{onDisconneced}} may be called during node stopping

[jira] [Updated] (IGNITE-10899) Service Grid: disconnecting during node stop may lead to deadlock

[ https://issues.apache.org/jira/browse/IGNITE-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10899: Description: In a rare case {{onDisconneced}} may be called during node stopping

[jira] [Created] (IGNITE-10899) Service Grid: disconnecting during node stop may lead to deadlock

Vyacheslav Daradur created IGNITE-10899: --- Summary: Service Grid: disconnecting during node stop may lead to deadlock Key: IGNITE-10899 URL: https://issues.apache.org/jira/browse/IGNITE-10899

[jira] [Commented] (IGNITE-10888) .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate

[ https://issues.apache.org/jira/browse/IGNITE-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740211#comment-16740211 ] Vyacheslav Daradur commented on IGNITE-10888: - *Summary:* In the .NET tests is checked

[jira] [Updated] (IGNITE-10888) .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate

[ https://issues.apache.org/jira/browse/IGNITE-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10888: Labels: MakeTeamcityGreenAgain Muted_test (was: MakeTeamcityGreenAgain) > .NET:

[jira] [Created] (IGNITE-10888) .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate

Vyacheslav Daradur created IGNITE-10888: --- Summary: .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate Key: IGNITE-10888 URL: https://issues.apache.org/jira/browse/IGNITE-10888

[jira] [Updated] (IGNITE-10888) .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate

[ https://issues.apache.org/jira/browse/IGNITE-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10888: Labels: MakeTeamcityGreenAgain (was: ) > .NET:

[jira] [Created] (IGNITE-10862) Introduce tool to free up space on a disc of unused memory pages

Vyacheslav Daradur created IGNITE-10862: --- Summary: Introduce tool to free up space on a disc of unused memory pages Key: IGNITE-10862 URL: https://issues.apache.org/jira/browse/IGNITE-10862

[jira] [Commented] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations

[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730051#comment-16730051 ] Vyacheslav Daradur commented on IGNITE-10811: - [~NIzhikov], could you review the prepared

[jira] [Updated] (IGNITE-10830) Return back semantic of GridServiceProcessor$ServiceTopologyCallable to avoid possible serialization issues

[ https://issues.apache.org/jira/browse/IGNITE-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10830: Summary: Return back semantic of GridServiceProcessor$ServiceTopologyCallable to

[jira] [Updated] (IGNITE-10830) Return back semantic of GridServiceProcessor$ServiceTopologyCallable to avoid possible serialization issues

[ https://issues.apache.org/jira/browse/IGNITE-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10830: Description: It's necessary to revert changes of

[jira] [Created] (IGNITE-10830) Return back semantic of GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization issues

Vyacheslav Daradur created IGNITE-10830: --- Summary: Return back semantic of GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization issues Key: IGNITE-10830 URL:

[jira] [Commented] (IGNITE-6259) GridServiceProcessor may leave futures hanging on unstable topology

[ https://issues.apache.org/jira/browse/IGNITE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729455#comment-16729455 ] Vyacheslav Daradur commented on IGNITE-6259: [~dmekhanikov], the issue has been resolved in

[jira] [Resolved] (IGNITE-3392) Propagate service deployment results from assigned nodes to initiator

[ https://issues.apache.org/jira/browse/IGNITE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-3392. Resolution: Done The task has been implemented within IGNITE-9607. > Propagate

[jira] [Resolved] (IGNITE-9075) Service Grid: Lifecycle of affinity deployed service should be reworked

[ https://issues.apache.org/jira/browse/IGNITE-9075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-9075. Resolution: Done The task has been implemented within IGNITE-9607. > Service

[jira] [Resolved] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.

[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-1478. Resolution: Fixed The issue has been solved within IGNITE-9607. > Service cannot

[jira] [Resolved] (IGNITE-8363) Handle topology changes during service deployment

[ https://issues.apache.org/jira/browse/IGNITE-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-8363. Resolution: Done The task has been implemented within IGNITE-9607. > Handle

[jira] [Resolved] (IGNITE-8362) Collect service deployment results asynchronously on coordinator

[ https://issues.apache.org/jira/browse/IGNITE-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-8362. Resolution: Done The task has been implemented within IGNITE-9607. > Collect

[jira] [Resolved] (IGNITE-8361) Use discovery messages for service deployment

[ https://issues.apache.org/jira/browse/IGNITE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur resolved IGNITE-8361. Resolution: Done The task has been implemented within IGNITE-9607. > Use

[jira] [Commented] (IGNITE-9607) Service Grid redesign - phase 1

[ https://issues.apache.org/jira/browse/IGNITE-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728758#comment-16728758 ] Vyacheslav Daradur commented on IGNITE-9607: The method {{onLocalJoin}} has been moved in 

[jira] [Commented] (IGNITE-9607) Service Grid redesign - phase 1

[ https://issues.apache.org/jira/browse/IGNITE-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728749#comment-16728749 ] Vyacheslav Daradur commented on IGNITE-9607: [~agoncharuk], thank you for the notes!

[jira] [Created] (IGNITE-10817) Service Grid: Introduce diagnostic tool to dump pending deployment tasks

Vyacheslav Daradur created IGNITE-10817: --- Summary: Service Grid: Introduce diagnostic tool to dump pending deployment tasks Key: IGNITE-10817 URL: https://issues.apache.org/jira/browse/IGNITE-10817

[jira] [Commented] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests

[ https://issues.apache.org/jira/browse/IGNITE-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728699#comment-16728699 ] Vyacheslav Daradur commented on IGNITE-10715: - The ticket has been reopened because of

[jira] [Updated] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations

[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10811: Description: It's necessary to add new build configuration on TeamCity (after

[jira] [Updated] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations

[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10811: Description: It's necessary to add new build configuration on TeamCity (after

[jira] [Created] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations

Vyacheslav Daradur created IGNITE-10811: --- Summary: Add new TC build-config to test Service Grid new and old implementations Key: IGNITE-10811 URL: https://issues.apache.org/jira/browse/IGNITE-10811

[jira] [Commented] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests

[ https://issues.apache.org/jira/browse/IGNITE-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725665#comment-16725665 ] Vyacheslav Daradur commented on IGNITE-10715: - [~avinogradov], could you review the PR,

[jira] [Created] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests

Vyacheslav Daradur created IGNITE-10715: --- Summary: Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests Key: IGNITE-10715 URL: https://issues.apache.org/jira/browse/IGNITE-10715

[jira] [Updated] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest

[ https://issues.apache.org/jira/browse/IGNITE-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10705: Description: Found that method

[jira] [Updated] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest

[ https://issues.apache.org/jira/browse/IGNITE-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10705: Description: Found that method

[jira] [Created] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest

Vyacheslav Daradur created IGNITE-10705: --- Summary: Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest Key: IGNITE-10705 URL: https://issues.apache.org/jira/browse/IGNITE-10705

[jira] [Updated] (IGNITE-10615) Ignite Compatibility: fix arguments' checking in the node runner

[ https://issues.apache.org/jira/browse/IGNITE-10615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10615: Issue Type: Bug (was: Improvement) > Ignite Compatibility: fix arguments'

[jira] [Created] (IGNITE-10615) Ignite Compatibility: fix arguments' checking in the node runner

Vyacheslav Daradur created IGNITE-10615: --- Summary: Ignite Compatibility: fix arguments' checking in the node runner Key: IGNITE-10615 URL: https://issues.apache.org/jira/browse/IGNITE-10615

[jira] [Commented] (IGNITE-10555) Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'

[ https://issues.apache.org/jira/browse/IGNITE-10555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713924#comment-16713924 ] Vyacheslav Daradur commented on IGNITE-10555: - The "Hibernate 1" test suite fails in master

[jira] [Created] (IGNITE-10555) Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'

Vyacheslav Daradur created IGNITE-10555: --- Summary: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder' Key: IGNITE-10555 URL:

[jira] [Updated] (IGNITE-10442) Failed checks on successful tasks canceling

[ https://issues.apache.org/jira/browse/IGNITE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10442: Ignite Flags: (was: Docs Required) > Failed checks on successful tasks

[jira] [Updated] (IGNITE-10442) Failed checks on successful tasks canceling

[ https://issues.apache.org/jira/browse/IGNITE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10442: Fix Version/s: 2.8 > Failed checks on successful tasks canceling >

[jira] [Commented] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.

[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709833#comment-16709833 ] Vyacheslav Daradur commented on IGNITE-9023: [~DmitriyGovorukhin], thank you for the review!

[jira] [Commented] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version

[ https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708903#comment-16708903 ] Vyacheslav Daradur commented on IGNITE-10523: - [~dpavlov], please, have a look at the

[jira] [Updated] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version

[ https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10523: Fix Version/s: 2.8 > Ignite Compatibility: add check that started node is of

[jira] [Created] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version

Vyacheslav Daradur created IGNITE-10523: --- Summary: Ignite Compatibility: add check that started node is of expected version Key: IGNITE-10523 URL: https://issues.apache.org/jira/browse/IGNITE-10523

[jira] [Commented] (IGNITE-8379) Add maven-surefire-plugin support for PDS Compatibility tests

[ https://issues.apache.org/jira/browse/IGNITE-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699283#comment-16699283 ] Vyacheslav Daradur commented on IGNITE-8379: [~dpavlov], there is no reason to run RunAll

[jira] [Assigned] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.

[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-9023: -- Assignee: Vyacheslav Daradur (was: ruchir choudhry) > LinkageError or

[jira] [Commented] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.

[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698236#comment-16698236 ] Vyacheslav Daradur commented on IGNITE-9023: I reassigned the issue myself because there is

[jira] [Commented] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property

[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697280#comment-16697280 ] Vyacheslav Daradur commented on IGNITE-7441: [~dmekhanikov], thanks! [~NIzhikov], could

[jira] [Commented] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property

[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697170#comment-16697170 ] Vyacheslav Daradur commented on IGNITE-7441: The tests marked as possible blockers fail in

[jira] [Updated] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.

[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-1478: --- Component/s: managed services > Service cannot be used on remote node immediately

[jira] [Updated] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.

[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-1478: --- Labels: iep-17 (was: ) > Service cannot be used on remote node immediately after

[jira] [Updated] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.

[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-1478: --- Fix Version/s: 2.8 > Service cannot be used on remote node immediately after

[jira] [Assigned] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.

[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-1478: -- Assignee: Vyacheslav Daradur > Service cannot be used on remote node

[jira] [Updated] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property

[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-7441: --- Fix Version/s: 2.8 > Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property >

[jira] [Updated] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property

[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-7441: --- Component/s: managed services > Drop IGNITE_SERVICES_COMPATIBILITY_MODE system

[jira] [Commented] (IGNITE-8379) Add maven-surefire-plugin support for PDS Compatibility tests

[ https://issues.apache.org/jira/browse/IGNITE-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693214#comment-16693214 ] Vyacheslav Daradur commented on IGNITE-8379: [~vveider], thank you for help with testing.

[jira] [Commented] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.

[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693081#comment-16693081 ] Vyacheslav Daradur commented on IGNITE-9023: Hi, [~ruchirc], would you mind if I assign the

[jira] [Commented] (IGNITE-8379) Add maven-surefire-plugin support for PDS Compatibility tests

[ https://issues.apache.org/jira/browse/IGNITE-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689849#comment-16689849 ] Vyacheslav Daradur commented on IGNITE-8379: Hi, [~vveider], I added support running tests

[jira] [Issue Comment Deleted] (IGNITE-9607) Service Grid redesign - phase 1

[ https://issues.apache.org/jira/browse/IGNITE-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-9607: --- Comment: was deleted (was: I attached a description of the implemented solution: 

[jira] [Commented] (IGNITE-10116) Document implemented design of Service Grid (redesign phase 1)

[ https://issues.apache.org/jira/browse/IGNITE-10116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678339#comment-16678339 ] Vyacheslav Daradur commented on IGNITE-10116: - I published documentation in wiki:

[jira] [Updated] (IGNITE-10116) Document implemented design of Service Grid (redesign phase 1)

[ https://issues.apache.org/jira/browse/IGNITE-10116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10116: Attachment: (was: Service Grid phase 1 - implementation details.docx) >

[jira] [Issue Comment Deleted] (IGNITE-10116) Document implemented design of Service Grid (redesign phase 1)

[ https://issues.apache.org/jira/browse/IGNITE-10116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10116: Comment: was deleted (was: I attached a prepared document to the issue. Also,

  1   2   3   4   5   6   >