MaxScale.log
mariadb-columnstore-maxscale-cdc-adapters-1.1.3-1-x86_64-centos7.rpm
[MCOL-1430] CDC Connector v2.2.5-1 unable to connect to MaxScale Created: 2018-05-19 Updated: 2023-10-26 Due: 2018-05-21 Resolved: 2018-06-07 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ?, MDB Plugin |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Faisal Saeed (Inactive) | Assignee: | Elena Kotsinova (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
REHL 7.4 |
||
| Attachments: |
MaxScale.log
mariadb-columnstore-maxscale-cdc-adapters-1.1.3-1-x86_64-centos7.rpm
|
| Sprint: | 2018-11, 2018-12 |
| Description |
|
After a complete setup of TX to MaxScale 2.2.x to Columnstore 1.1.x when we executed the following mxs_adapter -c /etc/Columnstore.xml -u cdcuser -p cdcpassword -h maxscale -P 4001 cdc_test test we got the output as "MaxScale connection could not be created: Request timed out" CDCUSER was already created and when we try to login with an invalid user, we got an authentication error which is expected. This confirms MaxScale is alive. Attached are the logs from the MaxScale for your reference. We used the following RPMs for our setup CDC setup with 2 UMs and 3 PMs:
|
| Comments |
| Comment by markus makela [ 2018-05-20 ] |
|
I've created a fix for this problem and uploaded a custom build to verify that it works. The package was build from commit 5ed54d5f839442c17ad0b7aa5c9ea9ef3728ee17. Please ignore the version number mismatch, it was not updated on the branch with the latest code. |
| Comment by markus makela [ 2018-05-21 ] |
|
The code is already merged into develop-1.1, I think review can be marked as done. |
| Comment by Elena Kotsinova (Inactive) [ 2018-06-07 ] |
|
verified with: 2. |