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

ASF GitHub Bot commented on IGNITE-3523:
----------------------------------------

GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-3523  IGFS: Remove "initialize default path modes" feature

    

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

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

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

    https://github.com/apache/ignite/pull/1786.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 #1786
    
----
commit 9d5b6b27a4afcdebee9af56f4b16d06ac1058cc9
Author: tledkov-gridgain <[email protected]>
Date:   2017-04-12T15:17:14Z

    IGNITE-3523 IGFS: Remove "initialize default path modes" feature

commit 5b8ec64dc99c9918cc245f00ae9fe9649ca21224
Author: tledkov-gridgain <[email protected]>
Date:   2017-04-13T07:57:08Z

    Merge branch '_master' into ignite-3523

----


> IGFS: Remove "initialize default path modes" feature.
> -----------------------------------------------------
>
>                 Key: IGNITE-3523
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3523
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Taras Ledkov
>             Fix For: 2.0
>
>
> Currently IGFS can create several paths by default, which will forcefully 
> work in different modes. This will never require in practice, but caused some 
> problems, e.g. performance degradation in our Hadoop FileSystem implementaions
> Let's just remove that feature along with relevant property in 
> {{FileSystemConfiguration}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to