SQL management and monitoring improvements

[Юрий]

Hi Igniters!

I think we can improve Ignite management and monitoring instruments related
to SQL.
I've prepared draft of IEP-29: SQL management and monitoring
<https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring>
.

What do you think about it? May be do you have some additional suggestions?


--
Живи с улыбкой! :D

[dmagda]

Yuri,

That's an excellent idea, thank you for driving it.

What is not explained is how to leverage from all that stat. For instance,
how can I know a total number of SELECTs, or a total number of SELECTs
happened yesterday for specific data sets. Do believe that it's feasible
and just not covered.

--
Denis



On Wed, Nov 7, 2018 at 2:01 AM Юрий <[hidden email]> wrote:

> Hi Igniters!
>
> I think we can improve Ignite management and monitoring instruments related
> to SQL.
> I've prepared draft of IEP-29: SQL management and monitoring
> <
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> >
> .
>
> What do you think about it? May be do you have some additional suggestions?
>
>
> --
> Живи с улыбкой! :D
>

[Alexey Plekhanov]

Yuri,

I think it will be useful if we extend in future management via SQL tool to
cover not only queries but also other parts of Ignite (for example: for
canceling tasks, for killing transactions, activation/deactivation,
baseline topology change, etc.).

Maybe, in this case, we should use a common prefix for such management
commands (like Oracle do: "ALTER SYSTEM ...")?

Something like:
ALTER GRID KILL QUERY ... [ON NODE ...]
ALTER GRID KILL TRANSACTION ... [ON NODE ...]
ALTER GRID ACTIVATE
etc.

What do you think about it?


чт, 8 нояб. 2018 г. в 0:06, Denis Magda <[hidden email]>:

> Yuri,
>
> That's an excellent idea, thank you for driving it.
>
> What is not explained is how to leverage from all that stat. For instance,
> how can I know a total number of SELECTs, or a total number of SELECTs
> happened yesterday for specific data sets. Do believe that it's feasible
> and just not covered.
>
> --
> Denis
>
>
>
> On Wed, Nov 7, 2018 at 2:01 AM Юрий <[hidden email]> wrote:
>
> > Hi Igniters!
> >
> > I think we can improve Ignite management and monitoring instruments
> related
> > to SQL.
> > I've prepared draft of IEP-29: SQL management and monitoring
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > .
> >
> > What do you think about it? May be do you have some additional
> suggestions?
> >
> >
> > --
> > Живи с улыбкой! :D
> >
>

[Юрий]

Denis,

I mentioned about it, may be it's not so clear now.  I'll try add more
explanation about it into IEP. It should be some SQL systems views and JMX
interfaces.
Deeper details will be covered in a tasks during more detailed analyze.

Thanks for your feedback.


чт, 8 нояб. 2018 г. в 0:06, Denis Magda <[hidden email]>:

> Yuri,
>
> That's an excellent idea, thank you for driving it.
>
> What is not explained is how to leverage from all that stat. For instance,
> how can I know a total number of SELECTs, or a total number of SELECTs
> happened yesterday for specific data sets. Do believe that it's feasible
> and just not covered.
>
> --
> Denis
>
>
>
> On Wed, Nov 7, 2018 at 2:01 AM Юрий <[hidden email]> wrote:
>
> > Hi Igniters!
> >
> > I think we can improve Ignite management and monitoring instruments
> related
> > to SQL.
> > I've prepared draft of IEP-29: SQL management and monitoring
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > .
> >
> > What do you think about it? May be do you have some additional
> suggestions?
> >
> >
> > --
> > Живи с улыбкой! :D
> >
>

--
Живи с улыбкой! :D

[Юрий]

Hi Alex,

Thanks for the ideas! It will be useful.
However, from my side, Oracle like syntax looks excess. Will be good if
someone else say opinion opinion about syntax.

Igniters, what do you think which syntax of Ignite management via SQL will
be prefer?


пт, 9 нояб. 2018 г. в 0:37, Alex Plehanov <[hidden email]>:

> Yuri,
>
> I think it will be useful if we extend in future management via SQL tool to
> cover not only queries but also other parts of Ignite (for example: for
> canceling tasks, for killing transactions, activation/deactivation,
> baseline topology change, etc.).
>
> Maybe, in this case, we should use a common prefix for such management
> commands (like Oracle do: "ALTER SYSTEM ...")?
>
> Something like:
> ALTER GRID KILL QUERY ... [ON NODE ...]
> ALTER GRID KILL TRANSACTION ... [ON NODE ...]
> ALTER GRID ACTIVATE
> etc.
>
> What do you think about it?
>
>
> чт, 8 нояб. 2018 г. в 0:06, Denis Magda <[hidden email]>:
>
> > Yuri,
> >
> > That's an excellent idea, thank you for driving it.
> >
> > What is not explained is how to leverage from all that stat. For
> instance,
> > how can I know a total number of SELECTs, or a total number of SELECTs
> > happened yesterday for specific data sets. Do believe that it's feasible
> > and just not covered.
> >
> > --
> > Denis
> >
> >
> >
> > On Wed, Nov 7, 2018 at 2:01 AM Юрий <[hidden email]> wrote:
> >
> > > Hi Igniters!
> > >
> > > I think we can improve Ignite management and monitoring instruments
> > related
> > > to SQL.
> > > I've prepared draft of IEP-29: SQL management and monitoring
> > > <
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > > >
> > > .
> > >
> > > What do you think about it? May be do you have some additional
> > suggestions?
> > >
> > >
> > > --
> > > Живи с улыбкой! :D
> > >
> >
>

--
Живи с улыбкой! :D

[Vladimir Ozerov]

Yuri,

Do you have any ideas in mind?

On Mon, Nov 12, 2018 at 1:25 PM Юрий <[hidden email]> wrote:

> Hi Alex,
>
> Thanks for the ideas! It will be useful.
> However, from my side, Oracle like syntax looks excess. Will be good if
> someone else say opinion opinion about syntax.
>
> Igniters, what do you think which syntax of Ignite management via SQL will
> be prefer?
>
>
> пт, 9 нояб. 2018 г. в 0:37, Alex Plehanov <[hidden email]>:
>
> > Yuri,
> >
> > I think it will be useful if we extend in future management via SQL tool
> to
> > cover not only queries but also other parts of Ignite (for example: for
> > canceling tasks, for killing transactions, activation/deactivation,
> > baseline topology change, etc.).
> >
> > Maybe, in this case, we should use a common prefix for such management
> > commands (like Oracle do: "ALTER SYSTEM ...")?
> >
> > Something like:
> > ALTER GRID KILL QUERY ... [ON NODE ...]
> > ALTER GRID KILL TRANSACTION ... [ON NODE ...]
> > ALTER GRID ACTIVATE
> > etc.
> >
> > What do you think about it?
> >
> >
> > чт, 8 нояб. 2018 г. в 0:06, Denis Magda <[hidden email]>:
> >
> > > Yuri,
> > >
> > > That's an excellent idea, thank you for driving it.
> > >
> > > What is not explained is how to leverage from all that stat. For
> > instance,
> > > how can I know a total number of SELECTs, or a total number of SELECTs
> > > happened yesterday for specific data sets. Do believe that it's
> feasible
> > > and just not covered.
> > >
> > > --
> > > Denis
> > >
> > >
> > >
> > > On Wed, Nov 7, 2018 at 2:01 AM Юрий <[hidden email]>
> wrote:
> > >
> > > > Hi Igniters!
> > > >
> > > > I think we can improve Ignite management and monitoring instruments
> > > related
> > > > to SQL.
> > > > I've prepared draft of IEP-29: SQL management and monitoring
> > > > <
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > > > >
> > > > .
> > > >
> > > > What do you think about it? May be do you have some additional
> > > suggestions?
> > > >
> > > >
> > > > --
> > > > Живи с улыбкой! :D
> > > >
> > >
> >
>
>
> --
> Живи с улыбкой! :D
>