Github user kishoreg commented on the pull request:
https://github.com/apache/helix/pull/32#issuecomment-122674486
So ClusterStateVerifier wont work for such resources? It might be better to
enhance the verifier to look at current state if externalview creation is
disabled.
Also, there is monitoring mbean which constantly compares idealstate and
externalview and emits the differences between the two. With this change, we
might see lot of false alerts.
How about real error, what if the task fails how will SRE's know about the
ERROR?
Overall code looks good but I am worried that this is deviating quite a bit
from Helix concepts.
I understand that this is a short term hack, do you have any ideas on long
term fix?
---
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.
---
