(file) Return to release.notes CVS log (file) (dir) Up to [Development] / JSOC / CM / V8.12

File: [Development] / JSOC / CM / V8.12 / release.notes (download)
Revision: 1.2, Wed Dec 7 20:17:50 2016 UTC (6 years, 5 months ago) by arta
Branch: MAIN
CVS Tags: Ver_LATEST, Ver_9-5, Ver_9-41, Ver_9-4, Ver_9-3, Ver_9-2, Ver_9-1, Ver_9-0, Ver_8-12, NetDRMS_Ver_LATEST, NetDRMS_Ver_9-5, NetDRMS_Ver_9-41, NetDRMS_Ver_9-4, NetDRMS_Ver_9-3, NetDRMS_Ver_9-2, NetDRMS_Ver_9-1, NetDRMS_Ver_9-0, NetDRMS_Ver_8-12, HEAD
Changes since 1.1: +46 -1 lines
Added release notes for the 8.12 release.

                       Release Notes JSOC V8.12        7DEC2016
                       ------------------------        ---------

A release is a set of binary and text files, each having a specific version. The release itself is
also versioned to facilitate the identification of the release. For example, release 1.3 may 
contain fileA#1.8, fileB#1.2, and fileC#2.2 and release 1.4 may contain fileA#2.5, fileB#2.1, 
and fileC#2.9. JSOC releases are similarly versioned and contain a set of such files.  JSOC release
code is guaranteed to compile on cluster nodes (e.g., n04 and solar3).  At the time of the 
creation of the release, the versions of each file will be very recent - most will be the
"head" versions. The set of files is stable. They have been tested and verified to work properly
on the supported systems. As time passes, newer versions of files will be committed to the 
code repository and there is no guarantee that these changes will not destabilize JSOC 
(i.e., they may cause JSOC to no longer compile or execute properly).  

There are several ways to use this release.  If you wish to simply use pre-built
binaries, you can use the production binaries, which are located at 
/home/jsoc/cvs/Development/JSOC (The release binaries are actually in
/home/jsoc/cvs/JSOC, but as our production code changes more quickly
than releases are generated, we put critical fixes in the
"Development" tree. To be sure you use code that has been built with
these critical fixes, you'll need to use the "Development" tree. As
time passes our production code will stabilize. When that happens, you should use
/home/jsoc/cvs/JSOC. But for now, you should use the "Development"
tree.). Every time a release is created, the binaries in this location get updated
by the jsoc user. To use these binaries, you can run them directly, 
"/home/jsoc/cvs/JSOC/Development/bin/linux_x86_64/show_info -j hmi.M_45s", 
for example. Or you can put /home/jsoc/cvs/JSOC/Development/bin/linux_x86_64 in 
your path environment variable.

If instead you want to work with stable source files, then you must have a local copy (e.g., 
in your home directory) of the source code in the CVS code repository. You must "build" or "make" 
the code this local code before it can be used. You will want to work with a local copy if you 
plan on making changes to the repository files (i.e., you plan on doing development). Changes you 
make to your local copy are not visible to other users until you commit those changes back to the 
CVS repository.  

Obtaining the Release
To update your working directory to this release, or to check-out this release anew, 
please visit http://jsoc.stanford.edu/jsocwiki/CvsInit (please see the section entitled
Update Your Existing Working Directory ("Sandbox")). Please keep in mind that
users may have modified files since the release was created, so use of the 
scripts documented in the web page may result in a working directory whose
content is not identical to the release.  

Additional Info
Use the Apache CVS gui to see diffs between file revisions. For example, go to http://jsoc2.stanford.edu/cvs/JSOC/base/drms/
and click on the name in the File column and then click on "diffs to previous #" to see the diffs.

Changes since previous release (V8.11 -  June 3, 2016)

- Remote SUMS: The download of SUs are now chunked so that a single SCP worker downloads multiple SUs to increase efficiency. There is a new Python class that handles the scps needed by multiple request.
- Modified the localization script to produce a defines file appropriate for bash (in addition to the existing files for Python, C, C-shell, and make) .
- Modified the series-subscription manager code to use server-side Python cursors (to avoid client-side memory bloat).
- Fixed DRMS lockfile Python code.
- Added the Storage Unit size to the rs.py CGI server program (which provides SU information to the remote-SUMS daemon at remote sites).
- Replaced a call to jsoc_fetch with a direct SQL command to the SUMS DB in the remote SUMS server.
- Converted remote SUMS from a Python 2 program to a Python 3 program.
- Added more logging in jsoc_fetch to help track down issues.
- Added a function to libmisc to compare floats for bit-wise equality.
- Added Kolja's drms_json library to our base/lib directory. The qmaps project uses it now.
- Added an entry for Jan 1, 2017 leap second to timeio library.
- This release contains prep work for the new non-RPC SUMS (aka the MT SUMS). At this point, this feature is disabled. It will be enabled for the next release.
- This release contains changes for the 8.12 version of the rings project.

- There are a few new config.local parameters for MT SUMS: 
  RS_N_WORKERS - Remote SUMS: The number of parallel SCP worker threads.
  RS_TMPDIR - Remote SUMS: The temporary directory into which Storage Units are downloaded. This should be on the same file system in which the SUMS directories are located.
  RS_SCP_MAXSUS - Remote SUMS: If more than this number of SUs are awaiting download, then an ScpWorker will initiate a download.
  RS_SCP_MAXPAYLOAD - Remote SUMS: If the cumulative payload exceeds this many MB, then an ScpWorker will initiate a download.
  RS_SCP_TIMEOUT - Remote SUMS: If an ScpWorker is idle for at least this many seconds, and there are SUs pending a download, then an ScpWorker will initiate a download.
  BIN_PY3 - The path of the Python 3 binary to be used by DRMS.
- Made some changes to the observables code to allow for localization of binary file paths. This was needed for Pete Schuck to work on the "24-hour-oscillation" issue.
- All RS_* timeout values are now expressed in seconds.
- Fixed make-dependency issue for libraries used by SUMS executables.
- Modified the configure script to return 1, and not 0, when an error occurs.
- Modified the close-records function to ensure that all open segment files are closed. This prevents DRMS modules from terminating with open files.
- Replaced shell-dependent code with shell-independent code in get_slony_logs.pl.
- Fixed a large memory leak in the series-subscription manager Python code.
- Fixed a problem with the usage of pipes in the generation of dump files by the series-subscription manager.
- Fixed a problem with the text in the dump files produced by the series-subscription manager. We now use the official Python/psycopg2 method for representing data values in text format.
- Fixed a syntax issue with a DB UPDATE statement in the series-subscription CGI server code.
- Made series-name comparisons case-insensitive in the series-subscription CGI server code.
- Fixed the ingestion of SQL in the series-subscription client code. There were issues of pipes filling up or pipes breaking if psql dies with an error.
- Fixed two thread-synchronization issues in the remote SUMS server.
- Fixed an issue with download-failure restarts in the remote SUMS server.
- Fixed an issue with download-failure error handling in the remote SUMS server.
- Fixed a deadlock in the remote SUMS server.
- Modified the remote SUMS server to handle the case where there are not enough resources to spawn a new worker thread.
- Fixed a threading issue in remote SUMS. A psycopg2 cursor was being shared between threads, and these cursors are not thread safe.
- Added functions to remote SUMS to commit changes to the db, and use them where necessary. Some changes the to DB were not being committed.
- Fixed issues related to the locking of certain table objects in remote SUMS.
- Fixed the export-system code that re-uses existing requests if a new request is identical to an existing, recent one.
- Added default information for linked keywords to jsoc_info.
- Modified fits-file support code to not bother looking for cached and opened FITS files in DRMS if the cache struct is NULL to begin with.
- Worked-around a PostgreSQL bug that incorrectly determine the type of integer in the ECPG compiler.
- Fixed a bug in im_patch registration.
- Fixed a bug in jsoc_resize.

Karen Tian
Powered by
ViewCVS 0.9.4