You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by "1ssqq1lxr (via GitHub)" <gi...@apache.org> on 2024/10/18 06:03:34 UTC

[I] I set the `workdir`, but the launch directory still generated the `ignite` directory. [ignite]

1ssqq1lxr opened a new issue, #11605:
URL: https://github.com/apache/ignite/issues/11605

   I set the `workdir`, but the launch directory still generated the `ignite` directory.
   `
   IgniteConfiguration igniteConfiguration = new IgniteConfiguration(); igniteConfiguration.setAsyncCallbackPoolSize(Runtime.getRuntime().availableProcessors() / 2); igniteConfiguration.setWorkDirectory(System.getProperty("user.home") + "/fluxmq");
   
   `
   ![image](https://github.com/user-attachments/assets/ce95ffd0-1e86-4604-a14d-3ff6a741bac9)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] I set the `workdir`, but the launch directory still generated the `ignite` directory. [ignite]

Posted by "1ssqq1lxr (via GitHub)" <gi...@apache.org>.
1ssqq1lxr commented on issue #11605:
URL: https://github.com/apache/ignite/issues/11605#issuecomment-2421503711

   Did the set workdir not take effect? What does this file mean?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] I set the `workdir`, but the launch directory still generated the `ignite` directory. [ignite]

Posted by "1ssqq1lxr (via GitHub)" <gi...@apache.org>.
1ssqq1lxr commented on issue #11605:
URL: https://github.com/apache/ignite/issues/11605#issuecomment-2428625044

   ![image](https://github.com/user-attachments/assets/9bcc45b4-bc4c-446e-868e-b3adcc460956)
   The diagnostic directory I specified is empty, but there are data files in the ignote directory of the startup directory
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] I set the `workdir`, but the launch directory still generated the `ignite` directory. [ignite]

Posted by "ptupitsyn (via GitHub)" <gi...@apache.org>.
ptupitsyn commented on issue #11605:
URL: https://github.com/apache/ignite/issues/11605#issuecomment-2428500358

   It works as expected for me with Ignite 2.16:
   
   ```java
   package org.example;
   
   import org.apache.ignite.Ignition;
   import org.apache.ignite.configuration.IgniteConfiguration;
   
   public class Main {
       public static void main(String[] args) {
           IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
           igniteConfiguration.setWorkDirectory(System.getProperty("user.home") + "/w/tests/ignite-work");
   
           Ignition.start(igniteConfiguration);
       }
   }
   ```
   
   ```bash
    pavel > work > w > tests > ignite-work $ ls -la --recursive
   .:
   total 16
   drwxrwxr-x  4 pavel pavel 4096 Oct 22 10:39 .
   drwxrwxr-x 73 pavel pavel 4096 Oct 22 10:39 ..
   drwxrwxr-x  4 pavel pavel 4096 Oct 22 10:39 db
   drwxrwxr-x  2 pavel pavel 4096 Oct 22 10:39 diagnostic
   
   ./db:
   total 16
   drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 .
   drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 0_0_0_0_0_0_0_1_lo_127_0_0_1_172_17_0_1_192_168_13_151_47500
   drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 marshaller
   
   ./db/0_0_0_0_0_0_0_1_lo_127_0_0_1_172_17_0_1_192_168_13_151_47500:
   total 8
   drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 .
   drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   
   ./db/marshaller:
   total 8
   drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 .
   drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   
   ./diagnostic:
   total 8
   drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 .
   drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] I set the `workdir`, but the launch directory still generated the `ignite` directory. [ignite]

Posted by "1ssqq1lxr (via GitHub)" <gi...@apache.org>.
1ssqq1lxr commented on issue #11605:
URL: https://github.com/apache/ignite/issues/11605#issuecomment-2428615246

   > It works as expected for me with Ignite 2.16:
   > 
   > ```java
   > package org.example;
   > 
   > import org.apache.ignite.Ignition;
   > import org.apache.ignite.configuration.IgniteConfiguration;
   > 
   > public class Main {
   >     public static void main(String[] args) {
   >         IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
   >         igniteConfiguration.setWorkDirectory(System.getProperty("user.home") + "/w/tests/ignite-work");
   > 
   >         Ignition.start(igniteConfiguration);
   >     }
   > }
   > ```
   > 
   > ```shell
   >  pavel > work > w > tests > ignite-work $ ls -la --recursive
   > .:
   > total 16
   > drwxrwxr-x  4 pavel pavel 4096 Oct 22 10:39 .
   > drwxrwxr-x 73 pavel pavel 4096 Oct 22 10:39 ..
   > drwxrwxr-x  4 pavel pavel 4096 Oct 22 10:39 db
   > drwxrwxr-x  2 pavel pavel 4096 Oct 22 10:39 diagnostic
   > 
   > ./db:
   > total 16
   > drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 .
   > drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   > drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 0_0_0_0_0_0_0_1_lo_127_0_0_1_172_17_0_1_192_168_13_151_47500
   > drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 marshaller
   > 
   > ./db/0_0_0_0_0_0_0_1_lo_127_0_0_1_172_17_0_1_192_168_13_151_47500:
   > total 8
   > drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 .
   > drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   > 
   > ./db/marshaller:
   > total 8
   > drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 .
   > drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   > 
   > ./diagnostic:
   > total 8
   > drwxrwxr-x 2 pavel pavel 4096 Oct 22 10:39 .
   > drwxrwxr-x 4 pavel pavel 4096 Oct 22 10:39 ..
   > ```
   
   I am also using version 2.16, JDK 21, and a cluster deployment method with a total of 3 nodes. The data mainly consists of some external data sources and some in memory data sources. No problem found
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org