[CONJ-392] Aurora cluster endpoint detection fails when time_zone doesn't match system_time_zone Created: 2016-11-23 Updated: 2017-02-08 Resolved: 2017-02-08 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Failover |
| Affects Version/s: | 1.5.5 |
| Fix Version/s: | 1.5.8 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jon Steinich | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Description |
|
The query to find cluster endpoints filters on a last update time. It uses the system_time_zone to create a string of the current time, but the query operates based on the time_zone parameter. In our case, the system_time_zone is UTC and time_zone is US/Central. This results in no endpoints being returned. Could probably fix by using the time_zone server data parameter or using a time function in the query. |
| Comments |
| Comment by Jon Steinich [ 2017-01-13 ] | |||||||||||||||
|
I just tried out 1.5.6 and the issue is not fixed. The query is still not returning any results because of the time check. | |||||||||||||||
| Comment by Diego Dupin [ 2017-01-31 ] | |||||||||||||||
|
to be checked back | |||||||||||||||
| Comment by Diego Dupin [ 2017-01-31 ] | |||||||||||||||
|
Correction is available throught snapshot using :
Could you validate this solve your issue ? | |||||||||||||||
| Comment by Jon Steinich [ 2017-02-01 ] | |||||||||||||||
|
I can confirm this now works for a single instance cluster. If I get some more free time I can add a second instance to our test cluster and check again. |