[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3432:


Github user asfgit closed the pull request at:

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


> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
> Attachments: test2IGFS-client.xml, test2IGFS-server.xml
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes. 
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same 
> caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3432:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3432  Multiple IGFS on the same caches.



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

$ git pull https://github.com/gridgain/apache-ignite ignite-3432

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

https://github.com/apache/ignite/pull/1201.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 #1201


commit a4c63ae113931615e940ada2411ebce32dba5db8
Author: iveselovskiy 
Date:   2016-09-30T07:45:13Z

IGNITE-3998: IGFS: Enabled 
IgfsAbstractSelfTest.testCreateConsistencyMultithreaded. This closes #1129.

commit a12298c0baf19407f3110ba3c4f0aab88b67946d
Author: Igor Sapego 
Date:   2016-09-30T08:00:51Z

IGNITE-3868: ODBC: Fixed connection string parsing. This closes #1051.

commit 5e7ef8644ad824b87d4797e59133eb783ff8b098
Author: vozerov-gridgain 
Date:   2016-10-03T07:37:25Z

Merge branch 'ignite-1.6.9' into ignite-1.6.10

commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f
Author: vozerov-gridgain 
Date:   2016-10-03T07:40:04Z

IGNITE-2881: Fixed SPI queries.

commit 0b66d2d7b695cf370a4b8a717844ad67742c6090
Author: sboikov 
Date:   2016-10-03T09:04:03Z

ignite-3601 Do not check version on commit for read-only serializable 
transactions.

commit 9f211e413332931f0fb1190744ddd7c7f38fd213
Author: tledkov-gridgain 
Date:   2016-10-03T09:26:12Z

IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This 
closes #1003.

commit fa698d6fcfde0006423ef009337dbef58ac62515
Author: vozerov-gridgain 
Date:   2016-10-03T10:33:12Z

Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by 
multicast IP finder.

commit bba019fd5076412ca43c10a32fd300b6031ccd0b
Author: vozerov-gridgain 
Date:   2016-10-03T14:25:20Z

IGNITE-3980: Processed failing tests in query suites. This closes #1137.

commit a92f20b5cc75e6b80b2731da0192723526b0c1dc
Author: vozerov-gridgain 
Date:   2016-10-04T11:10:26Z

IGNITE-3597: Removed static work directory.

commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1
Author: vozerov-gridgain 
Date:   2016-10-06T07:14:59Z

IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130.

commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497
Author: tledkov-gridgain 
Date:   2016-10-06T07:22:50Z

IGNITE-3163 IGFS: Added working directory support to 
IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This 
closes #1132.

commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701
Author: vozerov-gridgain 
Date:   2016-10-06T09:03:48Z

IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This 
closes #903. This closes #1145.

commit 952be8b995050b34379006dd6e739da3fe3b49e3
Author: Dmitriy Govorukhin 
Date:   2016-10-07T12:00:09Z

Squashed commit of the following:

commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1
Author: sboikov 
Date:   Fri Oct 7 13:08:38 2016 +0300

minor

commit 7fe88a1cb21f794ee55a176ab36d895cbf916528
Author: Dmitriy Govorukhin 
Date:   Thu Oct 6 11:11:24 2016 +0300

ignite-update-notifier fix after review

(cherry picked from commit a10d2ff)

commit f2de749f958a3b18dc479f8a5517d7bf9362b933
Author: Dmitriy Govorukhin 
Date:   Tue Oct 4 12:12:08 2016 +0300

ignite-2079-2 optimize import and change url path

(cherry picked from commit 830a3cf)

commit 0d1be85ad55b0aa91224690d6c112ae92e8bc0a9
Author: Dmitriy Govorukhin 
Date:   Thu Sep 29 19:54:54 2016 +0300

update-notifier remove parse xml, now parse like properties

(cherry picked from commit 9ecaa29)

commit e43bca6fb4528a7fc0dcb804a74fca1c59d7468b
Author: Dmitriy Govorukhin 
Date:   Tue Sep 27 17:07:21 2016 +0300

remove dom parser

(cherry picked from commit d1653b2)

commit b9c776a8423471706ecb1dc6176b38f23e799077
Author: Anton Vinogradov 
Date:   2016-10-10T08:52:57Z

IGNITE-3235 Failed to initialize primitive boolean cache property of 
superclass

commit f9a0676fad7fd6c23e3c91c10d7e0412ccb27c06
Author: 

[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-3432:
--

[Tests 
results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1201%2Fhead]

> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
> Attachments: test2IGFS-client.xml, test2IGFS-server.xml
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes. 
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same 
> caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-3432:
---

Now I see next behaviour:
# Server node is started successfully. It contain two IGFS instances where 
second is unavailable.
# Client node is failed on start with exception: 
{code}
class org.apache.ignite.IgniteCheckedException: Meta cache names should be 
different for different IGFS instances configuration (fix configuration or set 
-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property) 
[metaCacheName=igfs-meta, locNodeId=53722f5a-8505-4bd9-91af-7b4a7324eb50, 
rmtNodeId=6b9e1371-84f1-4b2c-856b-33be541bf039, locIgfsName=other, 
rmtIgfsName=igfs]
at 
org.apache.ignite.internal.processors.igfs.IgfsProcessor.checkIgfsOnRemoteNode(IgfsProcessor.java:400)
at 
org.apache.ignite.internal.processors.igfs.IgfsProcessor.onKernalStart(IgfsProcessor.java:198)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:940)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1761)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1595)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1041)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:963)
{code}

I think that *p.1* is incorrect. That create grid that is not available for 
client nodes.

> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes. 
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same 
> caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-3432:
--

The scenario isn't reproduced. 
Please clarify your point about the scenario. Where is the problem at the {p.2} 
or at the {p.3}?

- The problem had already fixed if one at the {p.2}. This is invalid 
configuration. The {{IgniteCheckedException("Data/Meta cache names should be 
different for different IGFS instances configuration")}} will be thrown.
- The issue is invalid if the problem at the {p.3}.

> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes. 
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same 
> caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)