Hi, manhua
Now no_sort reuse the loading flow of local_sort. It is not a good
solution and led to the situation which you have mentioned. In my opinion,
we need to adjust the loading flow of no_sort, maybe like global_sort
finally.
In addition, the producer-consumer pattern in data encoding
at 6:06 PM Liang Chen wrote:
>
> > OK, thank you feedbacked this issue, let us look into it.
> >
> > Regards
> > Liang
> >
> >
> > Manhua Jiang wrote
> > > Hi All,
> > > Recently, I found carbon over-use cluster resources. Gener
> Ajantha
> >
> > On Tue, Apr 14, 2020 at 6:06 PM Liang Chen
> > wrote:
> >
> > > OK, thank you feedbacked this issue, let us look into it.
> > >
> > > Regards
> > > Liang
> > >
> > >
> > > Manhua Jiang wro
??Carbon??
??Carbon??
--Original--
From:"chenliang6136"http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
ote:
>
> > OK, thank you feedbacked this issue, let us look into it.
> >
> > Regards
> > Liang
> >
> >
> > Manhua Jiang wrote
> > > Hi All,
> > > Recently, I found carbon over-use cluster resources. Generally the
> design
> >
ked this issue, let us look into it.
>
> Regards
> Liang
>
>
> Manhua Jiang wrote
> > Hi All,
> > Recently, I found carbon over-use cluster resources. Generally the design
> > of carbon work flow does not act as common spark task which only do one
> > small
OK, thank you feedbacked this issue, let us look into it.
Regards
Liang
Manhua Jiang wrote
> Hi All,
> Recently, I found carbon over-use cluster resources. Generally the design
> of carbon work flow does not act as common spark task which only do one
> small work in one thread, but
Hi All,
Recently, I found carbon over-use cluster resources. Generally the design of
carbon work flow does not act as common spark task which only do one small work
in one thread, but the task has its mind/logic.
For example,
1.launch carbon with --num-executors=1 but set
