Denis Magda created IGNITE-3501:
---
Summary: Step-by-step guidance on how to configure and use binary
type across Java and .Net
Key: IGNITE-3501
URL: https://issues.apache.org/jira/browse/IGNITE-3501
Proj
Hi everyone,
cross-posting from JIRA:
I recently came across this post:
http://codereview.stackexchange.com/a/31231
Do you think ReadWriteUpdateLock is something we can put to good use here
in Ignite?
This kind of lock should be more efficient for read-before-write patterns.
Best regards,
Vladi
On Mon, Jul 18, 2016 at 8:45 PM, Alexey Kuznetsov
wrote:
> I think we should have some general API and we could call it from web
> console and/or from other places.
>
Agree. The server side support should be sufficient to enable different
monitoring connections, including command-line visor, web
I think we should have some general API and we could call it from web
console and/or from other places.
18 Июл 2016 г. 20:18 пользователь "Dmitriy Setrakyan"
написал:
> I think we can add this functionality to Ignite web console, no?
>
> On Mon, Jul 18, 2016 at 11:08 AM, Vladimir Ozerov
> wrote
I think we can add this functionality to Ignite web console, no?
On Mon, Jul 18, 2016 at 11:08 AM, Vladimir Ozerov
wrote:
> Igor,
>
> I think that built-in monitoring facility will add great value to the
> product. We have to deal with user performance issues pretty often, and it
> is always a k
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/873
Ignite 2968
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-2968
Alternatively you can review and apply these chang
Alexey Goncharuk created IGNITE-3499:
Summary: GridCacheReplicatedFullApiMultithreadedSelfTest1 is
commented
Key: IGNITE-3499
URL: https://issues.apache.org/jira/browse/IGNITE-3499
Project: Ignite
Alexey Goncharuk created IGNITE-3500:
Summary: Generate expiry event in GridCacheMapEntry#checkExpired()
Key: IGNITE-3500
URL: https://issues.apache.org/jira/browse/IGNITE-3500
Project: Ignite
Alexey Goncharuk created IGNITE-3498:
Summary: Possible race leaving an untracked near entry
Key: IGNITE-3498
URL: https://issues.apache.org/jira/browse/IGNITE-3498
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-3497:
--
Summary: .NET: Improve IgniteConfigurationSection.XSD
Key: IGNITE-3497
URL: https://issues.apache.org/jira/browse/IGNITE-3497
Project: Ignite
Issue Type:
Pavel Tupitsyn created IGNITE-3496:
--
Summary: .NET: Identify 2.0 API changes
Key: IGNITE-3496
URL: https://issues.apache.org/jira/browse/IGNITE-3496
Project: Ignite
Issue Type: Task
Denis Magda created IGNITE-3495:
---
Summary: CacheMetrics.getAverage###Time is not calculated properly
Key: IGNITE-3495
URL: https://issues.apache.org/jira/browse/IGNITE-3495
Project: Ignite
Issu
Igor Sapego created IGNITE-3494:
---
Summary: CPP: Add tests for cross-platform put/get cache
operations.
Key: IGNITE-3494
URL: https://issues.apache.org/jira/browse/IGNITE-3494
Project: Ignite
I
Vasiliy Sisko created IGNITE-3493:
-
Summary: Web console: New item is not stored as selected.
Key: IGNITE-3493
URL: https://issues.apache.org/jira/browse/IGNITE-3493
Project: Ignite
Issue Typ
Vladimir Ozerov created IGNITE-3492:
---
Summary: IGFS: Support file-based evictions
Key: IGNITE-3492
URL: https://issues.apache.org/jira/browse/IGNITE-3492
Project: Ignite
Issue Type: Bug
Pavel Tupitsyn created IGNITE-3491:
--
Summary: .NET: Allow type name without assembly for type
properties in app.config
Key: IGNITE-3491
URL: https://issues.apache.org/jira/browse/IGNITE-3491
Project:
Andrey Novikov created IGNITE-3490:
--
Summary: Web console: Refactoring server side code to services,
append tests
Key: IGNITE-3490
URL: https://issues.apache.org/jira/browse/IGNITE-3490
Project: Igni
Igor,
I think that built-in monitoring facility will add great value to the
product. We have to deal with user performance issues pretty often, and it
is always a kind of pain to get to the bottom of the problem. We have to
ask users for configuration, logs, system config, etc, etc.. Instead, it
w
GitHub user dmagda opened a pull request:
https://github.com/apache/ignite/pull/872
ignite-3455
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3455
Alternatively you can review and apply these chan
19 matches
Mail list logo