[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2019-10-08 Thread Maxim Muzafarov (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16946871#comment-16946871
 ] 

Maxim Muzafarov commented on IGNITE-6826:
-

Moved to 2.9 due to inactivity. Please, feel free to move it back if you will 
be able to complete the ticket by 2.8 code freeze date, December 2, 2019.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2019-01-25 Thread Dmitriy Pavlov (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752473#comment-16752473
 ] 

Dmitriy Pavlov commented on IGNITE-6826:


I feel this change is sensitive and we probably need to build up a consensus on 
the dev.list.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2019-01-15 Thread Ivan Bessonov (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743141#comment-16743141
 ] 

Ivan Bessonov commented on IGNITE-6826:
---

[~SomeFire] changes look good, thank you!

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2019-01-14 Thread Ryabov Dmitrii (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741976#comment-16741976
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


[~avinogradov],

1. Reasons were discussed on devlist 
([1|http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html],
 
[2|http://apache-ignite-developers.2346864.n4.nabble.com/Re-Pushing-IGNITE-6826-forward-td32777.html],
 
[3|http://apache-ignite-developers.2346864.n4.nabble.com/Re-Pushing-forward-IGNITE-6826-Change-default-DiscoverySpi-ipFinder-type-for-examples-td32756.html]).
 Summary:
 * Multicast ipFinder adds some instability when several persons try & debug 
samples or evaluate a new Ignite version at the same local network.
 * Speedup for node start.

2. ExampleNodeStartup use the same configuration as examples, so it works as 
usual.

See the master branch: {{ExampleNodeStartup}} and {{ignite.bat/sh}} are 
*incompatible* because ignite.bat/sh uses default IgniteConfiguration with 
disabled peer class loading, but ExampleNodeStartup uses configuration with 
enabled peer class loading.

3. I assemled release version asa described in DEVNOTES.txt and checked some 
examples manually. They work normally with nodes started by ExampleNodeStartup.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2019-01-10 Thread Anton Vinogradov (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739399#comment-16739399
 ] 

Anton Vinogradov commented on IGNITE-6826:
--

Folks,

First of all, let's define why \{{it is better to change multicast ipFinder to 
static (vm) ipFinder}}.

Second, and most important, once you'll change multicast to vm you not be able 
to check how examples work with 
- nodes, started by ignite.bat/sh
- nodes, started by ExampleNodeStartup

In short, it's not allowed to change multicast to vm where you have to or may 
want to start nodes at different JVM.

Also, please keep im mind that we have to check how fix works inside assembled 
Apache Ignite before changing status to PA.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2019-01-09 Thread Ignite TC Bot (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738339#comment-16738339
 ] 

Ignite TC Bot commented on IGNITE-6826:
---

{panel:title=-- Run :: All: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2750802buildTypeId=IgniteTests24Java8_RunAll]

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-09-14 Thread Ryabov Dmitrii (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615058#comment-16615058
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=1849476]]

{color:#d04437}Platform C++ (Linux){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=1849422]]

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 
7|https://ci.ignite.apache.org/viewLog.html?buildId=1849421]]
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testAtomicLongRetries - 0,0% fails in 
last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetriesEvictionEnabled
 - 0,0% fails in last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetriesSingleValue
 - 0,0% fails in last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testOriginatingNodeFailureForcesOnePhaseCommitDataCleanup
 - 0,0% fails in last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testPutAsync - 0,0% fails in last 100 
master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testPutAsyncStoreEnabled - 0,0% fails 
in last 100 master runs.

{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849381]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite: 
GridCacheFullTextQuerySelfTest.testLocalTextQueryWithKeepBinary - 0,0% fails in 
last 100 master runs.

{color:#d04437}Binary Objects (Simple Mapper Compute Grid){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849380]]
* IgniteBinaryObjectsSimpleNameMapperComputeGridTestSuite: 
GridJobStealingSelfTest.testTwoJobs - 0,0% fails in last 100 master runs.

{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849420]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySpiTest.testDisconnectOnServersLeft_5 - 0,0% fails in last 
100 master runs.

{color:#d04437}Continuous Query 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849387]]
* IgniteCacheQuerySelfTestSuite3: 
CacheContinuousQueryAsyncFilterListenerTest.testNonDeadLockInFilterReplicatedJCacheApi
 - 0,0% fails in last 100 master runs.

{color:#d04437}PDS (Direct IO) 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=1849432]]
* IgnitePdsNativeIoTestSuite: IgniteDbPutGetWithCacheStoreTest.testReadThrough 
- 0,0% fails in last 100 master runs.

{color:#d04437}Basic 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=1849474]]
* IgniteBasicTestSuite: BPlusTreeReuseSelfTest.testMassiveRemove2_false - 0,0% 
fails in last 100 master runs.

{panel}
[TeamCity Run 
All|http://ci.ignite.apache.org/viewLog.html?buildId=1849477buildTypeId=IgniteTests24Java8_RunAll]

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-09-14 Thread Ryabov Dmitrii (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615050#comment-16615050
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=1849476]]

{color:#d04437}Platform C++ (Linux){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=1849422]]

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 
7|https://ci.ignite.apache.org/viewLog.html?buildId=1849421]]
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testAtomicLongRetries - 0,0% fails in 
last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetriesEvictionEnabled
 - 0,0% fails in last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetriesSingleValue
 - 0,0% fails in last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testOriginatingNodeFailureForcesOnePhaseCommitDataCleanup
 - 0,0% fails in last 100 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testPutAsync - 0,0% fails in last 100 
master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteCachePutRetryTransactionalSelfTest.testPutAsyncStoreEnabled - 0,0% fails 
in last 100 master runs.

{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849381]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite: 
GridCacheFullTextQuerySelfTest.testLocalTextQueryWithKeepBinary - 0,0% fails in 
last 100 master runs.

{color:#d04437}Binary Objects (Simple Mapper Compute Grid){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849380]]
* IgniteBinaryObjectsSimpleNameMapperComputeGridTestSuite: 
GridJobStealingSelfTest.testTwoJobs - 0,0% fails in last 100 master runs.

{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849420]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySpiTest.testDisconnectOnServersLeft_5 - 0,0% fails in last 
100 master runs.

{color:#d04437}Continuous Query 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=1849387]]
* IgniteCacheQuerySelfTestSuite3: 
CacheContinuousQueryAsyncFilterListenerTest.testNonDeadLockInFilterReplicatedJCacheApi
 - 0,0% fails in last 100 master runs.

{color:#d04437}PDS (Direct IO) 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=1849432]]
* IgnitePdsNativeIoTestSuite: IgniteDbPutGetWithCacheStoreTest.testReadThrough 
- 0,0% fails in last 100 master runs.

{color:#d04437}Basic 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=1849474]]
* IgniteBasicTestSuite: BPlusTreeReuseSelfTest.testMassiveRemove2_false - 0,0% 
fails in last 100 master runs.

{panel}
[TeamCity Run 
All|http://ci.ignite.apache.org/viewLog.html?buildId=1849477buildTypeId=IgniteTests24Java8_RunAll]

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-04-23 Thread Ryabov Dmitrii (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448294#comment-16448294
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


[~ptupitsyn], can you explain, how do you run tests with differently configured 
nodes, started by {{ignite.bat/sh}}?

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.6
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-04-06 Thread Anton Kurbanov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428231#comment-16428231
 ] 

Anton Kurbanov commented on IGNITE-6826:


[~SomeFire], exactly what what already described in comment section. Launching 
examples using both .exe and from VS with properly configured nodes using 
Apache.Ignite.exe. Nodes started by Ignite.bat/sh are using different 
configuration sourced from config/default-config.xml. As you already mentioned 
there are some exceptions being thrown in this case due to configuration 
mismatch.

Wondering if this should work with default configuration.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-04-05 Thread Ryabov Dmitrii (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427704#comment-16427704
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


[~antkr], I did the same, but Pavel said that .NET tests don't work with nodes, 
started by {{Ignite.bat/sh}}. I don't know what he meant, because I have same 
fail on 2.4.0 binary release with nodes started by {{Ignite.bat/sh}} and 
{{Apache.Ignite.exe}}, which means this fail exist not only in my branch, but 
in the master too. Or I do something wrong (what can be more simple than launch 
.exe file and build example?).

Anton, what do you mean by "examples are working fine"? How you ran them?

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-04-05 Thread Anton Kurbanov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426694#comment-16426694
 ] 

Anton Kurbanov commented on IGNITE-6826:


[~SomeFire], can you clarify what needs to be done in order to resolve this 
issue? I've changed ipFinder from multicast to static/vm and examples are 
working fine.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-01-17 Thread Ryabov Dmitrii (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328785#comment-16328785
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


[~ptupitsyn], I tried to use ignite.bat with examples in master. Only 
NearCacheExample, LifecycleExample and ThinClientPutGetExample (the last 
example doesn't connect to ignite.bat nodes) work for me. How do you use 
ignite.bat/sh?
As I see, it shouldn't work because examples config differs from default at 
least by {{peerClassLoadingEnabled}} parameter, which leads to the exception 
"Remote node has peer class loading enabled flag different from local".

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie
> Fix For: 2.4
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-01-12 Thread Ryabov Dmitrii (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323867#comment-16323867
 ] 

Ryabov Dmitrii commented on IGNITE-6826:


I'll check it.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>  Labels: newbie
> Fix For: 2.4
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-01-12 Thread Pavel Tupitsyn (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323856#comment-16323856
 ] 

Pavel Tupitsyn commented on IGNITE-6826:


Before that change you could run many examples with ignite.bat/sh with default 
config, and now you can't (at least for .NET).
I don't think this is a good change.

> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>  Labels: newbie
> Fix For: 2.4
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples

2018-01-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323718#comment-16323718
 ] 

ASF GitHub Bot commented on IGNITE-6826:


GitHub user SomeFire opened a pull request:

https://github.com/apache/ignite/pull/3362

IGNITE-6826



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/SomeFire/ignite ignite-6826

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3362.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3362


commit cd268cf53b769d26e3ae8a243013cb028569a846
Author: Dmitrii Ryabov 
Date:   2017-12-27T10:25:39Z

IGNITE-6826: ipFinder changed in java examples.

commit 78783a17fb625b854a7a3e3fa86bea918b2b2637
Author: Dmitrii Ryabov 
Date:   2018-01-11T14:11:11Z

IGNITE-6826: ipFinder changed in dotnet examples.

commit 69f85efa93195de88e691368b333f3633504ce50
Author: Dmitrii Ryabov 
Date:   2018-01-11T14:16:53Z

IGNITE-6826: ipFinder changed in cpp examples.




> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>  Labels: newbie
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)