OpenSearch/.gitignore

62 lines
1001 B
Plaintext
Raw Permalink Normal View History

2015-12-15 21:51:38 -05:00
# intellij files
2011-12-05 18:11:12 -05:00
.idea/
*.iml
*.ipr
*.iws
build-idea/
out/
# include shared intellij config
!.idea/inspectionProfiles/Project_Default.xml
!.idea/runConfigurations/Debug_OpenSearch.xml
!.idea/vcs.xml
# These files are generated in the main tree by IntelliJ
benchmarks/src/main/generated/*
2015-12-15 21:51:38 -05:00
# eclipse files
.project
.classpath
.settings
build-eclipse/
2011-12-08 03:47:07 -05:00
2015-12-15 21:51:38 -05:00
# netbeans files
2011-12-08 03:47:07 -05:00
nb-configuration.xml
nbactions.xml
2015-12-15 21:51:38 -05:00
# gradle stuff
.gradle/
build/
# vscode stuff
.vscode/
2015-12-15 21:51:38 -05:00
# testing stuff
**/.local*
.vagrant/
/logs/
2015-12-15 21:51:38 -05:00
# osx stuff
.DS_Store
Add BWC layer to seq no infra and enable BWC tests (#22185) Sequence BWC logic consists of two elements: 1) Wire level BWC using stream versions. 2) A changed to the global checkpoint maintenance semantics. For the sequence number infra to work with a mixed version clusters, we have to consider situation where the primary is on an old node and replicas are on new ones (i.e., the replicas will receive operations without seq#) and also the reverse (i.e., the primary sends operations to a replica but the replica can't process the seq# and respond with local checkpoint). An new primary with an old replica is a rare because we do not allow a replica to recover from a new primary. However, it can occur if the old primary failed and a new replica was promoted or during primary relocation where the source primary is treated as a replica until the master starts the target. 1) Old Primary & New Replica - this case is easy as is taken care of by the wire level BWC. All incoming requests will have their seq# set to `UNASSIGNED_SEQ_NO`, which doesn't confuse the local checkpoint logic (keeping it at `NO_OPS_PERFORMED`) 2) New Primary & Old replica - this one is trickier as the global checkpoint service currently takes all in sync replicas into consideration for the global checkpoint calculation. In order to deal with old replicas, we change the semantics to say all *new node* in sync replicas. That means the replicas on old nodes don't count for the global checkpointing. In this state the seq# infra is not fully operational (you can't search on it, because copies may miss it) but it is maintained on shards that can support it. The old replicas will have to go through a file based recovery at some point and will get the seq# information at that point. There is still an edge case where a new primary fails and an old replica takes over. I'lll discuss this one with @ywelsch as I prefer to avoid it completely. This PR also re-enables the BWC tests which were disabled. As such it had to fix any BWC issue that had crept in. Most notably an issue with the removal of the `timestamp` field in #21670. The commit also includes a fix for the default value of the seq number field in replicated write requests (it was 0 but should be -2), that surface some other minor bugs which are fixed as well. Last - I added some debugging tools like more sane node names and forcing replication request to implement a `toString`
2016-12-19 07:08:24 -05:00
# default folders in which the create_bwc_index.py expects to find old es versions in
/backwards
/dev-tools/backwards
# needed in case docs build is run...maybe we can configure doc build to generate files under build?
2015-12-15 21:51:38 -05:00
html_docs
# random old stuff that we should look at the necessity of...
2015-12-15 21:51:38 -05:00
/tmp/
eclipse-build
# projects using testfixtures
testfixtures_shared/
# These are generated from .ci/jobs.t
.ci/jobs/
# build files generated
doc-tools/missing-doclet/bin/