Vasiliy Sisko created IGNITE-6995:
-
Summary: Visor CMD: Actualize showed grid/cache configuration.
Key: IGNITE-6995
URL: https://issues.apache.org/jira/browse/IGNITE-6995
Project: Ignite
Issu
I think you are talking about the case when cluster temporarily gets into
unbalanced state and needs to rebalance. However, I am still not sure what
this metric would show. Can you provide an example?
D.
On Wed, Nov 22, 2017 at 2:10 PM, Alex Plehanov
wrote:
> It's not about caches.
> Each parti
Sounds like a positive step forward. I have several comments:
1. "More Features" should be all the way at the bottom
2. "What is Ignite" should go under Features
3. I would remove the words "Distributed" from the navigation menu and
leave "Key-Value" and "SQL". Otherwise, you would be adding the w
Thanks.
-Original Message-
From: Denis Magda [mailto:dma...@apache.org]
Sent: Thursday, November 23, 2017 4:30 AM
To: dev@ignite.apache.org
Subject: Re: Contributor permissions
Please try to assign the ticket now and let me know if you still have issues
with JIRA.
—
Denis
> On Nov 22
Please try to assign the ticket now and let me know if you still have issues
with JIRA.
—
Denis
> On Nov 22, 2017, at 3:38 PM, Cergey wrote:
>
> My username is cossack5.
> I have not noticed any change (still can't assign tickets to myself) since I
> asked before. Maybe I need to do somethin
My username is cossack5.
I have not noticed any change (still can't assign tickets to myself) since I
asked before. Maybe I need to do something on my part ?
-Original Message-
From: Denis Magda [mailto:dma...@apache.org]
Sent: Thursday, November 23, 2017 1:50 AM
To: dev@ignite.apache.o
Val, Nikolay,
Personally, I think that we should release the integration only after the
strategy is fully supported. Without the strategy we don’t really leverage from
Ignite’s SQL engine and introduce redundant data movement between Ignite and
Spark nodes.
How big is the effort to support the
Nikolay,
Custom strategy implementation is actually very important for this
integration. Basically, it will allow to create a SQL query for Ignite and
execute it directly on the cluster. Your current implementation only adds a
new DataSource which means that Spark will fetch data in its own memory
The list formatting was broken by ASF mail engine. Fixed below.
> On Nov 22, 2017, at 2:51 PM, Denis Magda wrote:
>
> - What’s Ignite?
> - Features
> — Distributed Key-Value
> — Distributed SQL
> — ACID Transactions
> — Machine Learning
> — Multi-Language Support
> — More Features…
>
Igniters,
Personally, I like the current version of the landing page reworked several
months ago. However, once the user finishes with the landing page and begins
exploring Ignite capabilities he/she will intuitively go to the “Features”
menu…which definitely requires meticulous grooming.
The
Vyacheslav,
There is no way to do this and I'm not sure why you want to do this. Ignite
persistence was developed to solve exactly the problems you're describing.
Just use it :)
-Val
On Wed, Nov 22, 2017 at 12:36 AM, Vyacheslav Daradur
wrote:
> Valentin, Evgeniy thanks for your help!
>
> Valen
It's not about caches.
Each partition has certain amount of copies. Amount of copies may differ
for different partitions of one cache group.
This configuration possible:
1) With custom affinity function
2) When nodes left the cluster, till rebalancing is not finished
2017-11-23 0:18 GMT+03:00 D
Nikita,
Your solution sounds reasonable from the first glance. However, the
communication layer processes a dozen of small system messages that should be
excluded from the compression. Guess, that we will spend more time on
compressing/decompressing them thus diminishing the positive effect of
Valentin Kulichenko created IGNITE-6994:
---
Summary: Need to document PartitionLossPolicy
Key: IGNITE-6994
URL: https://issues.apache.org/jira/browse/IGNITE-6994
Project: Ignite
Issue Typ
What’s your JIRA id?
I believe you were added to JIRA’s contributor list before.
—
Denis
> On Nov 22, 2017, at 12:22 PM, Cergey wrote:
>
> Please, can I be given contributor permissions ?
>
>
>
> Regards,
>
> Cergey Chaulin
>
>
>
Just provide FailureProcessingPolicy with possible reactions:
- NOOP - exceptions will be reported, metrics will be triggered but an affected
Ignite process won’t be touched.
- HAULT (or STOP or KILL) - all the actions of the of NOOP + Ignite process
termination.
- RESTART - NOOP actions + proces
Denis Magda created IGNITE-6993:
---
Summary: Document SMTP server documentation for Web Console
Key: IGNITE-6993
URL: https://issues.apache.org/jira/browse/IGNITE-6993
Project: Ignite
Issue Type:
On Wed, Nov 22, 2017 at 12:39 PM, Alex Plehanov
wrote:
> Hello Dmitriy,
>
> I agree.
>
> By "minimal partition redundancy level for cache group" I mean minimal
> number of partition copies among all partitions of this cache group.
> For example, if we have in our cluster for cache group one parti
Hello Dmitriy,
I agree.
By "minimal partition redundancy level for cache group" I mean minimal
number of partition copies among all partitions of this cache group.
For example, if we have in our cluster for cache group one partition with 2
copies (1 primary and 1 backup) and other partitions with
Please, can I be given contributor permissions ?
Regards,
Cergey Chaulin
Thanks Pavel! The document has good information. I'll create one on
readme.io; will also add some examples there.
On Wed, Nov 22, 2017 at 5:03 AM, Pavel Tupitsyn
wrote:
> Igniters,
>
> I've put together a detailed description of our Thin Client protocol
> in form of IEP on wiki:
> https://cwiki.
Vova,
Monitoring systems works not how you expected, they LOVE incremental
metrics :)
> 1) When did these events appear?
Monitoring gets metrics each N seconds.
01.00 got 0, 0
02.00 got 1, 20 -> means between 02.00 and 01.00 was 1 STW with duration 20
03.00 got 3, 100 -> means between 03.00 a
I think it is very useful feature.
I also have experience when server nodes connected via fast network.
But client nodes via very slow network.
I implemeted GridClientZipOptimizedMarshaller and that solved my issue.
But this marshaller works only with old
and org.apache.ignite.internal.client.Grid
Evgenii Zhuravlev created IGNITE-6992:
-
Summary: Ignite MR problem with accessing hdfs with enabled
Kerberos
Key: IGNITE-6992
URL: https://issues.apache.org/jira/browse/IGNITE-6992
Project: Ignite
The question is how administrator should interpret these numbers. Ok, I
opened JMX console and see that there was 10 long GC events, which took 100
seconds.
1) When did these events appear? Over the last day, which is more or less
OK, or over the last 10 minutes, so my server is nearly dead?
2) How
Vladislav Pyatkov created IGNITE-6991:
-
Summary: SharedDeploymentTest.testDeploymentFromSecondAndThird
Test fails in 100 percentage cases
Key: IGNITE-6991
URL: https://issues.apache.org/jira/browse/IGNITE-6991
Igniters,
I've put together a detailed description of our Thin Client protocol
in form of IEP on wiki:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol
To clarify:
- Protocol implementation is in master (see ClientMessageParser class)
- Protocol has not been released
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/3008
---
Hello, Igniters!
I think it is a useful feature. I suggest to implement it to communication
SPI like SSL encryption implemented. I have experience with this feature
and I can try to develop it.
2017-11-22 12:01 GMT+03:00 Alexey Kukushkin :
> Forwarding to DEV list: Ignite developers, could you p
Pavel Tupitsyn created IGNITE-6990:
--
Summary: .NET: Thin client: Remove OP_SQL_QUERY
Key: IGNITE-6990
URL: https://issues.apache.org/jira/browse/IGNITE-6990
Project: Ignite
Issue Type: Impro
Pavel Tupitsyn created IGNITE-6989:
--
Summary: .NET: Thin client: Group operation codes by purpose
Key: IGNITE-6989
URL: https://issues.apache.org/jira/browse/IGNITE-6989
Project: Ignite
Issu
Pavel Tupitsyn created IGNITE-6988:
--
Summary: .NET: Thin client: OP_DESTROY_CACHE should take cacheId
instead of name
Key: IGNITE-6988
URL: https://issues.apache.org/jira/browse/IGNITE-6988
Project:
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3081
Ignite-gg-13086
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-gg-13086
Alternatively you can review and apply th
Vasiliy Sisko created IGNITE-6987:
-
Summary: Visor CMD: Config command should show client connector
pool size.
Key: IGNITE-6987
URL: https://issues.apache.org/jira/browse/IGNITE-6987
Project: Ignite
Vova,
1) We can gain collections info from GarbageCollectorMXBean
But it provides only
- collectionCount
- collectionTime.
This is very interesting metrics, but they tell us nothing about long STW.
Long STW means we have huge latency during STW and we should find the
reason and solve it.
2) So,
Pavel Tupitsyn created IGNITE-6986:
--
Summary: .NET: Some exceptions can't be serialized
Key: IGNITE-6986
URL: https://issues.apache.org/jira/browse/IGNITE-6986
Project: Ignite
Issue Type: Bu
Hi, Igntrs!
Client reconnect cause transactions rollback in
IgniteTxManager#onDisconnected.
But it doesn’t change transaction state to ROLLING_BACK and ROLLED_BACK.
Thus every transaction, after client node reconnects, has got ACTIVE
status, which seems incorrect.
I added PR where you can find
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3080
IGNITE-6985 Wrong value of RebalancingStartTime cache metric
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignit
Aleksey Plekhanov created IGNITE-6985:
-
Summary: Wrong value of RebalancingStartTime cache metric
Key: IGNITE-6985
URL: https://issues.apache.org/jira/browse/IGNITE-6985
Project: Ignite
I
Forwarding to DEV list: Ignite developers, could you please share your
thoughts on how hard it is to extend Ignite to compress data on the network.
On Wed, Nov 22, 2017 at 10:04 AM, Gordon Reid (Nine Mile) <
gordon.r...@ninemilefinancial.com> wrote:
> Hi Igniters,
>
>
>
> I see there is a lot of
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/3079
Ignite incorrect state reconnect
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite ignite-incorrect-state-reconnect
Alternatively you
Valentin, Evgeniy thanks for your help!
Valentin, unfortunately, you are right.
I've tested that behavior in the following scenario:
1. Started N nodes and filled it with data
2. Shutdown one node
3. Called rebalance directly and waited to finish
4. Stopped all other (N-1) nodes
5. Started N-1 no
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3078
IGNITE-6984: Make cache creation slightly more verbose.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6984
Andrew Mashenkov created IGNITE-6984:
Summary: Make cache creation slightly more verbose.
Key: IGNITE-6984
URL: https://issues.apache.org/jira/browse/IGNITE-6984
Project: Ignite
Issue Typ
44 matches
Mail list logo
