DELETE Networking Team
[DCOS_OSS-213] Increase error level of "Failed to retrieve information from exhibitor to configure Spartan" Created: 07/Jul/16 Updated: 01/Apr/19 Resolved: 01/Apr/19 |
|
| Status: | Resolved |
| Project: | DC/OS |
| Component/s: | networking |
| Affects Version/s: | 1.7-open |
| Fix Version/s: | None |
| Type: | Task | Priority: | Low |
| Reporter: | John Garcia (Inactive) | Assignee: | Unassigned |
| Resolution: | Invalid | ||
| Labels: | issuetype:improvement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | DELETE Networking Team |
| Description |
|
When Spartan is not able to load configs from ZK, the following error is logged at level INFO: 2016-07-07 14:59:34.785 [info] <0.778.0>@spartan_config_loader_server:get_masters_exhibitor:133 Failed to retrieve information from exhibitor to configure Spartan: {error,{failed_connect,[{to_address,{"example.com",8181}},{inet,[inet],econnrefused}]}}
A community member has asked that we increase the level to ERROR: |
| Comments |
| Comment by Sargun Dhillon (Inactive) [ 07/Jul/16 ] |
|
I mean, but this is an issue? They should fix their environment. |
| Comment by John Garcia (Inactive) [ 07/Jul/16 ] |
|
Yep, that's why "Improvement" issue type instead of any other. We're just looking to present better troubleshooting info. |
| Comment by mnp [ 22/May/17 ] |
|
I'm seeing this too, on a cluster with working exhibitor that's struggling. Spartan is doing a GET http://master.mesos:8181/exhibitor/v1/cluster/status, which is taking 43 seconds. On a happy cluster, it's instant. |
| Comment by Orlando Hohmeier (Inactive) [ 01/Apr/19 ] |
|
I'm going to close this one as we no longer actively support the affected version. Feel free to adjust the affected version and reopen this JIRA if it also affects other versions. |
