Re: Ignite Map-Reduce Deadlocking, Running in SYS pool
I respectfully suggest you update your public documentation ASAP, as people (like my team) are developing new software now, using IGFS, expecting that it will continue to be supported. Please don't wait until you release 2.8. On Wed, Sep 11, 2019 at 11:07 AM Ilya Kasnacheev wrote: > Hello! > > https://issues.apache.org/jira/browse/IGNITE-11942 > > Vote already succeeded, there shouldn't be IGFS in 2.8. > > Regards, > -- > Ilya Kasnacheev > > > ср, 11 сент. 2019 г. в 16:52, Chris Software : > >> Ilya, >> >> When will an official announcement and support-drop schedule be made >> about dropping IGFS? >> >> Thank you, >> >> Chris >> >> On Tue, Aug 27, 2019 at 1:47 PM Chris Software >> wrote: >> >>> I see. Thank you. >>> >>> On Tue, Aug 27, 2019 at 12:30 PM Ilya Kasnacheev < >>> ilya.kasnach...@gmail.com> wrote: >>> >>>> Hello! >>>> >>>> This looks like a mistake. However, we're going to drop IGFS so the fix >>>> is unlikely to be expected. >>>> >>>> The recommended practical approach is to increase number of threads in >>>> system thread pool to large value. >>>> >>>> Regards, >>>> -- >>>> Ilya Kasnacheev >>>> >>>> >>>> вт, 27 авг. 2019 г. в 00:34, Chris Software >>> >: >>>> >>>>> Hello, >>>>> >>>>> I am working on a project and we have run into two related problems >>>>> while doing Map_Reduce on Ignite Filesystem Cache. >>>>> >>>>> We were originally on Ignite 2.6 but upgraded to 2.7.5 in an >>>>> unsuccessful bid to resolve the problem. >>>>> >>>>> We have a deadlock in our map-reduce process and have reproduced it at >>>>> https://github.com/csteppp/ignite-deadlock-issue in >>>>> https://github.com/csteppp/ignite-deadlock-issue/blob/master/src/test/java/testignite/MapReduceIgniteTest.java. >>>>> >>>>> >>>>> Basically, if you run the test (mvn test) it will deadlock and hang. >>>>> We have two IgfsTasks created and have set the SYS threadpool to size 2 >>>>> for >>>>> demonstration purposes. Each IgfsTask sleeps and then writes to a file. >>>>> This causes a deadlock because: >>>>> 1. The IgfsTask is run in the SYS pool. >>>>> 2. The Igfs write action uses a separate thread in the SYS pool >>>>> 3. Then if there are no empty threads available, the whole system >>>>> hangs. >>>>> >>>>> First, shouldn't executeAsync execute the task in the PUBLIC pool? >>>>> Using the SYS pool seems unnecessarily risky, as we found it actually >>>>> *locks >>>>> up an entire cluster of many ignite nodes *when it deadlocks. How do >>>>> I get it to use the PUBLIC pool? Also, since it is using the SYS pool, it >>>>> actually seems to execute this on the client. This is not obvious in this >>>>> test, but in my real cluster of 30 nodes, the client seems to be doing >>>>> this >>>>> work, which is a problem. >>>>> >>>>> Second, is it bad form to open a file within a map-reduce? Even using >>>>> the public pool will not solve the inherent deadlock here--that one thread >>>>> is depending on another thread in the same thread pool. That's an >>>>> inherent >>>>> risk. In our real process we open the file because we are performing file >>>>> transformations in the IgfsTask, and then writing the results out to temp >>>>> files in the cluster. In the end, we collate all the temp files. Is >>>>> there >>>>> a better approach, or a safe way to open a file and write to it from >>>>> within >>>>> a reduce? >>>>> >>>>> Thank you for your time! >>>>> >>>>> Chris >>>>> >>>>> >>>>>
Re: Ignite Map-Reduce Deadlocking, Running in SYS pool
Ilya, When will an official announcement and support-drop schedule be made about dropping IGFS? Thank you, Chris On Tue, Aug 27, 2019 at 1:47 PM Chris Software wrote: > I see. Thank you. > > On Tue, Aug 27, 2019 at 12:30 PM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> wrote: > >> Hello! >> >> This looks like a mistake. However, we're going to drop IGFS so the fix >> is unlikely to be expected. >> >> The recommended practical approach is to increase number of threads in >> system thread pool to large value. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> вт, 27 авг. 2019 г. в 00:34, Chris Software : >> >>> Hello, >>> >>> I am working on a project and we have run into two related problems >>> while doing Map_Reduce on Ignite Filesystem Cache. >>> >>> We were originally on Ignite 2.6 but upgraded to 2.7.5 in an >>> unsuccessful bid to resolve the problem. >>> >>> We have a deadlock in our map-reduce process and have reproduced it at >>> https://github.com/csteppp/ignite-deadlock-issue in >>> https://github.com/csteppp/ignite-deadlock-issue/blob/master/src/test/java/testignite/MapReduceIgniteTest.java. >>> >>> >>> Basically, if you run the test (mvn test) it will deadlock and hang. We >>> have two IgfsTasks created and have set the SYS threadpool to size 2 for >>> demonstration purposes. Each IgfsTask sleeps and then writes to a file. >>> This causes a deadlock because: >>> 1. The IgfsTask is run in the SYS pool. >>> 2. The Igfs write action uses a separate thread in the SYS pool >>> 3. Then if there are no empty threads available, the whole system >>> hangs. >>> >>> First, shouldn't executeAsync execute the task in the PUBLIC pool? >>> Using the SYS pool seems unnecessarily risky, as we found it actually *locks >>> up an entire cluster of many ignite nodes *when it deadlocks. How do I >>> get it to use the PUBLIC pool? Also, since it is using the SYS pool, it >>> actually seems to execute this on the client. This is not obvious in this >>> test, but in my real cluster of 30 nodes, the client seems to be doing this >>> work, which is a problem. >>> >>> Second, is it bad form to open a file within a map-reduce? Even using >>> the public pool will not solve the inherent deadlock here--that one thread >>> is depending on another thread in the same thread pool. That's an inherent >>> risk. In our real process we open the file because we are performing file >>> transformations in the IgfsTask, and then writing the results out to temp >>> files in the cluster. In the end, we collate all the temp files. Is there >>> a better approach, or a safe way to open a file and write to it from within >>> a reduce? >>> >>> Thank you for your time! >>> >>> Chris >>> >>> >>>
Re: Ignite Map-Reduce Deadlocking, Running in SYS pool
I see. Thank you. On Tue, Aug 27, 2019 at 12:30 PM Ilya Kasnacheev wrote: > Hello! > > This looks like a mistake. However, we're going to drop IGFS so the fix is > unlikely to be expected. > > The recommended practical approach is to increase number of threads in > system thread pool to large value. > > Regards, > -- > Ilya Kasnacheev > > > вт, 27 авг. 2019 г. в 00:34, Chris Software : > >> Hello, >> >> I am working on a project and we have run into two related problems while >> doing Map_Reduce on Ignite Filesystem Cache. >> >> We were originally on Ignite 2.6 but upgraded to 2.7.5 in an unsuccessful >> bid to resolve the problem. >> >> We have a deadlock in our map-reduce process and have reproduced it at >> https://github.com/csteppp/ignite-deadlock-issue in >> https://github.com/csteppp/ignite-deadlock-issue/blob/master/src/test/java/testignite/MapReduceIgniteTest.java. >> >> >> Basically, if you run the test (mvn test) it will deadlock and hang. We >> have two IgfsTasks created and have set the SYS threadpool to size 2 for >> demonstration purposes. Each IgfsTask sleeps and then writes to a file. >> This causes a deadlock because: >> 1. The IgfsTask is run in the SYS pool. >> 2. The Igfs write action uses a separate thread in the SYS pool >> 3. Then if there are no empty threads available, the whole system >> hangs. >> >> First, shouldn't executeAsync execute the task in the PUBLIC pool? Using >> the SYS pool seems unnecessarily risky, as we found it actually *locks >> up an entire cluster of many ignite nodes *when it deadlocks. How do I >> get it to use the PUBLIC pool? Also, since it is using the SYS pool, it >> actually seems to execute this on the client. This is not obvious in this >> test, but in my real cluster of 30 nodes, the client seems to be doing this >> work, which is a problem. >> >> Second, is it bad form to open a file within a map-reduce? Even using >> the public pool will not solve the inherent deadlock here--that one thread >> is depending on another thread in the same thread pool. That's an inherent >> risk. In our real process we open the file because we are performing file >> transformations in the IgfsTask, and then writing the results out to temp >> files in the cluster. In the end, we collate all the temp files. Is there >> a better approach, or a safe way to open a file and write to it from within >> a reduce? >> >> Thank you for your time! >> >> Chris >> >> >>
Ignite Map-Reduce Deadlocking, Running in SYS pool
Hello, I am working on a project and we have run into two related problems while doing Map_Reduce on Ignite Filesystem Cache. We were originally on Ignite 2.6 but upgraded to 2.7.5 in an unsuccessful bid to resolve the problem. We have a deadlock in our map-reduce process and have reproduced it at https://github.com/csteppp/ignite-deadlock-issue in https://github.com/csteppp/ignite-deadlock-issue/blob/master/src/test/java/testignite/MapReduceIgniteTest.java. Basically, if you run the test (mvn test) it will deadlock and hang. We have two IgfsTasks created and have set the SYS threadpool to size 2 for demonstration purposes. Each IgfsTask sleeps and then writes to a file. This causes a deadlock because: 1. The IgfsTask is run in the SYS pool. 2. The Igfs write action uses a separate thread in the SYS pool 3. Then if there are no empty threads available, the whole system hangs. First, shouldn't executeAsync execute the task in the PUBLIC pool? Using the SYS pool seems unnecessarily risky, as we found it actually *locks up an entire cluster of many ignite nodes *when it deadlocks. How do I get it to use the PUBLIC pool? Also, since it is using the SYS pool, it actually seems to execute this on the client. This is not obvious in this test, but in my real cluster of 30 nodes, the client seems to be doing this work, which is a problem. Second, is it bad form to open a file within a map-reduce? Even using the public pool will not solve the inherent deadlock here--that one thread is depending on another thread in the same thread pool. That's an inherent risk. In our real process we open the file because we are performing file transformations in the IgfsTask, and then writing the results out to temp files in the cluster. In the end, we collate all the temp files. Is there a better approach, or a safe way to open a file and write to it from within a reduce? Thank you for your time! Chris
Re: IgniteFileSystem.create(...) Question--File Properties?
Hello! We are using it as a standalone, in order to create a distributed file system for a (hopefully) fast cache of a few hours of data. We are not using it in front of Hadoop, although there is some discussion of eventually backing it with Cassandra, should we decide to keep more than a few hours of data in the future. Chris On Tue, May 14, 2019 at 10:35 PM Denis Magda wrote: > Hello, > > Are you using IGFS as a standalone file system or as a way to accelerate > Hadoop? If for the latter then I would suggest considering an alternate > solution that is proved to be efficient for production deployment and > Hadoop offloading: > > http://apache-ignite-users.70518.x6.nabble.com/SW-recommendation-Ignite-Native-Persistence-for-traditional-relational-data-warehouse-td28135.html > > - > Denis > > > On Tue, May 14, 2019 at 12:26 PM Chris Software > wrote: > >> Hello, >> >> I am wondering what sort of File Properties can be set in ignite using >> the IgniteFileSystem.create(IgfsPath path, int bufSize, boolean overwrite, >> int replication, long, blockSize, Map props) method. >> >> I am using the default storage. It's not obvious to me in the code what >> choices I have for this properties file. I don't see it documented in the >> javadoc. >> >> Thank you. >> >
IgniteFileSystem.create(...) Question--File Properties?
Hello, I am wondering what sort of File Properties can be set in ignite using the IgniteFileSystem.create(IgfsPath path, int bufSize, boolean overwrite, int replication, long, blockSize, Map props) method. I am using the default storage. It's not obvious to me in the code what choices I have for this properties file. I don't see it documented in the javadoc. Thank you.
Re: Future of IGFS.
Hello! Would this question be better suited to the contributor's distro? For one thing, I have a couple of patches I would like to submit if IGFS has a future. Thank you. On Sun, May 12, 2019 at 2:54 PM Chris Software wrote: > Hello, > > I have heard a rumor that IGFS will be dropped in the future. Can anyone > confirm or deny, and tell me why or why not? If there is a discussion > thread somewhere I would love a link. > > Source: alamar on StackOverflow > > Thank you. >
Future of IGFS.
Hello, I have heard a rumor that IGFS will be dropped in the future. Can anyone confirm or deny, and tell me why or why not? If there is a discussion thread somewhere I would love a link. Source: alamar on StackOverflow Thank you.
