You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Petr Ivanov <mr...@gmail.com> on 2018/10/09 14:43:07 UTC
Re: Upsource lags and connection timeouts
New dedicated disk subsystem is installed for MTCGA utility, hope that'll help to free resources for other services.
> On 21 Sep 2018, at 21:10, Anton Vinogradov <av...@apache.org> wrote:
>
> Folks,
>
> Thanks for the investigation!
> Could you please let us know once the problem will be solved?
>
> пт, 21 сент. 2018 г. в 19:28, Dmitriy Pavlov <dp...@gmail.com>:
>
>> Hi Anton, Petr,
>>
>> I confirm that TC Bot writes a lot of stuff, so it may create problems for
>> Cassandra storage.
>>
>> The latest version of Bot has optimization of data saving, and its reduces
>> amount of data to be saved to disk. But still, disc separation is a better
>> solution.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пт, 21 сент. 2018 г. в 19:19, Petr Ivanov <mr...@gmail.com>:
>>
>>> Anton,
>>>
>>>
>>> We shared this issue with Jetbrains and they found no current problems in
>>> logs, except possible problems with database connection (Apache
>> Cassandra).
>>> Currently there are no errors in logs.
>>>
>>> Possible troublemakers though exist:
>>> - MTCGA utility “lives” on the same server, possible resource race
>>> condition, will try to separate services (at least on disk subsystem
>> level)
>>> - connection to GitHub is an issue too — sometimes fetch speed drops
>>> significantly, that will be investigated also
>>>
>>>
>>>> On 20 Sep 2018, at 22:18, Anton Vinogradov <av...@apache.org> wrote:
>>>>
>>>> Still, see the same issues.
>>>>
>>>> Denis,
>>>>
>>>> Could you please prioritize the fix?
>>>>
>>>> вт, 18 сент. 2018 г. в 14:01, Anton Vinogradov <av...@apache.org>:
>>>>
>>>>> Also, I see following on each resolve attempt.
>>>>> UpsourceRequestExceptionImpl: 108: Internal error: An error occurred
>>>>> during flushing data to database
>>>>>
>>>>>
>>>>>
>>>>> вт, 18 сент. 2018 г. в 13:56, Anton Vinogradov <av...@apache.org>:
>>>>>
>>>>>> Folks,
>>>>>>
>>>>>> Who is responsible for Upsouce [1]?
>>>>>> I see a performance issues last week.
>>>>>> Can we check Upsource health?
>>>>>>
>>>>>> [1] https://reviews.ignite.apache.org
>>>>>>
>>>>>
>>>
>>>
>>
Re: Upsource lags and connection timeouts
Posted by Petr Ivanov <mr...@gmail.com>.
I am glad to help.
> On 9 Oct 2018, at 19:21, Dmitriy Pavlov <dp...@gmail.com> wrote:
>
> Hi Petr,
>
> I can't stress this enough, but this modification had a really positive
> impact to TC bot performance.
>
> Now it provides responses much faster. I hope it will help us to use this
> tool and integrate into our processes.
>
> Thank you for your efforts.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 9 окт. 2018 г. в 18:00, Anton Vinogradov <av...@apache.org>:
>
>> Thank you very much!
>>
>> вт, 9 окт. 2018 г. в 17:43, Petr Ivanov <mr...@gmail.com>:
>>
>>> New dedicated disk subsystem is installed for MTCGA utility, hope that'll
>>> help to free resources for other services.
>>>
>>>
>>>> On 21 Sep 2018, at 21:10, Anton Vinogradov <av...@apache.org> wrote:
>>>>
>>>> Folks,
>>>>
>>>> Thanks for the investigation!
>>>> Could you please let us know once the problem will be solved?
>>>>
>>>> пт, 21 сент. 2018 г. в 19:28, Dmitriy Pavlov <dp...@gmail.com>:
>>>>
>>>>> Hi Anton, Petr,
>>>>>
>>>>> I confirm that TC Bot writes a lot of stuff, so it may create problems
>>> for
>>>>> Cassandra storage.
>>>>>
>>>>> The latest version of Bot has optimization of data saving, and its
>>> reduces
>>>>> amount of data to be saved to disk. But still, disc separation is a
>>> better
>>>>> solution.
>>>>>
>>>>> Sincerely,
>>>>> Dmitriy Pavlov
>>>>>
>>>>> пт, 21 сент. 2018 г. в 19:19, Petr Ivanov <mr...@gmail.com>:
>>>>>
>>>>>> Anton,
>>>>>>
>>>>>>
>>>>>> We shared this issue with Jetbrains and they found no current
>> problems
>>> in
>>>>>> logs, except possible problems with database connection (Apache
>>>>> Cassandra).
>>>>>> Currently there are no errors in logs.
>>>>>>
>>>>>> Possible troublemakers though exist:
>>>>>> - MTCGA utility “lives” on the same server, possible resource race
>>>>>> condition, will try to separate services (at least on disk subsystem
>>>>> level)
>>>>>> - connection to GitHub is an issue too — sometimes fetch speed drops
>>>>>> significantly, that will be investigated also
>>>>>>
>>>>>>
>>>>>>> On 20 Sep 2018, at 22:18, Anton Vinogradov <av...@apache.org> wrote:
>>>>>>>
>>>>>>> Still, see the same issues.
>>>>>>>
>>>>>>> Denis,
>>>>>>>
>>>>>>> Could you please prioritize the fix?
>>>>>>>
>>>>>>> вт, 18 сент. 2018 г. в 14:01, Anton Vinogradov <av...@apache.org>:
>>>>>>>
>>>>>>>> Also, I see following on each resolve attempt.
>>>>>>>> UpsourceRequestExceptionImpl: 108: Internal error: An error
>> occurred
>>>>>>>> during flushing data to database
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> вт, 18 сент. 2018 г. в 13:56, Anton Vinogradov <av...@apache.org>:
>>>>>>>>
>>>>>>>>> Folks,
>>>>>>>>>
>>>>>>>>> Who is responsible for Upsouce [1]?
>>>>>>>>> I see a performance issues last week.
>>>>>>>>> Can we check Upsource health?
>>>>>>>>>
>>>>>>>>> [1] https://reviews.ignite.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>
>>>
>>
Re: Upsource lags and connection timeouts
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Petr,
I can't stress this enough, but this modification had a really positive
impact to TC bot performance.
Now it provides responses much faster. I hope it will help us to use this
tool and integrate into our processes.
Thank you for your efforts.
Sincerely,
Dmitriy Pavlov
вт, 9 окт. 2018 г. в 18:00, Anton Vinogradov <av...@apache.org>:
> Thank you very much!
>
> вт, 9 окт. 2018 г. в 17:43, Petr Ivanov <mr...@gmail.com>:
>
> > New dedicated disk subsystem is installed for MTCGA utility, hope that'll
> > help to free resources for other services.
> >
> >
> > > On 21 Sep 2018, at 21:10, Anton Vinogradov <av...@apache.org> wrote:
> > >
> > > Folks,
> > >
> > > Thanks for the investigation!
> > > Could you please let us know once the problem will be solved?
> > >
> > > пт, 21 сент. 2018 г. в 19:28, Dmitriy Pavlov <dp...@gmail.com>:
> > >
> > >> Hi Anton, Petr,
> > >>
> > >> I confirm that TC Bot writes a lot of stuff, so it may create problems
> > for
> > >> Cassandra storage.
> > >>
> > >> The latest version of Bot has optimization of data saving, and its
> > reduces
> > >> amount of data to be saved to disk. But still, disc separation is a
> > better
> > >> solution.
> > >>
> > >> Sincerely,
> > >> Dmitriy Pavlov
> > >>
> > >> пт, 21 сент. 2018 г. в 19:19, Petr Ivanov <mr...@gmail.com>:
> > >>
> > >>> Anton,
> > >>>
> > >>>
> > >>> We shared this issue with Jetbrains and they found no current
> problems
> > in
> > >>> logs, except possible problems with database connection (Apache
> > >> Cassandra).
> > >>> Currently there are no errors in logs.
> > >>>
> > >>> Possible troublemakers though exist:
> > >>> - MTCGA utility “lives” on the same server, possible resource race
> > >>> condition, will try to separate services (at least on disk subsystem
> > >> level)
> > >>> - connection to GitHub is an issue too — sometimes fetch speed drops
> > >>> significantly, that will be investigated also
> > >>>
> > >>>
> > >>>> On 20 Sep 2018, at 22:18, Anton Vinogradov <av...@apache.org> wrote:
> > >>>>
> > >>>> Still, see the same issues.
> > >>>>
> > >>>> Denis,
> > >>>>
> > >>>> Could you please prioritize the fix?
> > >>>>
> > >>>> вт, 18 сент. 2018 г. в 14:01, Anton Vinogradov <av...@apache.org>:
> > >>>>
> > >>>>> Also, I see following on each resolve attempt.
> > >>>>> UpsourceRequestExceptionImpl: 108: Internal error: An error
> occurred
> > >>>>> during flushing data to database
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> вт, 18 сент. 2018 г. в 13:56, Anton Vinogradov <av...@apache.org>:
> > >>>>>
> > >>>>>> Folks,
> > >>>>>>
> > >>>>>> Who is responsible for Upsouce [1]?
> > >>>>>> I see a performance issues last week.
> > >>>>>> Can we check Upsource health?
> > >>>>>>
> > >>>>>> [1] https://reviews.ignite.apache.org
> > >>>>>>
> > >>>>>
> > >>>
> > >>>
> > >>
> >
> >
>
Re: Upsource lags and connection timeouts
Posted by Anton Vinogradov <av...@apache.org>.
Thank you very much!
вт, 9 окт. 2018 г. в 17:43, Petr Ivanov <mr...@gmail.com>:
> New dedicated disk subsystem is installed for MTCGA utility, hope that'll
> help to free resources for other services.
>
>
> > On 21 Sep 2018, at 21:10, Anton Vinogradov <av...@apache.org> wrote:
> >
> > Folks,
> >
> > Thanks for the investigation!
> > Could you please let us know once the problem will be solved?
> >
> > пт, 21 сент. 2018 г. в 19:28, Dmitriy Pavlov <dp...@gmail.com>:
> >
> >> Hi Anton, Petr,
> >>
> >> I confirm that TC Bot writes a lot of stuff, so it may create problems
> for
> >> Cassandra storage.
> >>
> >> The latest version of Bot has optimization of data saving, and its
> reduces
> >> amount of data to be saved to disk. But still, disc separation is a
> better
> >> solution.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> пт, 21 сент. 2018 г. в 19:19, Petr Ivanov <mr...@gmail.com>:
> >>
> >>> Anton,
> >>>
> >>>
> >>> We shared this issue with Jetbrains and they found no current problems
> in
> >>> logs, except possible problems with database connection (Apache
> >> Cassandra).
> >>> Currently there are no errors in logs.
> >>>
> >>> Possible troublemakers though exist:
> >>> - MTCGA utility “lives” on the same server, possible resource race
> >>> condition, will try to separate services (at least on disk subsystem
> >> level)
> >>> - connection to GitHub is an issue too — sometimes fetch speed drops
> >>> significantly, that will be investigated also
> >>>
> >>>
> >>>> On 20 Sep 2018, at 22:18, Anton Vinogradov <av...@apache.org> wrote:
> >>>>
> >>>> Still, see the same issues.
> >>>>
> >>>> Denis,
> >>>>
> >>>> Could you please prioritize the fix?
> >>>>
> >>>> вт, 18 сент. 2018 г. в 14:01, Anton Vinogradov <av...@apache.org>:
> >>>>
> >>>>> Also, I see following on each resolve attempt.
> >>>>> UpsourceRequestExceptionImpl: 108: Internal error: An error occurred
> >>>>> during flushing data to database
> >>>>>
> >>>>>
> >>>>>
> >>>>> вт, 18 сент. 2018 г. в 13:56, Anton Vinogradov <av...@apache.org>:
> >>>>>
> >>>>>> Folks,
> >>>>>>
> >>>>>> Who is responsible for Upsouce [1]?
> >>>>>> I see a performance issues last week.
> >>>>>> Can we check Upsource health?
> >>>>>>
> >>>>>> [1] https://reviews.ignite.apache.org
> >>>>>>
> >>>>>
> >>>
> >>>
> >>
>
>