+1 with Anton decisions.
>Среда, 24 июля 2019, 8:44 +03:00 от Anton Vinogradov :
>
>Folks,
>
>It looks like we're trying to implement "extended debug" instead of
>"monitoring".
>It should not be interesting for real admin what phase of PME is in
>progress and so on.
>Interested metrics are
>- tot
Folks,
It looks like we're trying to implement "extended debug" instead of
"monitoring".
It should not be interesting for real admin what phase of PME is in
progress and so on.
Interested metrics are
- total blocked time (will be used for real SLA counting)
- are we blocked right now (shows we hav
Looping in the dev list.
Pavel, Igor and other C# maintainers, this looks like a valuable extension
of our C# APIs. Shouldn't this be a quick addition to Ignite?
-
Denis
On Mon, Jul 22, 2019 at 3:22 PM Raymond Wilson
wrote:
> Alexandr,
>
> If .WithExecute is not planned to be made available i
Mahesh Renduchintala created IGNITE-12008:
-
Summary: thick client has all system threads busy indefinitely
Key: IGNITE-12008
URL: https://issues.apache.org/jira/browse/IGNITE-12008
Project: Ign
Also there are more similar candidates:
* "Binary Objects (Simple Mapper Basic)" [1] corresponds to "Basic 1" [2]
* "Binary Objects (Simple Mapper Cache Full API)" [3] -- "Cache (Full API)" [4]
* "Binary Objects (Simple Mapper Compute Grid)" [5] -- "Compute (Grid)" [6]
I think they could be moved
Folks, let me step in.
Nikita, thanks for your suggestions!
1. initialVersion. Topology version that initiates the exchange.
2. initTime. Time PME was started.
3. initEvent. Event that triggered PME.
4. partitionReleaseTime. Time when a node has finished waiting for all
updates and translations
Igor Belyakov created IGNITE-12007:
--
Summary: Latest "apacheignite/web-console-backend" docker image is
broken
Key: IGNITE-12007
URL: https://issues.apache.org/jira/browse/IGNITE-12007
Project: Ignit
Hello, Dmitriy.
You are absolutely right.
I put the same answer on the SO, already.
В Вт, 23/07/2019 в 13:36 +0300, Dmitriy Pavlov пишет:
> Thank you, Stephen. I've checked this question. For now, it seems to me
> that keys are different on 2 different nodes. Why it can happen, it is not
> so c
Nikita,
I agree with total blocking duration metric but
I still don't understand why instant value indicating that operations are
blocked should be boolean.
Duration time since blocking has started looks more appropriate and useful.
It gives more information while semantic is left the same.
вт,
Thank you, Stephen. I've checked this question. For now, it seems to me
that keys are different on 2 different nodes. Why it can happen, it is not
so clear for me.
TDE verifies digests of master keys of nodes joining to cluster. These
digests should be equal. Equal keys give the same digests. The
Sergey Antonov created IGNITE-12006:
---
Summary: Threads may be parked for indefinite time during
throttling after spurious wakeups
Key: IGNITE-12006
URL: https://issues.apache.org/jira/browse/IGNITE-12006
I have a few ideas, maybe somebody will support me
1. Exclude Spatial Indexes from API for removal (I don't know internal
issues, but is I'd like this kind of index)
2. Exclude Storm, Flume, Flink from Integrations for Discontinuation
because I've ready to try support them (or dive in this question
Assume he means this one:
https://stackoverflow.com/questions/57124826/apache-ignite-transparent-data-encryption-master-key-digest-differs-node-join
> On 23 Jul 2019, at 11:02, Dmitriy Pavlov wrote:
>
> Hi Vladimir, could you please share link to the question?
>
> вт, 23 июл. 2019 г. в 12:47,
Hi Vladimir, could you please share link to the question?
вт, 23 июл. 2019 г. в 12:47, Vladimir Pligin :
> Hi igniters,
>
> I can see a question on SO
> http://apache-ignite-developers.2346864.n4.nabble.com. The question is
> related to encryption.
> Nikolay Izhikov, as far as know you're the aut
Hi igniters,
I can see a question on SO
http://apache-ignite-developers.2346864.n4.nabble.com. The question is
related to encryption.
Nikolay Izhikov, as far as know you're the author of the feature and
unfortunately I don't know anyone else who is familiar with it. Could you
please answer? Thanks
Folks,
All previous suggestions have some disadvantages. It can be several
exchanges between two metric updates and fast exchange can rewrite
previous long exchange.
We can introduce a metric of total blocking duration that will
accumulate at the end of the exchange. So, users will get actual
inf
16 matches
Mail list logo