imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-456682541
@kangkaisen I think returning 404 is OK if it can stop Chrome sending request
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-456638189
> The reason for curl failed is `HttpServerHandler.channelReadComplete`
close the connect early. we shouldn't close ctx even if the action is n
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-455999649
> @imay I added header "Transfer-Encoding: chunked" to java http client,
which still work well. After I debugged, I think either the Netty
Htt
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-455980791
@kangkaisen
I found that curl's request has HTTP header "Transfer-Encoding: chunked".
Maybe this encoding type caused the different res
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-455955335
> Yes. I used `curl -v` and added ` --location-trusted` option.
>
> ```
> [#2#kangkaisen@kks ~ 11:00:22]$seq 1 10 | awk '{OFS="\t"}{pr
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-455945319
@kangkaisen
Could you provide more details when executing `LoadAction` with curl.
You can use `curl -v` to print more information.
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-455438577
> @morningman
>
> > There is a serious problem that if the metadata has error, the Frontend
instance may not even able to start, so that
imay commented on issue #549: Add a colocate join meta repair tool
URL: https://github.com/apache/incubator-doris/issues/549#issuecomment-455053722
I think HTTP or SQL is OK. CommandLine need admin to login in the host where
service locates on, so it's not convenient.
For HTTP and SQ