Re: destroy cache holding residual metadata in memory (2.7)

[Denis Magda]

+ dev list

Vladimir, Igniters,

Don't we wipe out the metadata on a cache destroy? Is it an issue or done
on purpose?

--
Denis


On Wed, Oct 31, 2018 at 11:28 AM wt  wrote:

> i am testing code and part of my tests is adding\removing tables. In one of
> the tests i add a table then destroy it and add it again but with an
> additional column. When i try load the table i am getting a data type
> mismatch and it is referring to the previous version of the table
>
> in the work directory there is a folder for the original table but it is
> empty. here is the error i get when trying to flush the loader. If i stop
> and start ignite then adding the table with the new column data type works
> so there is some residual metadata that isn't being cleaned up by
> destroycache of the client.
>
> Apache.Ignite.Core.Binary.BinaryObjectException
>   HResult=0x80131500
>   Message=Binary type has different field types
> [typeName=Tables.csvCurrencyRates, fieldName=id, fieldTypeName1=UUID,
> fieldTypeName2=String]
>   Source=Apache.Ignite.Core
>   StackTrace:
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong(Int32 type,
> Action`1 writeAction)
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOp(Int32 type,
> Action`1 action)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.FinishMarshal(BinaryWriter
> writer)
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong(Int32 type,
> Action`1 writeAction)
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOp(Int32 type,
> Action`1 action)
>at Apache.Ignite.Core.Impl.Datastream.DataStreamerImpl`2.Update(Action`1
> action)
>at
>
> Apache.Ignite.Core.Impl.Datastream.DataStreamerBatch`2.Send(DataStreamerImpl`2
> ldr, Int32 plc)
>at
>
> Apache.Ignite.Core.Impl.Datastream.DataStreamerImpl`2.Flush0(DataStreamerBatch`2
> curBatch, Boolean wait, Int32 plc)
>at Apache.Ignite.Core.Impl.Datastream.DataStreamerImpl`2.Flush()
>at ClusterTool.classes.DbProviderCSV.StreamCsvData(List`1 headers,
> String
> tablename, ICsvLine[] lines, Object _class, Type type, IIgnite
> igniteclient,
> Boolean hashashid, CsvNewId csvid) in
> C:\temp\IgniteTool\ClusterTool\classes\DbProviderCSV.cs:line 236
>at ClusterTool.classes.DbProviderCSV.LoadFromCsvFiles(String tablename)
> in C:\temp\IgniteTool\ClusterTool\classes\DbProviderCSV.cs:line 104
>at ClusterTool.DataLoaderForm.<>c__DisplayClass7_0.b__0() in
> C:\temp\IgniteTool\ClusterTool\DataLoaderForm.cs:line 94
>at System.Threading.ExecutionContext.RunInternal(ExecutionContext
> executionContext, ContextCallback callback, Object state, Boolean
> preserveSyncCtx)
>at System.Threading.ExecutionContext.Run(ExecutionContext
> executionContext, ContextCallback callback, Object state, Boolean
> preserveSyncCtx)
>at System.Threading.ExecutionContext.Run(ExecutionContext
> executionContext, ContextCallback callback, Object state)
>at System.Threading.ThreadHelper.ThreadStart()
>
> Inner Exception 1:
> JavaException: class org.apache.ignite.binary.BinaryObjectException: Binary
> type has different field types [typeName=Tables.csvCurrencyRates,
> fieldName=id, fieldTypeName1=UUID, fieldTypeName2=String]
> at
>
> org.apache.ignite.internal.binary.BinaryUtils.mergeMetadata(BinaryUtils.java:1047)
> at
>
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:480)
> at
>
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:207)
> at
>
> org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1332)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformContextImpl.processMetadata(PlatformContextImpl.java:336)
> at
>
> org.apache.ignite.internal.processors.platform.binary.PlatformBinaryProcessor.processInStreamOutLong(PlatformBinaryProcessor.java:70)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.processInStreamOutLong(PlatformAbstractTarget.java:87)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

[MTCGA]: new failures in builds [2226328] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New test failure in master 
DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1739950558570586458=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - pmgheap.sbt 
http://ci.ignite.apache.org/viewModification.html?modId=837493=false
 - pmgheap.sbt 
http://ci.ignite.apache.org/viewModification.html?modId=837487=false
 - stanlukyanov 
http://ci.ignite.apache.org/viewModification.html?modId=837479=false
 - klaster1 
http://ci.ignite.apache.org/viewModification.html?modId=837473=false

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 01:43:30 03-11-2018 

Re: Partition Loss Policies issues

[Denis Magda]

Hi Stan,

Thanks for the extensive analysis. Alex G. could you please step in and
share your thoughts. Seems it's time to revisit IEP-4 and prioritize the
gaps.

--
Denis

On Wed, Oct 31, 2018 at 7:56 AM Stanislav Lukyanov 
wrote:

> Hi Igniters,
>
> I've been looking into various scenarios of Partition Loss Policies usage
> recently,
> and found a number of issues in the current implementation.
>
> I'll start with an overview, but if you'd like to dive to a proposal I
> have right now then please
> feel free to scroll down to TLDR.
>
> The list of issues is below:
> https://issues.apache.org/jira/browse/IGNITE-10041: Partition loss
> policies work incorrectly with BLT
> https://issues.apache.org/jira/browse/IGNITE-10043: Lost partitions list
> is reset when only one server is alive in the cluster
> https://issues.apache.org/jira/browse/IGNITE-9841: SQL doesn't take lost
> partitions into account when persistence is enabled
> https://issues.apache.org/jira/browse/IGNITE-10057: SQL queries hang
> during rebalance if there are LOST partitions
> https://issues.apache.org/jira/browse/IGNITE-9902: ScanQuery doesn't take
> lost partitions into account
> https://issues.apache.org/jira/browse/IGNITE-10059: Local scan query
> against LOST partition fails
> https://issues.apache.org/jira/browse/IGNITE-10044: LOST partition is
> marked as OWNING after the owner rejoins with existing persistent data
> https://issues.apache.org/jira/browse/IGNITE-10058: resetLostPartitions()
> leaves an additional copy of a partition in the cluster
>
> I'm sure this is not a complete list, but this is what I could find by
> tackling how queries and
> persistence interact with current handling of partition loss.
>
> It seems that the issues - from this list and some other fixed recently -
> can be split into three categories
> - corner case bugs - there are always some, and we can fix them as they
> show up
> - handling of lost partitions by different APIs - while JCache API handles
> lost partitions fine,
> SQL and Scan queries have known issues; other APIs, such different types
> of queries, DataStreamer,
> etc probably need to have more testing
> - Partition Loss Policices + BLT (
> https://issues.apache.org/jira/browse/IGNITE-10041) - BLT seems
> to be fundametally conflicting with the pre-existing semantics of
> partition loss
>
> While the former two categories can be solved case-by-case, the last one
> needs a wider design effort.
> We need to reimagine our partition loss semantics for BLT, and change
> behavior accordingly.
> For now, most of the features don't really work for a cache with BLT, with
> only READ_WRITE_SAFE and
> READ_ONLY_SAFE working correctly (good thing - these two are the most
> useful policies anyway).
>
> TLDR: we have issues with partition loss policices, and the largest one is
> that BLT semantics
> conflict with most partition lost policices, and we need to address this
> somehow.
>
> What I suggest to do right now:
> 1. Deny the configurations that don't work - e.g. just throw an exception
> if a cache starts
> with BLT and PartitionLossPolicy.IGNORE or others.
> 2. Change default PartitionLossPolicy to READ_WRITE_SAFE *for persistent
> caches only*.
> This is what effectively in place for the persistent caches already (since
> IGNORE semantics are
> not supported), so this shouldn't bring a lot of compatibility issues.
>
> I believe doing this will at least help us to protect the users from
> unexpected/inconsistent behavior.
> Actual design changes can be done later, e.g. as a part of IEP 4 Phase 2/3.
>
> WDYT?
>
> Thanks,
> Stan
>
>

[GitHub] ignite pull request #5250: IGNITE-10134 fix bug in --cache list --config com...

[antonovsergey93]

GitHub user antonovsergey93 opened a pull request:

https://github.com/apache/ignite/pull/5250

IGNITE-10134 fix bug in --cache list --config command.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10134

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5250.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5250


commit a5510150fd0ecb2a0b7d7b3837c0b77ed6b95daa
Author: Sergey Antonov 
Date:   2018-11-02T20:44:39Z

IGNITE-10134 Fix bug in reducing result on multinode execution.

commit 5363c47f670cb6b9dc659130cf67d00d9282465c
Author: Sergey Antonov 
Date:   2018-11-02T20:45:32Z

IGNITE-10134 Code was reformatted.




---

[jira] [Created] (IGNITE-10137) [TC Bot] Add button 'Expand all' on 'PR failures' page

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10137:


 Summary: [TC Bot] Add button 'Expand all' on 'PR failures' page
 Key: IGNITE-10137
 URL: https://issues.apache.org/jira/browse/IGNITE-10137
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin


Add button 'Expand all' on '[PR failures|http://localhost:8080/prs.html]' page. 
The button should show additional information for all available lines.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Abbreviation code-style requirement.

[Dmitriy Pavlov]

Hi Vyacheslav,

I'm sorry I almost gave up with this donation

http://apache-ignite-developers.2346864.n4.nabble.com/Re-Place-Ignite-Abbrev-Plugin-to-ASF-Ignite-supplementary-git-repo-tp32745p32764.html
because
we need someone to sign a software grant agreement, but there were several
people who contributed to the plugin.

Some of the authors are not active contributors anymore. So I've stuck with
finding a way how to donate.

Sincerely,
Dmitriy Pavlov

пт, 2 нояб. 2018 г. в 21:24, Vyacheslav Daradur :

> I've double checked, we are really able to use IDEA inspection's to
> inspect abbreviations by inspection's structure search and replace
> templates.
> It rather not intuitive and requires complex regex patterns.
>
> Also, at first sight, it shouldn't be difficult to work with the
> project's local properties from the plugin.
>
> On Fri, Nov 2, 2018 at 2:32 PM Vyacheslav Daradur 
> wrote:
> >
> > I like your idea about auto updates.
> >
> > In this case, abbr-plugin should be improved to check and download
> > updates from external URI or local repo.
> > Looks like it could be implemented using Intellij's SDK virtual file [1].
> >
> > But as I can see that abbreviations list update is the very rare case,
> > therefore I'm not sure that we really need to do it.
> >
> > Also, I have another idea we can try to use IDEA inspections and it's
> > naming conventions rules.
> > IDEA inspections are under the project's git already.
> >
> > [1]
> https://www.jetbrains.org/intellij/sdk/docs/basics/architectural_overview/virtual_file.html
> > On Fri, Nov 2, 2018 at 1:47 PM Yakov Zhdanov 
> wrote:
> > >
> > > No, I meant under Ignite's git so any change to resource file arrives
> with
> > > project workspace updates and gets automatically picked up by plugin.
> > >
> > > Makes sense?
> > >
> > > --Yakov
> >
> >
> >
> > --
> > Best Regards, Vyacheslav D.
>
>
>
> --
> Best Regards, Vyacheslav D.
>

Re: Abbreviation code-style requirement.

[Vyacheslav Daradur]

I've double checked, we are really able to use IDEA inspection's to
inspect abbreviations by inspection's structure search and replace
templates.
It rather not intuitive and requires complex regex patterns.

Also, at first sight, it shouldn't be difficult to work with the
project's local properties from the plugin.

On Fri, Nov 2, 2018 at 2:32 PM Vyacheslav Daradur  wrote:
>
> I like your idea about auto updates.
>
> In this case, abbr-plugin should be improved to check and download
> updates from external URI or local repo.
> Looks like it could be implemented using Intellij's SDK virtual file [1].
>
> But as I can see that abbreviations list update is the very rare case,
> therefore I'm not sure that we really need to do it.
>
> Also, I have another idea we can try to use IDEA inspections and it's
> naming conventions rules.
> IDEA inspections are under the project's git already.
>
> [1] 
> https://www.jetbrains.org/intellij/sdk/docs/basics/architectural_overview/virtual_file.html
> On Fri, Nov 2, 2018 at 1:47 PM Yakov Zhdanov  wrote:
> >
> > No, I meant under Ignite's git so any change to resource file arrives with
> > project workspace updates and gets automatically picked up by plugin.
> >
> > Makes sense?
> >
> > --Yakov
>
>
>
> --
> Best Regards, Vyacheslav D.



-- 
Best Regards, Vyacheslav D.

[jira] [Created] (IGNITE-10136) NPE in PartitionUpdateCountersMessage

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-10136:
--

 Summary: NPE in PartitionUpdateCountersMessage
 Key: IGNITE-10136
 URL: https://issues.apache.org/jira/browse/IGNITE-10136
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
 Fix For: 2.7


{noformat}
[14:00:55,950][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint started [checkpointId=9d5398bc-896a-469c-8686-38e2afd517c1, 
startPtr=FileWALPointer [idx=0, fileOff=17828636, len=210609], 
checkpointLockWait=0ms, checkpointLockHoldTime=11ms, 
walCpRecordFsyncDuration=12ms, pages=636, reason='timeout']
[14:00:56,029][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint finished [cpId=9d5398bc-896a-469c-8686-38e2afd517c1, pages=636, 
markPos=FileWALPointer [idx=0, fileOff=17828636, len=210609], 
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=26ms, 
pagesWrite=21ms, fsync=58ms, total=105ms]
[14:00:56,940][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint started [checkpointId=5f46c89e-ead8-4c87-adad-72a50c26bd7c, 
startPtr=FileWALPointer [idx=0, fileOff=20005440, len=210609], 
checkpointLockWait=0ms, checkpointLockHoldTime=8ms, 
walCpRecordFsyncDuration=5ms, pages=474, reason='timeout']
[14:00:57,003][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint finished [cpId=5f46c89e-ead8-4c87-adad-72a50c26bd7c, pages=474, 
markPos=FileWALPointer [idx=0, fileOff=20005440, len=210609], 
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=15ms, 
pagesWrite=10ms, fsync=53ms, total=78ms]
[14:00:57,065][SEVERE][grid-nio-worker-tcp-comm-2-#42][GridDirectParser] Failed 
to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1, 
ordered=false, timeout=0, skipOnTimeout=false, msg=null], 
buf=java.nio.DirectByteBuffer[pos=792 lim=885 cap=32768], 
reader=RollingUpgradeMessageReader [state=StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1, 
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true, 
msg=GridCacheIdMessage [cacheId=0]GridDistributedBaseMessage 
[ver=GridCacheVersion [topVer=152301622, order=1540821647376, nodeOrder=4], 
committedVers=null, rolledbackVers=null, cnt=0, 
super=]GridDistributedTxPrepareRequest [threadId=236, concurrency=PESSIMISTIC, 
isolation=REPEATABLE_READ, writeVer=GridCacheVersion [topVer=152301622, 
order=1540821647377, nodeOrder=4], timeout=0, reads=null, writes=ArrayList [], 
dhtVers=null, txSize=-1, plc=2, txState=null, flags=last, 
super=]GridDhtTxPrepareRequest 
[nearNodeId=3800f476-beb1-46b0-8a39-faa51c91831d, 
futId=f794020c661-cc8749ef-caa5-4f1e-9d89-4a9beff59798, miniId=1, 
topVer=AffinityTopologyVersion [topVer=5, minorTopVer=8], 
invalidateNearEntries={}, nearWrites=null, owned=null, 
nearXidVer=GridCacheVersion [topVer=152301622, order=1540821647374, 
nodeOrder=5], subjId=3800f476-beb1-46b0-8a39-faa51c91831d, taskNameHash=0, 
preloadKeys=null, mvccSnapshot=MvccSnapshotResponse [futId=1, 
crdVer=1540821617885, cntr=16, opCntr=1, txs=null, cleanupVer=15, tracking=0], 
skipCompletedVers=false, super=], mapIt=null, it=null, arrPos=-1, 
keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0, 
uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0, fieldCnt=7, 
readFieldCnt=0, curName=msg, typeRead=true, itemTypeRead=false, 
keyTypeRead=false, valTypeRead=false, curType=21, curItemType=null, 
curKeyType=null, curValType=null, readMsgCls=class 
o.a.i.i.managers.communication.GridIoMessage]StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1, 
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true, 
msg=PartitionUpdateCountersMessage{cacheId=-553317389, size=0, cntrs=}, 
mapIt=null, it=null, arrPos=-1, keyDone=false, readSize=1, readItems=0, prim=0, 
primShift=0, uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, 
lastFinished=true], state=0, fieldCnt=-1, readFieldCnt=0, curName=null, 
typeRead=false, itemTypeRead=false, keyTypeRead=false, valTypeRead=false, 
curType=0, curItemType=null, curKeyType=null, curValType=null, 
readMsgCls=null]StateItem [stream=DirectByteBufferStreamImplV2 
[baseOff=140703933959040, arrOff=-1, tmpArrOff=0, valReadBytes=0, 
tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1, 
keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0, 
uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0, fieldCnt=-1, 
readFieldCnt=0, curName=null, typeRead=false, itemTypeRead=false, 
keyTypeRead=false, valTypeRead=false, curType=0, curItemType=null, 
curKeyType=null, curValType=null, readMsgCls=null]StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1, 
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=false, msg=null, 
mapIt=null, it=null, arrPos=-1, keyDone=false, 

[jira] [Created] (IGNITE-10135) Documentation link to ClusterNodeAttributeAffinityBackupFilter

[David Harvey (JIRA)]

David Harvey created IGNITE-10135:
-

 Summary: Documentation link to 
ClusterNodeAttributeAffinityBackupFilter
 Key: IGNITE-10135
 URL: https://issues.apache.org/jira/browse/IGNITE-10135
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: David Harvey
 Fix For: 2.7


IGNITE-9365 adds ClusterNodeAttributeAffinityBackupFilter to allow "Crash-safe 
Affinity"  
([https://apacheignite.readme.io/docs/affinity-collocation|https://apacheignite.readme.io/docs/affinity-collocation_])
 to be configured from spring.  

The class should have an adequate description of how to set this up, but the 
above section should link to or otherwise flag that such a procedure exist.

[https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.java]

 

Note: the implementation is generic, allowing any node attribute (or 
environment variable) to be configured so that primary and backup's are always 
forced to not be on the same node.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Comittership bar quidance & mailing lists, openness & how large code drops/off-list development are killing the community

[Dmitriy Pavlov]

Hi Igniters,

I would like to share with Apache Ignite community a slightly updated
comittership bar guide. It is a not strict rule, but a recommendation:

https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance

There were no significant changes. PMC agreed to avoid counting messages
and introducing any metric for participation in discussions, but a
candidate still needs to have a good presence and visibility on the dev
list.


I also would like to share several more Apache links related to
committership :

https://community.apache.org/newcommitter.html


https://wiki.apache.org/incubator/DefaultProjectGuidelines

https://community.apache.org/contributors/#contributing-a-project-copdoc

https://www.apache.org/foundation/how-it-works.html#meritocracy

Also, there is the discussion on community developers mailing list to find
out opinions of ASF fellows about the case when a developer is not visible
on the mailing list:

https://lists.apache.org/thread.html/906785eeb03c6a35a65843689f3e23ec75410b0cf36c6779f6b36acd@%3Cdev.community.apache.org%3E

And one more discussion about the impact of large code drops from
commercial companies and their impact on a community, about the importance
of openness:

https://lists.apache.org/thread.html/8d915443bc31a228d747744e2f65d54176608c95dc93efac184f66bc@%3Cdev.community.apache.org%3E

Sincerely,

Dmitriy Pavlov

Re: IGNITE-2.7. New Features

[David Harvey]

IGNITE-9365 Force backups to different AWS availability zones using only
Spring XML

This deserves documentation enhancements:
https://apacheignite.readme.io/docs/affinity-collocation

What is the mechanism for proposing an update for 2.7?


On Fri, Nov 2, 2018 at 6:31 AM Andrey Kuznetsov  wrote:

> Great news!
>
> Future release is about to contain mission critical Ignite workers liveness
> monitoring, introduced in IGNITE-6587.
>
>
> пт, 2 нояб. 2018 г. в 13:23, Nikolay Izhikov :
>
> > Hello, Guys.
> >
> > Good news! We have 2 final tickets for 2.7.
> > So release date is very near!
> >
> > Let's collect new features and improvements of Ignite 2.7 and includes it
> > to release notes and other documents.
> >
> > Can you answer and describe your contributions?
> >
>
>
> --
> Best regards,
>   Andrey Kuznetsov.
>

[jira] [Created] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[ARomantsov (JIRA)]

ARomantsov created IGNITE-10134:
---

 Summary: control.sh --cache list . --config not working on big 
cache setup
 Key: IGNITE-10134
 URL: https://issues.apache.org/jira/browse/IGNITE-10134
 Project: Ignite
  Issue Type: Bug
Reporter: ARomantsov



{code:java}
[17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job results 
due to undeclared user exception 
[task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
err=java.lang.AssertionError]
java.lang.AssertionError
at 
org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
at 
org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
due to undeclared user exception 
[task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
 err=java.lang.AssertionError]
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at 
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
at 
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 

[GitHub] ignite pull request #5249: IGNITE-10133: Switch to per-node TensorFlow worke...

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

https://github.com/apache/ignite/pull/5249

IGNITE-10133: Switch to per-node TensorFlow worker strategy.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10133

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5249.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5249


commit 13962c2c13d1cf945cac90ce003831d0a4a4fd33
Author: Anton Dmitriev 
Date:   2018-11-02T15:20:52Z

IGNITE-10133: Switch to per-node TensorFlow worker strategy.




---

[jira] [Created] (IGNITE-10133) ML: Switch to per-node TensorFlow worker strategy

[Anton Dmitriev (JIRA)]

Anton Dmitriev created IGNITE-10133:
---

 Summary: ML: Switch to per-node TensorFlow worker strategy
 Key: IGNITE-10133
 URL: https://issues.apache.org/jira/browse/IGNITE-10133
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Affects Versions: 2.8
Reporter: Anton Dmitriev
Assignee: Anton Dmitriev
 Fix For: 2.8


Currently we start TensorFlow worker process per every cache partition. In case 
node is equipped by GPU and TensorFlow uses this GPU it acquires all GPU 
memory. If two worker processes try to acquire all GPU memory they will fail.

To eliminate this problem and allow users utilizing GPU during the training we 
need to switch to per-node strategy. It means we need to start one TensorFlow 
worker process per node, not per partition.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5248: IGNITE-9897: ODBC fix for PDO when used with unix...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/5248

IGNITE-9897: ODBC fix for PDO when used with unixODBC



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9897

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5248.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5248


commit 28f4a3a866f0d090baf4b20fa2085e9e58c68cee
Author: Igor Sapego 
Date:   2018-11-02T14:16:37Z

IGNITE-9897: ODBC fix for PDO when used with unixODBC




---

[GitHub] zzzadruga opened a new pull request #58: IGNITE-10125 Uniform style for buttons

[GitBox]

zzzadruga opened a new pull request #58: IGNITE-10125 Uniform style for buttons
URL: https://github.com/apache/ignite-teamcity-bot/pull/58
 
 
   Uniform style for buttons: "Inspect" from PR selection, "Show graph" from 
Master Trends, "More >>" from PR Failures


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (IGNITE-10132) TC: the thin client suites (PHP, nodejs etc) must contains log of the Ignite node

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-10132:
-

 Summary: TC: the thin client suites (PHP, nodejs etc) must 
contains log of the Ignite node
 Key: IGNITE-10132
 URL: https://issues.apache.org/jira/browse/IGNITE-10132
 Project: Ignite
  Issue Type: Task
  Components: thin client
Reporter: Taras Ledkov
Assignee: Peter Ivanov


It will be great to add the Ignite node's log to a build artifact for thin 
clients tests suites.
It makes troubleshooting easier.
If there is another way to publish node's log that is more convenient please 
use it (I know nothing about it).

Test suites:
- Thin client: Node.js;
- Thin client: PHP;
- Thin client: Python.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5247: IGNITE-10109 MVCC TX: data become inconsistent af...

[gvvinblade]

GitHub user gvvinblade opened a pull request:

https://github.com/apache/ignite/pull/5247

IGNITE-10109 MVCC TX: data become inconsistent after several updates



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10109

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5247.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5247


commit bc9d4dbe96bc9de3cf80aaa58a3be8536aed66d5
Author: Igor Seliverstov 
Date:   2018-11-02T14:05:59Z

IGNITE-10109 fixed wrong keys postprocessing on backup nodes




---

[GitHub] ignite pull request #5246: TC test

[xtern]

GitHub user xtern opened a pull request:

https://github.com/apache/ignite/pull/5246

TC test



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/xtern/ignite IGNITE-9858-TC

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5246.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5246


commit 59681c1049256b4a8f815c3bdfb4889678121cb8
Author: pereslegin-pa 
Date:   2018-11-02T13:55:25Z

TC test




---

[jira] [Created] (IGNITE-10131) Wrong processing of loaded from store keys on backup nodes.

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-10131:
-

 Summary: Wrong processing of loaded from store keys on backup 
nodes.
 Key: IGNITE-10131
 URL: https://issues.apache.org/jira/browse/IGNITE-10131
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Igor Seliverstov


In scope of IGNITE-7086 was added a closure, which puts a key value pair in 
case the node is a local backup and readThrough is enabled and the key is 
absent on the node (in other words the key was read from store on a primary 
node).

Currently this closure post-processes each call even in case 3rd party 
persistence store is disabled for the cache because readThrough flag is 
obtained by inversion of skipStore flag of operation context (which is false by 
default).

see {{CU.createBackupPostProcessingClosure(..)}} for details



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5245: IGNITE-10052: Restart node during TX causes vacuu...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

https://github.com/apache/ignite/pull/5245

IGNITE-10052: Restart node during TX causes vacuum error.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10052

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5245.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5245


commit 363b5707b21a4d07d4b45845ffe3172fd8335c05
Author: Andrey V. Mashenkov 
Date:   2018-10-31T15:29:30Z

IGNITE-10052: Introduce MvccDataRecord - WAL record for mvcc entries.

commit 0f1de5bc46d4ca9ccd1e34b6c0e1104f3d1a21d9
Author: Andrey V. Mashenkov 
Date:   2018-11-01T10:09:03Z

IGNITE-10052: Introduce MvccDataRecord - WAL record for mvcc entries.

commit 7ddbe1375cfad152712da9a1a5b073c52a082332
Author: Andrey V. Mashenkov 
Date:   2018-11-01T10:13:51Z

IGNITE-10052: Fix orphan rows handling.

Grid restart case:
Treat rows created by unknown (non-active and non-finished) TX with on old 
coordinator version as aborted TX.

Backup node restart case:
Treat non-primary rows created by unknown (non-active and non-finished) TX 
with older version, but same coordinator as aborted TX.

commit c6928c32c80ea52cd68c76c29cceef585b8ed048
Author: Andrey V. Mashenkov 
Date:   2018-11-01T17:38:50Z

IGNITE-10052: Fix rebalanced entries.

commit f826a1db1919c634707dc64375510e008962e46f
Author: Andrey V. Mashenkov 
Date:   2018-11-01T17:38:50Z

IGNITE-10052: Fix rebalanced entries.

commit dbdc280e9414e2ea33f73f904239738bb4e713ce
Author: Andrey V. Mashenkov 
Date:   2018-11-01T17:53:13Z

Merge remote-tracking branch 'origin/ignite-10052' into ignite-10052

commit 862093ab1b5e640abdcd59649b3b52efb70cb466
Author: Andrey V. Mashenkov 
Date:   2018-11-02T09:11:01Z

IGNITE-10052: Fix rebalanced entries.

commit 8007faa41c2db083470a547d28aed5be0bce4b70
Author: Andrey V. Mashenkov 
Date:   2018-11-02T11:26:32Z

IGNITE-10052: Fix recovery from WAL.




---

[GitHub] ignite pull request #5244: Ignite-2.4.12-wd

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

https://github.com/apache/ignite/pull/5244

Ignite-2.4.12-wd



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.12-wd

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5244.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5244


commit a58bc16543e72dfc3a2b97c50506cd532d4d9dee
Author: devozerov 
Date:   2018-03-29T12:21:46Z

IGNITE-7421: Reverted invalid server-side authentication.

commit e7ec84a17c5999441f1731aad64f540fd2eda279
Author: devozerov 
Date:   2018-03-29T12:23:26Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 188279848a75d6458b9441d65917fb628834355e
Author: devozerov 
Date:   2018-03-30T09:04:33Z

IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations. 
This closes #3496.

commit b4320072ca75e5b11bbeeb033c2f60f31f4855f9
Author: devozerov 
Date:   2018-03-30T09:18:10Z

Merge remote-tracking branch 'upstream/ignite-2.4.4' into ignite-2.4.4

commit b0de9d14caaf2bfc91c4f8283b0806c354ef7b73
Author: Alexey Goncharuk 
Date:   2018-03-30T14:40:28Z

IGNITE-8053 Make sure local partitions collection does not change

commit 7214eff5b5d8102ba32a7b7bf7597ac5a4b04eee
Author: Alexey Kukushkin 
Date:   2018-04-02T08:08:05Z

IGNITE-8076: Java Thin Client: authentication. This closes #3720.

commit 2c0e269fe7793bb70d1be28d2052f1394b96f2b1
Author: devozerov 
Date:   2018-04-02T08:09:17Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit cb89494be26be1b0e397e06f7eaeb6419aec1828
Author: Alexey Kuznetsov 
Date:   2018-03-02T09:35:26Z

IGNITE-7803 REST: Implemented possibility to get values from cache inserted 
via API or SQL.

(cherry picked from commit a84018b)

commit 149802a3be82ba1f88770dbff75d74b892bb0a94
Author: Alexey Kuznetsov 
Date:   2018-03-07T17:17:20Z

IGNITE-7803 Fixed regression in tests.

(cherry picked from commit 90c0af8)

commit 5b5571adc7282a29cdecd8ab2e945a446ea709fc
Author: Alexey Kuznetsov 
Date:   2018-03-23T02:55:13Z

IGNITE-8002 REST: Added support of new authentication via new API.

(cherry picked from commit 921f0cf)

commit 128fdfcd874286f4a358546c0f43b6ef082a064b
Author: devozerov 
Date:   2018-04-02T10:11:16Z

IGNITE-7884: Sample data set for JDBC. This closes #3702.

commit 247a9ef5a68de198106a866b277f1bee596c3633
Author: devozerov 
Date:   2018-04-02T10:16:00Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 3949df02128e3003c409e0169ad0c80948ba134c
Author: Aleksey Plekhanov 
Date:   2018-02-13T13:43:49Z

IGNITE-5265 Eviction Rate memory metric to be implemented

Signed-off-by: Anton Vinogradov 

commit 7bc6c1ad3bacaf5e354d2710931eb398c346c06c
Author: Tim Onyschak 
Date:   2018-03-31T12:58:25Z

IGNITE-7090 Semaphore Stuck when no acquirers to assign permit - Fixes 
#3443.

Signed-off-by: dspavlov 

(cherry picked from commit 3fc5d57)

commit c854ad86f4c64260171085c8c7cce97ba1ad2530
Author: Pavel Kovalenko 
Date:   2018-02-22T09:02:31Z

IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin test. - Fixes #3540.

Signed-off-by: Alexey Goncharuk 

commit b2e94b36bddebbf7b3ff40631e099939d16926d2
Author: Alexey Goncharuk 
Date:   2018-02-13T15:53:23Z

IGNITE-7692 Corrected test to not fail when SQL is executed on backup

commit 852425d4170ed1871c79f5ac26bfb3d03cc36a6f
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 
(cherry picked from commit e491f10)

commit 42f529f0a04ce22786bb4a23032a64f93e214233
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit b5f180838246f895d36846ea707790c1ff7fe70a
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

(cherry picked from commit 3a4f23b)

commit 1ce8e1a8fd48469073592e2fb77e2881a168a219
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

(cherry picked from commit d70477b)

commit 840e193b3e604e8b0d90be5fac16cf11d8c832e6
Author: Ilya Lantukh 
Date:   2018-04-06T10:49:10Z

ignite-8087 : Backported ignite-8018.

(cherry picked from commit 175edf3)

commit 94e857c94ce5e7998fc39e38deee69f389ddbc5b
Author: 

[GitHub] ignite pull request #5243: IGNITE-10080

[xtern]

GitHub user xtern opened a pull request:

https://github.com/apache/ignite/pull/5243

IGNITE-10080



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/xtern/ignite IGNITE-10080

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5243.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5243


commit 3f4d7a2cd76042f7562de2f902575dbd5337d5f9
Author: pereslegin-pa 
Date:   2018-10-31T09:20:23Z

IGNITE-10080 TxOptimisticPrepareOnUnstableTopologyTest decrese startup 
delay.

commit 716d8a85290e59abf4853eadab6e270e7cec2879
Author: pereslegin-pa 
Date:   2018-10-31T09:21:30Z

IGNITE-10080 CacheExchangeMergeTest#concurrentStart decrese iterations 
count.

commit e054cfd263082c5bd65a48cd53923e99dc7a7761
Author: pereslegin-pa 
Date:   2018-11-02T12:04:45Z

IGNITE-10080 Suspend/resume test optimization

commit ae3605b59f2a29bc38209ae43d7766b94a276b01
Author: pereslegin-pa 
Date:   2018-11-02T12:43:02Z

IGNITE-10080 TxRollbackAsyncTest decrese tx count.

commit 497e1fe1322aba20b62d0711205fd1d128a0c4f2
Author: pereslegin-pa 
Date:   2018-11-02T12:51:23Z

IGNITE-10080 Codestyle.




---

[jira] [Created] (IGNITE-10130) Add option to API for disable triggering cache interceptor.

[Sergey Antonov (JIRA)]

Sergey Antonov created IGNITE-10130:
---

 Summary: Add option to API for disable triggering cache 
interceptor.
 Key: IGNITE-10130
 URL: https://issues.apache.org/jira/browse/IGNITE-10130
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5242: IGNITE-10129: Disable Vacuum warnings if mvcc is ...

[rkondakov]

GitHub user rkondakov opened a pull request:

https://github.com/apache/ignite/pull/5242

IGNITE-10129: Disable Vacuum warnings if mvcc is not enabled.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10129

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5242.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5242


commit 25a8625438204bccf988ed1e3f39ee54c3c164c1
Author: rkondakov 
Date:   2018-11-02T12:09:48Z

IGNITE-10129: Disable Vacuum warnings if mvcc is not enabled.




---

[GitHub] ignite pull request #5238: IGNITE-6856

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5238


---

[GitHub] ignite pull request #5237: IGNITE-10123 Disable events in IgniteLogicalRecov...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5237


---

[GitHub] ignite pull request #5240: IGNITE-10128 Race in read\write cache configurati...

[zstan]

Github user zstan closed the pull request at:

https://github.com/apache/ignite/pull/5240


---

[GitHub] ignite pull request #5241: IGNITE-10128 Race in read\write cache configurati...

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/5241

IGNITE-10128 Race in read\write cache configurations.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10128

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5241.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5241


commit e21cecdfc0df7651175792b73b8814b8f83ed402
Author: zstan 
Date:   2018-11-02T10:02:55Z

IGNITE-10128 Race in read\write cache configurations.




---

[GitHub] ignite pull request #5240: GG-14379 Race in read\write cache configurations.

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/5240

GG-14379 Race in read\write cache configurations.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10128

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5240.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5240


commit 59a82f75eb4e2c52d54b1b8d462ec462235cc381
Author: zstan 
Date:   2018-11-02T10:02:55Z

GG-14379 Race in read\write cache configurations.




---

Re: Abbreviation code-style requirement.

[Vyacheslav Daradur]

I like your idea about auto updates.

In this case, abbr-plugin should be improved to check and download
updates from external URI or local repo.
Looks like it could be implemented using Intellij's SDK virtual file [1].

But as I can see that abbreviations list update is the very rare case,
therefore I'm not sure that we really need to do it.

Also, I have another idea we can try to use IDEA inspections and it's
naming conventions rules.
IDEA inspections are under the project's git already.

[1] 
https://www.jetbrains.org/intellij/sdk/docs/basics/architectural_overview/virtual_file.html
On Fri, Nov 2, 2018 at 1:47 PM Yakov Zhdanov  wrote:
>
> No, I meant under Ignite's git so any change to resource file arrives with
> project workspace updates and gets automatically picked up by plugin.
>
> Makes sense?
>
> --Yakov



-- 
Best Regards, Vyacheslav D.

[jira] [Created] (IGNITE-10129) MVCC TX: do not log Vacuum warnings if mvcc is not enabled

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-10129:
-

 Summary: MVCC TX: do not log Vacuum warnings if mvcc is not enabled
 Key: IGNITE-10129
 URL: https://issues.apache.org/jira/browse/IGNITE-10129
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Igor Seliverstov
 Fix For: 2.7


currently we can see warnings like : 
{{[10:18:48,741][INFO][exchange-worker-#64][MvccProcessorImpl] Attempting to 
stop inactive vacuum.}} on node stop.

Such warnings should not appear in case MVCC is disabled (there is no MVCC 
caches).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10128) IO race during read\write cache configurations.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-10128:
---

 Summary: IO race during read\write cache configurations.
 Key: IGNITE-10128
 URL: https://issues.apache.org/jira/browse/IGNITE-10128
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.6
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
 Fix For: 2.8


During grid usage, found problem below. I tries simultaneously start several 
nodes and call *activate* on ** each node.
{code:java}
[15:38:25,186][INFO][exchange-worker-#63][FileWriteAheadLogManager] Resuming 
logging to WAL segment 
[file=/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/wal/node2/.wal,
 offset=0, ver=2]
[15:38:25,210][INFO][exchange-worker-#63][GridSnapshotAwareClusterStateProcessorImpl]
 Writing BaselineTopology[id=0]
[15:38:25,225][INFO][exchange-worker-#63][GridCacheDatabaseSharedManager] 
Resume logging performed in 41 ms.
[15:38:25,252][INFO][exchange-worker-#63][CacheAffinitySharedManager] Updating 
caches registry performed in 27 ms.
[15:38:25,743][SEVERE][sys-#70][] Critical system error detected. Will be 
handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
[tryStop=false, timeout=0, super=AbstractFailureHandler 
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED]]], 
failureCtx=FailureContext [type=CRITICAL_ERROR, 
err=java.nio.file.NoSuchFileException: 
/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
Critical system error detected. Will be handled accordingly to configured 
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
err=java.nio.file.NoSuchFileException: 
/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
java.nio.file.NoSuchFileException: 
/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
at java.nio.file.Files.move(Files.java:1395)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.storeCacheData(FilePageStoreManager.java:390)
at 
org.apache.ignite.internal.processors.cache.CachesRegistry.lambda$persistCacheConfigurations$4(CachesRegistry.java:303)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6875)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5196: IGNITE-9972 Deleted entries remain in local parti...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5196


---

[jira] [Created] (IGNITE-10127) GridCacheRebalancingSyncSelfTest ignores check result

[Ryabov Dmitrii (JIRA)]

Ryabov Dmitrii created IGNITE-10127:
---

 Summary: GridCacheRebalancingSyncSelfTest ignores check result
 Key: IGNITE-10127
 URL: https://issues.apache.org/jira/browse/IGNITE-10127
 Project: Ignite
  Issue Type: Test
Reporter: Ryabov Dmitrii
 Fix For: 2.8


{{checkSupplyContextMapIsEmpty()}} method checks that map is empty, but ignores 
result of this check.

{code:java}
GridTestUtils.waitForCondition(new PA() {
@Override public boolean apply() {
synchronized (map) {
return map.isEmpty();
}
}
}, 15_000);
{code}

We should check that {{waitForCondition()}} returns true to be sure that map is 
cleared.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Abbreviation code-style requirement.

[Yakov Zhdanov]

No, I meant under Ignite's git so any change to resource file arrives with
project workspace updates and gets automatically picked up by plugin.

Makes sense?

--Yakov

Re: IGNITE-2.7. New Features

[Andrey Kuznetsov]

Great news!

Future release is about to contain mission critical Ignite workers liveness
monitoring, introduced in IGNITE-6587.


пт, 2 нояб. 2018 г. в 13:23, Nikolay Izhikov :

> Hello, Guys.
>
> Good news! We have 2 final tickets for 2.7.
> So release date is very near!
>
> Let's collect new features and improvements of Ignite 2.7 and includes it
> to release notes and other documents.
>
> Can you answer and describe your contributions?
>


-- 
Best regards,
  Andrey Kuznetsov.

IGNITE-2.7. New Features

[Nikolay Izhikov]

Hello, Guys.

Good news! We have 2 final tickets for 2.7.
So release date is very near!

Let's collect new features and improvements of Ignite 2.7 and includes it to 
release notes and other documents.

Can you answer and describe your contributions?


signature.asc
Description: This is a digitally signed message part

[GitHub] ignite pull request #4689: IGNITE-8331 Add Decimal precision and scale const...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4689


---

Re: Problem with reading incomplete payload - IGNITE-7153

[Michael Fong]

Hi Yakov,

Thanks so much for your analysis.

Parser expects chunks to be complete and has all the data to read entire
> message, but this is not guaranteed and single message can arrive in
> several chunks.

This is indeed the the assumption to my implementation. I have not come up
a another parsing algorithm to handle this rainy day case. Perhaps, it
would require more refactoring on existing code. In addition, I might need
to check how Redis dev implements the parser state machine.

I would be interested to see how current implementation (based on
2.6/master) behaves if we intentionally split the message into chunks as
you suggested for the reproducer.

Regards,

Michael

On Wed, Oct 31, 2018 at 7:08 PM Yakov Zhdanov  wrote:

> Hi Mike!
>
> Thanks for reproducer. Now I understand the problem. NIO worker reads
> chunks from the network and notifies the parser on data read. Parser
> expects chunks to be complete and has all the data to read entire message,
> but this is not guaranteed and single message can arrive in several chunks.
> Which is demostrated by your test.
>
> The problem is inside GridRedisProtocolParser. We should add ability to
> store the parsing context if we do not have all the data to complete
> message parsing, as it is done, for example in GridBufferedParser. So, it
> is definitely an issue and should be fixed by adding parsing state. I see
> you attempted to do so in PR
> https://github.com/apache/ignite/pull/5044/files. I did not do a formal
> review, so let's ask community to review your patch.
>
> Couple of comments about your reproducer.
>
> 1. Let's dump a proper Redis message bytes sent by Jedis.
> 2. Let's split this dump into 5 chunks and send them with 100 ms delays.
>
> This should fail before fix is applied, and should pass with proper message
> parsed after we have the issue fixed.
>
> Thanks!
>
> --Yakov
>

[GitHub] ignite pull request #5239: IGNITE-10126

[Max-Pudov]

GitHub user Max-Pudov opened a pull request:

https://github.com/apache/ignite/pull/5239

IGNITE-10126



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10126

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5239.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5239


commit fa0b52b013cdbbc996bea2477528a4ebb6f0db55
Author: Max-Pudov 
Date:   2018-11-02T10:14:16Z

IGNITE-10126 Update Apache Storm due to vulnerability issue CVE-2018-1331




---

Re: Abbreviation code-style requirement.

[Vyacheslav Daradur]

Yes, it's under git already in Dmitry Pavlov's GitHub account [1].
AFAIK donation to ASF is in progress [2]. (Dmitry Pavlov, please,
correct me if I'm wrong)

[1] 
https://github.com/dspavlov/ignite-abbrev-plugin/blob/master/src/abbreviation.properties
[2] 
http://apache-ignite-developers.2346864.n4.nabble.com/Re-Place-Ignite-Abbrev-Plugin-to-ASF-Ignite-supplementary-git-repo-tp32745p32764.html
On Fri, Nov 2, 2018 at 12:30 PM Yakov Zhdanov  wrote:
>
> Agree with Vyacheslav - reviewers can either fix the issues or ask to fix
> them. After several PRs new contributors will get used with project
> requirements.
>
> As far as one time contributions, they are usually pretty simple and should
> not take any significant time to fix. If one time contirbutor returns with
> more contributions then he or she should account all the changes made on
> review and, again, come to a point where all project requirements are
> staisfied.
>
> Btw, Vyacheslav, can we have abbreviations.properties in the project under
> git and have plugin use it?
>
> --Yakov



-- 
Best Regards, Vyacheslav D.

[GitHub] ignite pull request #4632: IGNITE-9312 Remove unnecessary @SuppressWarnings ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4632


---

[GitHub] ignite pull request #5238: IGNITE-6856

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/5238

IGNITE-6856



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6856

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5238.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5238


commit f9befc35c25a638c6e303838320db20844b7de97
Author: devozerov 
Date:   2018-11-01T11:35:46Z

WIP.

commit 07a121cdbb11b0cd7c6cd707a3781aae67d731ea
Author: devozerov 
Date:   2018-11-01T13:12:23Z

Base test works.

commit 32012593dc9b415df6e4e4d50cd134f4aca6a542
Author: devozerov 
Date:   2018-11-02T09:12:13Z

Merge branch 'master' into ignite-6856




---

Re: Abbreviation code-style requirement.

[Yakov Zhdanov]

Agree with Vyacheslav - reviewers can either fix the issues or ask to fix
them. After several PRs new contributors will get used with project
requirements.

As far as one time contributions, they are usually pretty simple and should
not take any significant time to fix. If one time contirbutor returns with
more contributions then he or she should account all the changes made on
review and, again, come to a point where all project requirements are
staisfied.

Btw, Vyacheslav, can we have abbreviations.properties in the project under
git and have plugin use it?

--Yakov

Re: Ignite documentation process

[Yakov Zhdanov]

Denis, there were email notifications from wiki on corresponding edits =)

--Yakov

[GitHub] ignite pull request #5083: 9986 flakiness

[SomeFire]

Github user SomeFire closed the pull request at:

https://github.com/apache/ignite/pull/5083


---

[jira] [Created] (IGNITE-10125) [TC Bot] Uniform style for buttons

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10125:


 Summary: [TC Bot] Uniform style for buttons
 Key: IGNITE-10125
 URL: https://issues.apache.org/jira/browse/IGNITE-10125
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin


Uniform style for buttons: "Inspect" from [PR 
selection|mtcga.gridgain.com/prs.html], "Show graph" from [Master 
Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10124) [TC Bot] Redesign and refactor UI

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10124:


 Summary: [TC Bot] Redesign and refactor UI
 Key: IGNITE-10124
 URL: https://issues.apache.org/jira/browse/IGNITE-10124
 Project: Ignite
  Issue Type: Task
Reporter: Nikolai Kulagin


We must make the TC bot more user-friendly, make UI more intuitive and simple



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5069: IGNITE-9841: SQL doesn't take lost partitions int...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5069


---

[GitHub] ignite pull request #5237: IGNITE-10123 Disable events in IgniteLogicalRecov...

[agoncharuk]

GitHub user agoncharuk opened a pull request:

https://github.com/apache/ignite/pull/5237

IGNITE-10123 Disable events in IgniteLogicalRecoveryTest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10123

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5237.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5237


commit 88dcc8a100a6f2b4dc995a1e28bebe67b0a2edbf
Author: Alexey Goncharuk 
Date:   2018-11-02T08:46:00Z

IGNITE-10123 Disable events in IgniteLogicalRecoveryTest




---

Re: Abbreviation code-style requirement.

[Vyacheslav Daradur]

I've faced such practice.

Very first my contribution, when I have not been familiar with style
guidelines, Yakov Zhdanov kindly fixed code style issues himself.

I think it depends on a reviewer:
- in one case reviewer can fix issues independently
- in other case ask a contributor to solve them

On Fri, Nov 2, 2018 at 11:31 AM Павлухин Иван  wrote:
>
> Andrey, Dmitry,
>
> If we have a practice of formatting a code before merge by committer
> then it is already much better. But do we have such a practice?
>
> As for me personally. I have not felt much discomfort with abbreviations.
> I already used them extensively. Even "cctx", "ccfg" which are not
> mandatory today.
>
> пт, 2 нояб. 2018 г. в 10:58, Dmitriy Pavlov :
>
> > Hi Ivan,
> >
> > provided that committer has installed ignite-abbrev-plugin it is not a big
> > deal to abbreviate common words before a merge.
> >
> > I had the same impression about abbreviations when I came to the project:
> > "all other development world tends to expose as much meaning as it is
> > humanly possible in code, but Ignite has abbreviations seemed to hide this
> > meaning".  But later I've used to most common abbreviations, like ctx, and
> > I always understand that this implies context.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 2 нояб. 2018 г. в 10:21, Andrey Kuznetsov :
> >
> > > Ivan, I agree with you: some our code style rules are really uncommon.
> > >
> > > As for one-time contributions, if somebody decides to make a contribution
> > > to some project, it's ok to adopt that project rules. Moreover, reviewing
> > > committer can silently fix minor code style issues himself upon merge.
> > >
> > > пт, 2 нояб. 2018 г. в 10:08, Павлухин Иван :
> > >
> > > > Andrey, Yakov,
> > > >
> > > > Actually my concert is more about one-time contributions. I imagine
> > > > the following. Someone finds a bug a decides to contribute a fix.
> > > > I think it is quite common scenario in Open Source.
> > > > He creates a PR and awaits a review. I think that a smooth and fast
> > > > review process will encourage for new contributions. But if the review
> > > > process is not such the contributor can simply give up.
> > > >
> > > > P.S. In my mind there are quite uncommon code style rules in Ignite
> > > > project. But it is definitely not for that topic. I imagine some "New
> > > > Contributor Survey".
> > > >
> > > > чт, 1 нояб. 2018 г. в 18:28, Yakov Zhdanov :
> > > >
> > > > > Ivan I removed "lic" from the list. Thanks for catch!
> > > > >
> > > > > Agree with Andrey. After several code reviews newcomers will get used
> > > to
> > > > > abbreviations.
> > > > >
> > > > > Andrey, try searching for "fut" and make sure to have "Word" checked.
> > > You
> > > > > will see plenty of usages. "f" is also ok for future in case it does
> > > not
> > > > > bring confusion and does not hurt readability.
> > > > >
> > > > > Let's keep using abbreviations and treat them as mandatory
> > requirement.
> > > > > This is important for keeping our codebase consistent and tidy.
> > > > >
> > > > > --Yakov
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > >   Andrey Kuznetsov.
> > >
> >
>
>
> --
> Best regards,
> Ivan Pavlukhin



-- 
Best Regards, Vyacheslav D.

[jira] [Created] (IGNITE-10123) Intermittent OOME errors in PDS indexing tests

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-10123:
-

 Summary: Intermittent OOME errors in PDS indexing tests
 Key: IGNITE-10123
 URL: https://issues.apache.org/jira/browse/IGNITE-10123
 Project: Ignite
  Issue Type: Test
Reporter: Alexey Goncharuk
 Fix For: 2.8






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5236: Ignite 2.5.1 p150

[voropava]

GitHub user voropava opened a pull request:

https://github.com/apache/ignite/pull/5236

Ignite 2.5.1 p150



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p150

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5236.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5236


commit afbad007cc7dd1d2795ab3e04ffdb580763ca99d
Author: Dmitriy Sorokin 
Date:   2018-07-04T10:16:21Z

IGNITE-8910 PagesList.takeEmptyPage may fail with AssertionError: type = 1 
- Fixes #4294.

Signed-off-by: Ivan Rakov 

(cherry picked from commit e6f44ad)

commit 84ce1a3452fdd0195c3f7c291141a54ced76b125
Author: Alexey Stelmak 
Date:   2018-07-04T14:15:28Z

IGNITE-8780 File I/O operations must be retried if buffer hasn't 
read/written completely

Signed-off-by: Andrey Gura 

commit ab298bc8b61ef176709398f96eb1f17a19e1965a
Author: AMedvedev 
Date:   2018-07-05T10:19:23Z

IGNITE-8737 Improve checkpoint logging information - Fixes #4244.

Signed-off-by: Ivan Rakov 

(cherry-picked from commit#a727a4c7135e57415de0756e8fdc235ba191109a)

commit 6971f3d09bcf67e76efde290154b6c36470b20cb
Author: Pavel Kovalenko 
Date:   2018-07-06T20:00:25Z

IGNITE-8904 Add rebalanceThreadPoolSize to nodes configuration consistency 
check

Signed-off-by: Ivan Rakov 

(cherry picked from commit b490982)
Signed-off-by: Ivan Rakov 

commit 6c0f32fe6fdcc5d0b17388a9e1290371499368ce
Author: vd-pyatkov 
Date:   2018-07-06T15:11:55Z

IGNITE-8754 Node outside of baseline does not start when service configured

Signed-off-by: Andrey Gura 
(cherry picked from commit b1832673eba37919ad33f9d1c42b9b6bfa7e5a34)

commit 6ac7204f1c66e9691504ef7cd25e8d904bdf36c4
Author: vd-pyatkov 
Date:   2018-07-09T17:15:49Z

IGNITE-8898 Renamed command argument '--force' to '--yes' for control.sh

Signed-off-by: Andrey Gura 
(cherry picked from commit 413b4a8a1f905e31e3a8770d2c78ca953d39a60f)

commit d3b140f763433686dbdd3f156edfeec1561df531
Author: devozerov 
Date:   2018-07-04T14:11:00Z

IGNITE-8925: SQL: Limit default number of threads for CREATE INDEX to 4. 
This closes #4301.

(cherry picked from commit 5cc41df7ac33ce4664f7db1c1cf8b3cf33d71cc8)

commit 72848848268c6c0facbd96ebff7ed1f6de10de29
Author: a-polyakov 
Date:   2018-07-06T15:31:23Z

IGNITE-8620 Remove intOrder and loc keys from node info in control.sh --tx 
utility

Signed-off-by: Andrey Gura 
(cherry picked from commit 532dc79a1459befa757849487f7aef2cb8608cee)

commit f9fbf2a5b50ba623599292e4cc1bab8893e698d8
Author: ascherbakoff 
Date:   2018-07-11T14:09:05Z

IGNITE-8942 In some cases grid cannot be deactivated because of hanging CQ 
internal cleanup. - Fixes #4329.

Signed-off-by: Ivan Rakov 

(cherry picked from commit 08f98e3)

commit 3e83d6ac0457811a212bc61e82ae00bddbd3fc52
Author: Pereslegin Pavel 
Date:   2018-07-11T14:25:34Z

IGNITE-7366 Affinity assignment exception in service processor during 
multiple nodes join - Fixes #4321.

Signed-off-by: Ivan Rakov 

(cherry picked from commit efa3269)

commit bc920ccb37f3bd31e98a61fc43c89038f804d12a
Author: Ivan Daschinskiy 
Date:   2018-07-11T14:33:57Z

IGNITE-8945 Stored cache data files corruption when node stops abruptly. - 
Fixes #4319.

Signed-off-by: Ivan Rakov 

(cherry picked from commit fff979a)

commit 86b465b61591b0b00b58c387c03e2cba86eb36e3
Author: Ivan Rakov 
Date:   2018-07-11T14:57:53Z

IGNITE-8965 Add logs in SegmentReservationStorage on exchange process

(cherry picked from commit ee909a3)

commit 02c3419e7d39a0db6ae0dcc6e84c5e9e89b54863
Author: Ivan Rakov 
Date:   2018-07-11T15:45:31Z

IGNITE-8946 AssertionError can occur during release of WAL history that was 
reserved for historical rebalance

(cherry picked from commit 54055ec)

commit 3d727d316c4187c46cf7499255a328a2e265f91d
Author: Alexey Goncharuk 
Date:   2018-07-11T16:50:58Z

IGNITE-8827 Fixed failing test

commit 5c269ebfaf91ce56e8825bf36f41db88fb791cd0
Author: Eduard Shangareev 
Date:   2018-07-11T16:43:19Z

IGNITE-8955 Checkpoint can't get write lock if massive eviction on node 
start started

Signed-off-by: Ivan Rakov 

(cherry picked from commit a0fa79a)

commit 692d8871fc7707fe16aebd6acc340637b9e122f1
Author: Aleksei Scherbakov 
Date:   2018-07-12T09:17:56Z

IGNITE-8863 Tx rollback can cause remote tx hang. - Fixes #4262.

Signed-off-by: Ivan Rakov 

(cherry picked from commit 6440e0c)

commit 8ca5d55ff43db466fba0fddea747fd69bf6fce13
Author: Sergey Chugunov 
Date:   2018-07-11T16:08:56Z

IGNITE-8905 Incorrect assertion in GridDhtPartitionsExchangeFuture - Fixes 

Re: Abbreviation code-style requirement.

[Павлухин Иван]

Andrey, Dmitry,

If we have a practice of formatting a code before merge by committer
then it is already much better. But do we have such a practice?

As for me personally. I have not felt much discomfort with abbreviations.
I already used them extensively. Even "cctx", "ccfg" which are not
mandatory today.

пт, 2 нояб. 2018 г. в 10:58, Dmitriy Pavlov :

> Hi Ivan,
>
> provided that committer has installed ignite-abbrev-plugin it is not a big
> deal to abbreviate common words before a merge.
>
> I had the same impression about abbreviations when I came to the project:
> "all other development world tends to expose as much meaning as it is
> humanly possible in code, but Ignite has abbreviations seemed to hide this
> meaning".  But later I've used to most common abbreviations, like ctx, and
> I always understand that this implies context.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 2 нояб. 2018 г. в 10:21, Andrey Kuznetsov :
>
> > Ivan, I agree with you: some our code style rules are really uncommon.
> >
> > As for one-time contributions, if somebody decides to make a contribution
> > to some project, it's ok to adopt that project rules. Moreover, reviewing
> > committer can silently fix minor code style issues himself upon merge.
> >
> > пт, 2 нояб. 2018 г. в 10:08, Павлухин Иван :
> >
> > > Andrey, Yakov,
> > >
> > > Actually my concert is more about one-time contributions. I imagine
> > > the following. Someone finds a bug a decides to contribute a fix.
> > > I think it is quite common scenario in Open Source.
> > > He creates a PR and awaits a review. I think that a smooth and fast
> > > review process will encourage for new contributions. But if the review
> > > process is not such the contributor can simply give up.
> > >
> > > P.S. In my mind there are quite uncommon code style rules in Ignite
> > > project. But it is definitely not for that topic. I imagine some "New
> > > Contributor Survey".
> > >
> > > чт, 1 нояб. 2018 г. в 18:28, Yakov Zhdanov :
> > >
> > > > Ivan I removed "lic" from the list. Thanks for catch!
> > > >
> > > > Agree with Andrey. After several code reviews newcomers will get used
> > to
> > > > abbreviations.
> > > >
> > > > Andrey, try searching for "fut" and make sure to have "Word" checked.
> > You
> > > > will see plenty of usages. "f" is also ok for future in case it does
> > not
> > > > bring confusion and does not hurt readability.
> > > >
> > > > Let's keep using abbreviations and treat them as mandatory
> requirement.
> > > > This is important for keeping our codebase consistent and tidy.
> > > >
> > > > --Yakov
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> >
> >
> > --
> > Best regards,
> >   Andrey Kuznetsov.
> >
>


-- 
Best regards,
Ivan Pavlukhin

[jira] [Created] (IGNITE-10122) Move Web-Console Frontend/Backend Docker images build to dedicated directory

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10122:
-

 Summary: Move Web-Console Frontend/Backend Docker images build to 
dedicated directory
 Key: IGNITE-10122
 URL: https://issues.apache.org/jira/browse/IGNITE-10122
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Ilya Murchenko
 Fix For: 2.8


It is required to move [frontend / 
backend|https://github.com/apache/ignite/tree/master/modules/web-console/docker/compose]
 Docker build of Web-Console to dedicated directory: {{/docker/compose/}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10121) Web console: Create documentation how to run Web agent as Docker image

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-10121:
--

 Summary: Web console: Create documentation how to run Web agent as 
Docker image
 Key: IGNITE-10121
 URL: https://issues.apache.org/jira/browse/IGNITE-10121
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Ilya Murchenko


Especially specify ho configure path to external folder with jdbc driver.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Abbreviation code-style requirement.

[Dmitriy Pavlov]

Hi Ivan,

provided that committer has installed ignite-abbrev-plugin it is not a big
deal to abbreviate common words before a merge.

I had the same impression about abbreviations when I came to the project:
"all other development world tends to expose as much meaning as it is
humanly possible in code, but Ignite has abbreviations seemed to hide this
meaning".  But later I've used to most common abbreviations, like ctx, and
I always understand that this implies context.

Sincerely,
Dmitriy Pavlov

пт, 2 нояб. 2018 г. в 10:21, Andrey Kuznetsov :

> Ivan, I agree with you: some our code style rules are really uncommon.
>
> As for one-time contributions, if somebody decides to make a contribution
> to some project, it's ok to adopt that project rules. Moreover, reviewing
> committer can silently fix minor code style issues himself upon merge.
>
> пт, 2 нояб. 2018 г. в 10:08, Павлухин Иван :
>
> > Andrey, Yakov,
> >
> > Actually my concert is more about one-time contributions. I imagine
> > the following. Someone finds a bug a decides to contribute a fix.
> > I think it is quite common scenario in Open Source.
> > He creates a PR and awaits a review. I think that a smooth and fast
> > review process will encourage for new contributions. But if the review
> > process is not such the contributor can simply give up.
> >
> > P.S. In my mind there are quite uncommon code style rules in Ignite
> > project. But it is definitely not for that topic. I imagine some "New
> > Contributor Survey".
> >
> > чт, 1 нояб. 2018 г. в 18:28, Yakov Zhdanov :
> >
> > > Ivan I removed "lic" from the list. Thanks for catch!
> > >
> > > Agree with Andrey. After several code reviews newcomers will get used
> to
> > > abbreviations.
> > >
> > > Andrey, try searching for "fut" and make sure to have "Word" checked.
> You
> > > will see plenty of usages. "f" is also ok for future in case it does
> not
> > > bring confusion and does not hurt readability.
> > >
> > > Let's keep using abbreviations and treat them as mandatory requirement.
> > > This is important for keeping our codebase consistent and tidy.
> > >
> > > --Yakov
> > >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>
>
> --
> Best regards,
>   Andrey Kuznetsov.
>

[jira] [Created] (IGNITE-10120) Create docker images for Web Console Frontend & Backend

[Yuriy Sergeev (JIRA)]

Yuriy Sergeev created IGNITE-10120:
--

 Summary: Create docker images for Web Console Frontend & Backend
 Key: IGNITE-10120
 URL: https://issues.apache.org/jira/browse/IGNITE-10120
 Project: Ignite
  Issue Type: Task
Reporter: Yuriy Sergeev


Add docker images 2.6.0:

[https://hub.docker.com/r/apacheignite/web-console-frontend/tags/]

[https://hub.docker.com/r/apacheignite/web-console-backend/tags/]

Thx



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Abbreviation code-style requirement.

[Andrey Kuznetsov]

Ivan, I agree with you: some our code style rules are really uncommon.

As for one-time contributions, if somebody decides to make a contribution
to some project, it's ok to adopt that project rules. Moreover, reviewing
committer can silently fix minor code style issues himself upon merge.

пт, 2 нояб. 2018 г. в 10:08, Павлухин Иван :

> Andrey, Yakov,
>
> Actually my concert is more about one-time contributions. I imagine
> the following. Someone finds a bug a decides to contribute a fix.
> I think it is quite common scenario in Open Source.
> He creates a PR and awaits a review. I think that a smooth and fast
> review process will encourage for new contributions. But if the review
> process is not such the contributor can simply give up.
>
> P.S. In my mind there are quite uncommon code style rules in Ignite
> project. But it is definitely not for that topic. I imagine some "New
> Contributor Survey".
>
> чт, 1 нояб. 2018 г. в 18:28, Yakov Zhdanov :
>
> > Ivan I removed "lic" from the list. Thanks for catch!
> >
> > Agree with Andrey. After several code reviews newcomers will get used to
> > abbreviations.
> >
> > Andrey, try searching for "fut" and make sure to have "Word" checked. You
> > will see plenty of usages. "f" is also ok for future in case it does not
> > bring confusion and does not hurt readability.
> >
> > Let's keep using abbreviations and treat them as mandatory requirement.
> > This is important for keeping our codebase consistent and tidy.
> >
> > --Yakov
> >
>
>
> --
> Best regards,
> Ivan Pavlukhin
>


-- 
Best regards,
  Andrey Kuznetsov.

Re: Abbreviation code-style requirement.

[Павлухин Иван]

Andrey, Yakov,

Actually my concert is more about one-time contributions. I imagine
the following. Someone finds a bug a decides to contribute a fix.
I think it is quite common scenario in Open Source.
He creates a PR and awaits a review. I think that a smooth and fast
review process will encourage for new contributions. But if the review
process is not such the contributor can simply give up.

P.S. In my mind there are quite uncommon code style rules in Ignite
project. But it is definitely not for that topic. I imagine some "New
Contributor Survey".

чт, 1 нояб. 2018 г. в 18:28, Yakov Zhdanov :

> Ivan I removed "lic" from the list. Thanks for catch!
>
> Agree with Andrey. After several code reviews newcomers will get used to
> abbreviations.
>
> Andrey, try searching for "fut" and make sure to have "Word" checked. You
> will see plenty of usages. "f" is also ok for future in case it does not
> bring confusion and does not hurt readability.
>
> Let's keep using abbreviations and treat them as mandatory requirement.
> This is important for keeping our codebase consistent and tidy.
>
> --Yakov
>


-- 
Best regards,
Ivan Pavlukhin

[jira] [Created] (IGNITE-10119) Remove BETA sticker/label from WC

[Yuriy Sergeev (JIRA)]

Yuriy Sergeev created IGNITE-10119:
--

 Summary: Remove BETA sticker/label from WC
 Key: IGNITE-10119
 URL: https://issues.apache.org/jira/browse/IGNITE-10119
 Project: Ignite
  Issue Type: Task
  Components: UI, wizards
Affects Versions: 2.6
Reporter: Yuriy Sergeev






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)