[IGNITE-14421] Get rid of useless waiting on grep

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Sprint: Ducktape Sprint 4, Ducktape Sprint 5, Ducktape Sprint 6, Ducktape Sprint 7
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Anton Vinogradov
• Reporter: Anton Vinogradov
• Created: 26/Mar/21 08:26
• Updated: 07/Apr/21 08:33
• Resolved: 07/Apr/21 08:33

Description

Currently, we wait 5 seconds after each grep miss

[DEBUG - 2021-03-25 18:08:09,577 - remoteaccount - _log - lineno:160]: ducker@ducker11: Running ssh command: jcmd | awk '/org.apache.ignite.internal.ducktest.utils.IgniteAwareApplicationService/ { print $1 }'
[DEBUG - 2021-03-25 18:08:09,736 - remoteaccount - _log - lineno:160]: ducker@ducker11: Running ssh command: tail -c +1 /mnt/service/logs/console.log | grep 'IGNITE_APPLICATION_FINISHED\|IGNITE_APPLICATION_BROKEN'
[DEBUG - 2021-03-25 18:08:09,783 - remoteaccount - _log - lineno:160]: ducker@ducker11: Running ssh command: tail -c +1 /mnt/service/logs/console.log | grep 'IGNITE_APPLICATION_BROKEN'
[DEBUG - 2021-03-25 18:08:09,833 - remoteaccount - _log - lineno:160]: ducker@ducker11: Running ssh command 'tail -c +1 /mnt/service/logs/console.log | grep 'IGNITE_APPLICATION_BROKEN'' exited with status 1 and message: b''
[DEBUG - 2021-03-25 18:08:14,836 - remoteaccount - _log - lineno:160]: ducker@ducker11: Running ssh command: tail -c +1 /mnt/service/logs/console.log | grep 'IGNITE_APPLICATION_FINISHED'

Let's get rid of this backoff_sec=5 by default.
Need to make it 0 if possible, or as small as possible.
Usages with defined backoff_sec should be also checked to minimization availability.

Issue Links

• duplicates: IGNITE-14483 Ignite_app and ignite clean_up