How can I stop getting these updates ?
On Mon, Aug 21, 2023 at 9:01 AM Robson Hermes <robsonhermes@gmail.com>
wrote:
> This email was sent from an external source so please treat with caution.
>
> No, it stops them also.
> The problem is precisely what Greg described, now the stop signal comes
> from the same thread. So any source task which is running in a blocking way
> will not process the stop signal until the current poll finishes.
> So would need to patch source jdbc connector.
>
> On Mon, 21 Aug 2023 at 15:48, sunil chaudhari <sunilmchaudhari05@gmail.com
> >
> wrote:
>
> > I think when you delete connector it removes the task and workers
> continues
> > to run.
> > When you stop it actually stops the worker.
> > Both different things.
> > Point to be noted is Worker has connector.
> > So connector should be removed before stopping the worker.
> >
> > Though I am not expert in this.
> >
> > On Mon, 21 Aug 2023 at 7:10 PM, Robson Hermes <robsonhermes@gmail.com>
> > wrote:
> >
> > > Hello Sunil
> > >
> > > I'm not calling a stop, I'm straight deleting the connectors with the
> > > DELETE. Stopping the connector is done internally during deletion.
> > >
> > > Regards
> > > Robson
> > >
> > > On Mon, 21 Aug 2023 at 15:36, sunil chaudhari <
> > sunilmchaudhari05@gmail.com
> > > >
> > > wrote:
> > >
> > > > You have to remove connectors first using delete api
> > > > and then stop the connector
> > > >
> > > > On Thu, 17 Aug 2023 at 2:51 AM, Robson Hermes <
> robsonhermes@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello
> > > > >
> > > > > I'm using kafka connect 7.4.0 to read data from Postgres views and
> > > write
> > > > to
> > > > > another Postgres tables. So using JDBC source and sink connectors.
> > > > > All works good, but whenever I stop the source connectors via the
> > rest
> > > > api:
> > > > >
> > > > > DEL http://kafka-connect:8083/connectors/connector_name_here
> > > > >
> > > > > The connector stops fine, but not the task:
> > > > >
> > > > >
> > > > > Graceful stop of connector (connector-name-here) succeeded.
> > > > >
> > > > > Graceful stop of task (task-name-here) failed.
> > > > >
> > > > >
> > > > > It only happens with the *source* connector tasks. The sink
> connector
> > > > > and tasks shutdown gracefully and fine.
> > > > >
> > > > > The timeout for task shutdown has been increased, but didn't help:
> > > > >
> > > > > task.shutdown.graceful.timeout.ms=60000
> > > > >
> > > > >
> > > > >
> > > > > The connectors are running once per day (during the night) to load
> a
> > > > > lot of data, and the error happens when I try to delete the
> > connectors
> > > > > in the middle of the day. That is, they are not actually
> > > > > executing/loading any data, it has finished already.
> > > > >
> > > > > offset.flush.interval.ms=10000 in development and integration
> > > > > environments.
> > > > >
> > > > > offset.flush.interval.ms=60000 in production and uat.
> > > > >
> > > > >
> > > > > The rest of the config is pretty much the default.
> > > > >
> > > > > What could be the issue?
> > > > >
> > > > > The errors of the graceful stop of the tasks are triggering our
> alert
> > > > > system, so trying to get rid of those.
> > > > >
> > > > >
> > > > > Thanks a lot
> > > > >
> > > > > Robson
> > > > >
> > > >
> > >
> >
>
About Ascential plc
Ascential delivers specialist information, analytics and ecommerce optimisation platforms to the world's leading consumer brands and their ecosystems.
Our world-class businesses improve performance and solve problems for our customers by delivering immediately actionable information combined with visionary longer-term thinking across Digital Commerce, Product Design and Marketing. We also serve customers across Retail & Financial Services.
With over 3,000 employees across five continents, we combine local expertise with a global footprint for clients in over 120 countries.
Ascential is listed on the London Stock Exchange.
The information in or attached to this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any use, disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful.
If you have received this message in error, please notify the sender immediately by return email and delete this message and any copies from your computer and network. Ascential does not warrant that this email and any attachments are free from viruses and accepts no liability for any loss resulting from infected email transmissions.
Ascential reserves the right to monitor all email through its networks. Any view expressed may be those of the originator and not necessarily of Ascential plc. Please be advised all phone calls may be recorded for training and quality purposes and by accepting and/or making calls to us you acknowledge and agree to calls being recorded.
Ascential plc, number 9934451 (England and Wales). Registered Office: 33 Kingsway, London, WC2B 6UF.
On Mon, Aug 21, 2023 at 9:01 AM Robson Hermes <robsonhermes@gmail.com>
wrote:
> This email was sent from an external source so please treat with caution.
>
> No, it stops them also.
> The problem is precisely what Greg described, now the stop signal comes
> from the same thread. So any source task which is running in a blocking way
> will not process the stop signal until the current poll finishes.
> So would need to patch source jdbc connector.
>
> On Mon, 21 Aug 2023 at 15:48, sunil chaudhari <sunilmchaudhari05@gmail.com
> >
> wrote:
>
> > I think when you delete connector it removes the task and workers
> continues
> > to run.
> > When you stop it actually stops the worker.
> > Both different things.
> > Point to be noted is Worker has connector.
> > So connector should be removed before stopping the worker.
> >
> > Though I am not expert in this.
> >
> > On Mon, 21 Aug 2023 at 7:10 PM, Robson Hermes <robsonhermes@gmail.com>
> > wrote:
> >
> > > Hello Sunil
> > >
> > > I'm not calling a stop, I'm straight deleting the connectors with the
> > > DELETE. Stopping the connector is done internally during deletion.
> > >
> > > Regards
> > > Robson
> > >
> > > On Mon, 21 Aug 2023 at 15:36, sunil chaudhari <
> > sunilmchaudhari05@gmail.com
> > > >
> > > wrote:
> > >
> > > > You have to remove connectors first using delete api
> > > > and then stop the connector
> > > >
> > > > On Thu, 17 Aug 2023 at 2:51 AM, Robson Hermes <
> robsonhermes@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello
> > > > >
> > > > > I'm using kafka connect 7.4.0 to read data from Postgres views and
> > > write
> > > > to
> > > > > another Postgres tables. So using JDBC source and sink connectors.
> > > > > All works good, but whenever I stop the source connectors via the
> > rest
> > > > api:
> > > > >
> > > > > DEL http://kafka-connect:8083/connectors/connector_name_here
> > > > >
> > > > > The connector stops fine, but not the task:
> > > > >
> > > > >
> > > > > Graceful stop of connector (connector-name-here) succeeded.
> > > > >
> > > > > Graceful stop of task (task-name-here) failed.
> > > > >
> > > > >
> > > > > It only happens with the *source* connector tasks. The sink
> connector
> > > > > and tasks shutdown gracefully and fine.
> > > > >
> > > > > The timeout for task shutdown has been increased, but didn't help:
> > > > >
> > > > > task.shutdown.graceful.timeout.ms=60000
> > > > >
> > > > >
> > > > >
> > > > > The connectors are running once per day (during the night) to load
> a
> > > > > lot of data, and the error happens when I try to delete the
> > connectors
> > > > > in the middle of the day. That is, they are not actually
> > > > > executing/loading any data, it has finished already.
> > > > >
> > > > > offset.flush.interval.ms=10000 in development and integration
> > > > > environments.
> > > > >
> > > > > offset.flush.interval.ms=60000 in production and uat.
> > > > >
> > > > >
> > > > > The rest of the config is pretty much the default.
> > > > >
> > > > > What could be the issue?
> > > > >
> > > > > The errors of the graceful stop of the tasks are triggering our
> alert
> > > > > system, so trying to get rid of those.
> > > > >
> > > > >
> > > > > Thanks a lot
> > > > >
> > > > > Robson
> > > > >
> > > >
> > >
> >
>
About Ascential plc
Ascential delivers specialist information, analytics and ecommerce optimisation platforms to the world's leading consumer brands and their ecosystems.
Our world-class businesses improve performance and solve problems for our customers by delivering immediately actionable information combined with visionary longer-term thinking across Digital Commerce, Product Design and Marketing. We also serve customers across Retail & Financial Services.
With over 3,000 employees across five continents, we combine local expertise with a global footprint for clients in over 120 countries.
Ascential is listed on the London Stock Exchange.
The information in or attached to this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any use, disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful.
If you have received this message in error, please notify the sender immediately by return email and delete this message and any copies from your computer and network. Ascential does not warrant that this email and any attachments are free from viruses and accepts no liability for any loss resulting from infected email transmissions.
Ascential reserves the right to monitor all email through its networks. Any view expressed may be those of the originator and not necessarily of Ascential plc. Please be advised all phone calls may be recorded for training and quality purposes and by accepting and/or making calls to us you acknowledge and agree to calls being recorded.
Ascential plc, number 9934451 (England and Wales). Registered Office: 33 Kingsway, London, WC2B 6UF.
Comments
Post a Comment