Watcher index closed error

alerting

(piyush) #1

Hi Team,
I installed watcher and post testing we were not using it for a month, due to other priorities. In the mean time i did some index closed exercise. Now i have alert stories to work on but when tried to access watcher it's throwing index closed exception.
May i know which index to open for this? _watcher/_open didn't work and i can't find _watcher index.

Details:

  1. Get _watcher
    {
    "version": {
    "number": "2.3.1",
    "build_hash": "9b8af7034bcde3",
    "build_timestamp": "2016-04-04T12:57:03Z",
    "build_snapshot": false
    },
    "tagline": "You Know, for Alerts & Automation"
    }

  2. Get _watcher/watch/fs_disk_top1
    {
    "error": {
    "root_cause": [
    {
    "type": "cluster_block_exception",
    "reason": "blocked by: [FORBIDDEN/4/index closed];"
    }
    ],
    "type": "cluster_block_exception",
    "reason": "blocked by: [FORBIDDEN/4/index closed];"
    },
    "status": 403
    }

  3. POST_watcher/_open
    {
    "error": {
    "root_cause": [
    {
    "type": "illegal_argument_exception",
    "reason": "No feature for name [_open]"
    }
    ],
    "type": "illegal_argument_exception",
    "reason": "No feature for name [_open]"
    },
    "status": 400
    }

  4. .triggered_watches/_open - worked

  5. POST _watcher/watch/_open
    {
    "error": {
    "root_cause": [
    {
    "type": "cluster_block_exception",
    "reason": "blocked by: [FORBIDDEN/4/index closed];"
    }
    ],
    "type": "cluster_block_exception",
    "reason": "blocked by: [FORBIDDEN/4/index closed];"
    },
    "status": 403
    }

i reconfirm that watcher plugin is installed on all ES nodes.

Thanks & Regards,
Piyush Tekade


(Steve Kearns) #2

The watcher API is at _watcher, but the actual watches index is .watches Try opening or deleting that index. You may need to restart watcher to have it take effect.

Thanks,
Steve


(piyush) #3

It worked, Thanks.


(system) #4