[IGNITE-18403] ignite-cdc.sh fails to start with non-default work directory location

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.15
• Labels: IEP-59 ise
• Release Note: Fixed ignite-cdc.sh start failure with non-defailt work directory
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Nikolay Izhikov
• Reporter: Sergey Korotkov
• Created: 14/Dec/22 07:29
• Updated: 24/Apr/23 15:00
• Resolved: 16/Dec/22 10:34

Description

ignite-cdc.sh fails to start if the non-default work directory is configured.

As shown on the screenshot attached, it correctly detects the work directory location at the begining of work, but afterwards tries to access / create the work directory in the default location.

If directory can not be created (say because of permissions lack or read-only filesystem) ignite-cdc.sh just doesn't start.

 

Issue Links

• links to: GitHub Pull Request #10445