[IGNITE-12103] Change the default ignite work directory once again to avoid writing to ~/work

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.7.6
• Component/s: general
• Release Note: Ignite work directory is now set to ${user.dir}/ignite/work by default, with README.txt in it, when IGNITE_HOME not set.
• Flags: Important
• Ignite Flags: Docs Required
• Assignee: Ilya Kasnacheev
• Reporter: Ilya Kasnacheev
• Created: 26/Aug/19 09:11
• Updated: 24/Sep/20 12:55
• Resolved: 02/Sep/19 10:51

Description

While testing 2.7.6-RC1 it came up that we no longer write data to /tmp/ignite/work, which is good, but now we would instead write to /home/username/work, which is bad. ~/work is a generic directory not linked to Ignite in any obvious way, and users will be puzzled by its appearance with possibilities of data loss or, even worse, their own documents loss if they happen to have something in Work dir and it gets clobbered/removed by accident.

I suggest changing this default once more, to use either /home/username/ignite/

{work,logs,etc} or ./ignite/{work,logs,etc}

by leveraging user.dir property pointing to current working dir.

Please note that user.dir has its own problems since it is supposed to not be changeable after JVM is up, but some code still tries to change it.

Issue Links

• causes: IGNITE-13384 Auto-generated README.txt contains invalid workingDirectory property name
• causes: IGNITE-12260 Fallback to {user.home}/ignite/work if {user.dir} is not writable
• is caused by: IGNITE-12057 Persistence files are stored to temp dir
• is related to: IGNITE-12134 Document default Ignite work dir location
• links to: GitHub Pull Request #6816
• links to: Ignite Developers maillist discussion