Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/77#issuecomment-50111555
@blrunner, thanks for the great contribution!
I tested the latest patch on a real cluster, and it seems that there are a
couple of problems.
Here are descriptions.
* When HA mode is disabled, the web UI doesn't work well.
* There are some problems when derby is used as catalog store.
* I couldn't execute the backup master due to the duplicated pid problem.
* The duplicated catalog uri also incurred a problem.
* When I used a different catalog uri as a workaround for the above
problem, there were differences between the catalog of active master and that
of backup master, obviously.
* I manually added tables to the backup master catalog to test the failover
during the query execution. When the active master is killed, the backup master
becomes to active and every worker is registered to the changed active master
successfully, but the information of executed query is disappeared.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
