Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
margo
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • sds
  • margo
  • Issues
  • #39

Closed
Open
Opened Jan 26, 2018 by Matthieu Dorier@mdorier
  • Report abuse
  • New issue
Report abuse New issue

Handle cache not working properly

This issue came up in testing sds-keyval. The scenario is as follows: A client issues one "open" RPC, then X "put" RPCs, then on "shutdown" RPC. If X is 31 or greater, the "shutdown" RPC will cause the following error on the client side:

# HG -- Warning -- /home/mdorier/spack/var/spack/stage/mercury-master-nreeb4qqqsnhpfwmrl22o7shh7vnv2es/mercury/src/mercury_core_header.c:293
 # hg_core_header_response_verify(): Response return code: HG_INVALID_PARAM

And in the server:

# HG -- Error -- /home/mdorier/spack/var/spack/stage/mercury-master-nreeb4qqqsnhpfwmrl22o7shh7vnv2es/mercury/src/mercury_core.c:2229
 # hg_core_process(): Error while executing RPC callback

To try the code in sds-keyval, call the server as follows:

bin/sdskv-server-daemon -f addr.txt na+sm mydb:bwt

and the client as follows:

test/sdskv-put-test `cat addr.txt` 1 mydb 40
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: sds/margo#39