[FALCON-1681] Improve logging for idempotent behaviour while scheduling entities.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9
• Fix Version/s: 0.9
• Component/s: scheduler
• Assignee: Pallavi Rao
• Reporter: Pragya Mittal
• Created: 21/Dec/15 11:33
• Updated: 23/Dec/15 04:46
• Resolved: 23/Dec/15 04:45

Description

Currently if an entity is scheduled once, user can schedule that entity any number of times. Since scheduler is not changing any functionality for end users, it should show the same behaviour. Although when a scheduled entity is scheduled again it fails with the following error :

dataqa@lda01:/mnt/users/pragya/scheduler$ fep -schedule -name Native-2 -properties falcon.scheduler:oozie
ERROR: Bad Request;ua1/Entity schedule failed for process: Native-2