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

2016-10-19 Thread 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 edited comment on IGNITE-3432 at 10/19/16 10:34 AM:
--

Now I see next behaviour (seel configs in attachments):
# 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}
# Also is not runned second server node. Look like check of IGFS caches exists 
only on comparison of configurations on node connect.

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


was (Author: vsisko):
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
>
> 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] [Comment Edited] (IGNITE-3432) Multiple IGFS on the same caches.

2016-10-14 Thread 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 edited comment on IGNITE-3432 at 10/14/16 2:04 PM:


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*.


was (Author: tledkov-gridgain):
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)